Teach Us Something Technical: The Command Line

For our first meetup, 6 people will teach us something awesome about the command line (specifics to follow). If you have an idea and you'd like to present, let us know here (https://docs.google.com/forms/d/1uYaHqy7cF4gDHtFyRAc49yzO8RJ9ai0ShWLBT3AyLGA/viewform?usp=send_form).

Agenda

• 6:30pm - 6:45pm: meet and greet

• 6:45pm - 7:45pm: presentations

• 7:45pm - 8:15pm: meet and greet

• 8:15pm: drinks nearby (TBD)

Presentations

• Intro to Screen - Sha-Mayn Teh

• Analyzing and reusing your command history - Nathan Hurst

• Creating a homebrew installable project from a Github repo - Tommy Murphy

• Bash scripting case study - Courteney Ervin

• bash_profile - Eric Tang

• Power unix commands - Scott Carleton

Who should come?

The meetup is open to any engineer who is still learning (to us, that means every engineer). We ask that the speakers target their talks for the following background...

If I'm teaching at this meetup, what should I do?

Talks are 10 minutes total including questions. This usually means preparing 5 minutes of content and taking 5 minutes of questions.

To help teachers hone their clarity, we encourage the audience to ask questions during the talks. For now, we’re limiting questions to one question per audience member to keep things moving.

A few other guidelines:

• Make sure you target the topic of the meetup

• Your talk should target teaching engineers something that they can use soon - likely immediately. That means most talks should avoid non-free or and non-open-source software.

• Your talk should be broadly applicable. This means you should avoid avoid company pitches.

• Please practice your presentation all the way through at least once!

Who should I target my talk toward?

We generally expect engineers at all experience levels to be at the meetup, but feel free to make the following assumptions:

• Members have used a scripting language (ex: Ruby, Python, PHP, Javascript). Don’t assume people have experience with other languages - it’s fine to present in them, but you may need to be ready to answer a few more questions.

• Members have some experience with a web framework.

• Members have basic knowledge of the command line.

• Members have used a version control system.

Who should not come?

We focus on teaching, learning, and technology, not recruiting. If your primary goal is to recruit engineers, there are other places to go.