* 2013 session submissions should be made through the Register/Profile page.
Welcome to Code Camp. By definition code camp is a conference by developers for developers and that means our presenters are drawn from our local development community. This article serves as a guideline to help new presenters put together their first talk.
Code camp talks are 75 minutes in length. The room provided to you will depend on the number of folks who register for your talk. You may have a small intimate setting for groups under 30 or a larger amphitheater setting for larger groups.
Projectors are provided and usually display best at 1024 x 768. Make sure that your material presents well at that resolution. If for example you are using Visual Studio, change your text to display a 14pt font. If you plan on giving out material, you will need to bring as many copies as you need. We have no access to copy machines at camp. Also, wireless and wired internet will likely be available for speakers. If your session requires the internet, make sure you come come early to verify you have a good connection.
You will need to bring your own notebook computer to plug in if your session requires that. There may be equipment in the room you are presenting in, but don't count on anything more than a projector. Same with white or black boards. They may be available, but don't count on it.
If you have material you would like to share with your attendees, you can use the wiki link on your session. By default, you wiki points to PBWiki, however if you want to use WetPaint's integrated wiki, you can change your profile to point to that instead.
Choosing a Topic
There are a few approaches to choosing a topic but for your first talk - choose something you’re passionate about and/or really interested in. This will make the experience fun and your enthusiasm will carry you through any first time jitters.
You should also select a topic that you can talk about for more than 75 minutes. You don’t need to know every detail about your topic, but you will be asked questions so you’ll want to have more depth on the subject than you present.
Once you’ve decided on the topic you’ll need to start planning. Usually you will have a slide deck for some parts of your presentation. At a minimum the slide deck should contain:
- A leading slide that contains the presentation title and author information. This should be up and visible as soon as your computer is ready to start so that the audience can quickly determine if they are in the right room.
- An agenda that lays out what you will be covering in the talk and in what order. This prepares the audience for what is to come and helps set their expectations and lays a learning framework.
- A closing slide that contains any information you want to leave them with like your blog or email address.
For example, if you are going to give a C# intermediate talk then you can assume that the core of your audience will have written something using C#. These types of assumptions allow you to create a persona of your expected audience attendee. Having a “person” to target the talk to will help you plan how you will move through your talk and what you will emphasize.
Once you’ve created the outline, complete the talk by adding depth. This depth may consist of concept slides, code samples, images, tables, sound elements, etc… all depending on the nature of your topic. Your content should support your talking points so talks that are code specific should have plenty of coding examples while concept talks (like architecture, project management, etc…) should use images or case studies.
I find it helpful to think of this process as creating a learning journey for my attendees. I have my persona who has some grounding in the technologies I’m going to cover, and is there to learn about the specific element(s) I’m presenting on.
During this stage don’t worry about time. You are simply trying to figure out how much material you must have to support the basic premises of your talk.
Once you’ve created all your content - do a timed run through. Do you have too much material? Not enough?
If you have too much content it is very likely that you have tried to do too much; that your subject is too broad. This is actually a great place to be. Re-evaluate the topic and constrain it. How much to bring it in depends on how much over the one hour time limit you are.
Get the talk down to 60 minutes even though the time limit is 75 because you’ll want to leave time for questions. Places for questions can be sprinkled through out your talk or just done at the end. How you handle questions is based on how engaged you want to make your audience. Remember that each attendee is coming to your talk looking for some kernel of wisdom that they can take away. Sometimes it is the question period that will get you the great reviews and this is where having a deep knowledgeable comes in very handy.
If you have to choose between a slide and code…choose code. I’ve even seen code put into a slide to zoom in on a particular concept. This technique can actually save you time when discussing small code snippets that don’t require the development environment.
Practice alone a few times until you feel comfortable with the material. Then take that big step and ask some close friends to listen to your talk. Ideally you’ll want some folks who are familiar with the subject and some who are not. Listen to the feedback from both groups. You are likely to hear their questions again and having already answered will make it easier to respond during a “live” talk. Additionally, your friends can double check your assumptions, code, and approach. Letting you know what parts look good and what parts need more work.
While rehearsing, make sure that the presentation content, such as code, is clearly visible from the back of an average size conference room.
Now it’s time for the presentation.
Before you get there:
- Get a good night’s sleep.
- Eat breakfast.
- Wear comfortable clothes.
- Bring water.
- Double check your equipment. Laptop, power cable, mouse, etc…
- Bring business cards.
Be ready to start setting up your machine as soon as the speaker from the last section finishes.
- Make sure that the presentation is set up so that the users can see the material. This is especially important for code examples because you’ll likely have to adjust the font and move some of your tools off the main GUI.
- Pre start as much as you can before the presentation so that you can just switch. This may be a slide deck, development environment, sample files, console window, etc…
- Make sure that you remembered to reset any code samples to the starting state. It is common to forget to reset these after you’ve done your practice runs.
During the presentation:
- Slow things down; don’t talk too fast
- Talk to the guy in the back of the room.
- Be yourself.
- Have fun.
Remember that your audience wants you to succeed. They are there because they believe that you have something to teach them. So have fun and good luck.