Write/Speak/Code

By Leave a Comment

Open Source: The Whys and Hows

Many programmers, both new and seasoned, have heard the advice:

“You should contribute to an Open Source project!”

Despite being solid advice, there’s less information on why contributing to Open Source is a good idea, particularly for women, and then even less on how to go about finding a project and contributing. Github, the most well-known repository for open-source projects is rather daunting to new visitors. Thankfully, Camille spoke to WriteSpeakCode participants on how to participate and why.

Open Source needs more participation from women and minorities. Women make up only 3% of the Open Source community, but those who participate have made a significant impact. In another post, we’ll go over some of the barriers to entry for these groups. WriteSpeakCode is about becoming more visible in the tech community, and participating in Open Source is a great way to do that. Open Source appeals to a nerd’s needs to solve problems, and there’s a “warm fuzzy” feeling you get when adding your contribution. If you’re a “joiner” then Open Source is definitely for you. It’s all about joining in and being a part of something. It’s also easy to get started. Downloading the codebase for a project is only a few clicks, and anyone can comment on bug reports and add to project wikis.

If the actually contributing part is easy, the hard part is finding a project to contribute to. As I mentioned before, github can be kind of overwhelming. There are so many projects listed and languages mentioned. The first thing to think about when finding a project is your goal for working in Open Source. You might be looking to experiment with different languages. Perhaps you want to make a contribution to the community or contribute to a project that resonates with your values. You might just be looking for more visibility, that’s fine, too.

Once you know your reasons for contributing, it’s easier to find a project that fits in with your reason in mind. Here are some ideas for finding a project that interests you:

If there is a particular Open Source software, framework, or other tool you use frequently, you might want to consider contributing to that. You may have even already noticed bugs that need fixing!

Now you found a project, so it’s time to participate! Github can be a little daunting at first, but CodeSchool provides this amazing free interactive tutorial to get you started: try.github.com

Remember that you’re not required to contribute code. There are other ways to participate, like adding to documentation. But if you want to code, then by all means code!

Another way to contribute to the Open Source is by starting your own project! It’s easy to do on GitHub: https://help.github.com/articles/create-a-repo

One thing to keep in mind if you’re starting your own project is that you will need to add a license. I’m not a lawyer, but I still think it’s a good idea to add a license so that your code can be freely used, modified, and shared—which is the heart of Open Source. Here’s more information on prefab licenses you can use (since you’re probably not a lawyer, either):Bit.ly/OSSLicenses

At WriteSpeakCode, we were challenged to find and contribute to an Open Source project on code day! Here are some of our contributions:

  • Commenting on a ticket in a Rails repository that lead to the ticket being closed.
  • Working on an exclamation point monitor so you don’t use too many!!!!!!!!!!!
  • Fixing a typo on code used to calculate business days.
  • Contributing to a project using symbol fonts to create maps by adding a SASS feature for adding colors.
  • Cleaning up confusing documentation for OpenCity.
  • Fixing a broken link in the Etherpad Lite readme.
  • Fixing documentation and adding links for a WordPress plugin.
  • Testing bugs and adding documentation to Normalize.css.

Now it’s your turn!

By Leave a Comment

Speak Now!

Tips on Proposal Writing for Tech Conferences

Speak Day focused primarily on speaking at tech conferences, and the way you become a speaker at a tech conference is by submitting a proposal. If you’re familiar with academic proposals, tech proposals are quite different. Most tech conferences are looking for a title and a description, nothing more. Sometimes they ask for an abstract and/or reviewer notes. Make sure you follow the proposal submission guidelines for the talk you’re submitting your proposal to. Here are some more proposal tips from conference organizers and other experts:

  • Provide details such as the names of languages and tools you want to cover in your talk.
  • You don’t want to mislead your potential audience as to what your talk is about. (For example, don’t describe your talk as being philosophical if it’s really about shipping containers.)
  • Tell a story in your proposal and bring the organizer along with you.
  • Show that you’re saying something unique: form your own opinion in a controversial area, find a topic that your audience wouldn’t normally be interested and explain why they should, or do something instructional.
  • Do some thinking or even outlining on your topic that goes beyond your initial idea. You might find more interesting concepts and ideas to add to your proposal.
  • If the conference has a template for proposals, follow it. It will show you how specific to be.
  • Make your talk sound like something people would want to see!

Women interested in speaking are encouraged to follow @callbackwomen on twitter to receive notifications when conferences are looking for proposals. Conference organizers like to reach out to people they’ve seen talk before, but there are plenty of ways for newbie speakers to get started. You can get experience talking at some conferences that are more open to new speakers. Some have shorter slots available. Participating with meetup groups is another great way to get started. Barcamps and unconferences are great opportunities for speaking as they encourage (or even sometimes require) attendees to speak. Local hackerspaces often do short lightning talks where they welcome new speakers. You don’t have to start by giving a big presentation at a national conference, but of course, you can.

By Leave a Comment

Public Speaking Tips for Technical People

One of the great things about Speak Day was that many of the experts who came to speak with us about speaking hadn’t always been experts. Many of them have, and still do, experience many of the same fears about public speaking that we do. Given that background, their tips for presenting at a tech conference, or any other public speaking event, really hit home.

Tips on Knowing Your Material

  • People who know you well can provide suggestions on what to talk about.
  • Your experiences and knowledge areas are unique.
  • Think of speaking as a way to get feedback on a hypothesis you have about a topic.
  • Preparing for a talk is an excellent way to learn new material.

Tips on Confidence as a Woman Speaker

  • Know that you have a right to be there and that you have important things to say and don’t let anyone convince you otherwise.
  • Know that other women will see you up there and think about participating because you’re there.
  • Be comfortable and passionate about what you’re saying.
  • Understand that often people at tech conferences want to see more women participating.

Tips for Handling Nerves

  • Practice a lot!
  • Practice with coworkers or friends, or on yourself.
  • Record yourself and listen to your voice, or video yourself and watch it.
  • Give the presentation to someone who isn’t in your field.
  • Preparation will make you feel comfortable and successful.
  • Do some yoga before hand.
  • Don’t get too invested in your slide changing mechanism (or your slides, for that matter) since technology often fails, even at tech conferences.
  • Prepare the first few slides from memory and then look for friendly faces in the audience.
  • Ground yourself by taking a deep breath. This can help you avoid nervous behavior such as saying “um” or “and so” or fiddling.
  • Embrace your adrenaline! Put the rush of nervous energy towards what you’re saying and making eye contact with the audience.
  • People don’t expect you to be perfect. They don’t know what you were planning on saying, so they’ll have no idea if you deviate from the plan.

Tips on Q&A Sessions

  • Make sure you leave time at the end of your talk for questions.
  • Ask your peers what questions they have.
  • If someone is derailing the conversation, ask to speak with them about it in person after the talk is over.
  • Anticipate controversy. Know what the controversies and alternative lines of reasoning surrounding your argument are before you give the talk.
  • Be honest if you don’t know the answer: that’s better than making up something.

Tips on Engaging Presentations

  • Make eye-contact. Try to look at everyone (or every section in a bigger presentation) but don’t go back and forth like a sprinkler.
  • Ask your audience questions.
  • Understand your audience so you talk in a way they can understand you.
  • Don’t just include the facts, but explain what the facts mean and why they’re important.
  • Tell a story.
  • Create your presentation materials after you know what you’re going to say.
  • The presentation materials should enhance the talk, but you should be able to give the presentation without them.
  • Keep your slides consistant (such as using all black and white photos).
  • Don’t use Comic Sans.
  • Cats!