YAPC::NA 2011 • Asheville, NC

Lightning Talks Day 1
By R Geoffrey Avery (‎rGeoffrey‎) from Philadelphia.pm
Date: Monday, 27 June 2011 11:35
Duration: 50 minutes
Target audience: Beginner
Language:

You can find more information on the speaker's site:


More talks:
R Geoffrey Avery (‎rGeoffrey‎) - ‎Lightning Talks Day 2‎
R Geoffrey Avery (‎rGeoffrey‎) - ‎Lightning Talks Day 3‎

Schedule:

Jan Dubois - ‎Running Perl applications on the Stackato cloud platform‎
John Anderson (‎genehack‎) - ‎All Your Code Gonna Git Got‎
Brian Duggan - ‎Navigate with Toto‎
Uri Guttman (‎uri‎) - ‎Template Benchmarks‎
Duke Leto - ‎Solgenomics : Slicing and Dicing Plant Genomes with Perl‎

Sam Vilain (‎mugwump‎) - ‎Threading Perl with TBB‎
Brad Oaks (‎bradoaks‎) - ‎SQL so close I can paste it‎
Sterling Hanenkamp (‎zostay‎) - ‎OWASP Top 10‎
Shawn Moore (‎sartak‎) - ‎cpandoc: perldoc for modules you haven't installed yet‎
Dan Wright (‎ehdonhon‎) - ‎Pittsburgh Perl Workshop‎

These Lightning Talks may be serious, funny, or both. They may be given by experienced speakers already giving full length talks or by first time speakers just starting out (this is a great way to get started if you have something to say). If you are a first time speaker you will win a tie with an experience speaker when the schedule is made if it comes to it. Today's first time speaker could be tomorrow's keynote speaker.

We will have about 10 Lightning Talks of 5 minutes each day. Submit your talk through the submit talk link on this website. The first deadline is with the full length talks in April. The second deadline is one week before the conference starts and many proposals will be accepted. At least two speaking spots on day 2 will be held open until the day before the talks to give you a chance to see something at the conference and put together a Lightning Talk response. However if you wait for the later deadlines note that there are fewer spots available and you are less likely to be accepted so please try to submit more than a week before the conference.

In addition to the five minute Lightning Talks where you get to use your computer, slides, and any other tool, we will also have some Lightning Advertisements. These are only 30 seconds, you don't have to submit a proposal, you don't get any slides, and the only AV assistance offered is a microphone. If you have a BOF to announce, an auction item so advertise or any other short message you can use the transition time that would be otherwise wasted between Lightning Talks to share your message. Just show up before we start and take a seat in the assigned seats in the front of the room.




Why Would You Want to do a Lightning Talk?

Maybe you've never given a talk before, and you'd like to start small. For a Lightning Talk, you don't need to make slides, and if you do decide to make slides, you only need to make three.

Maybe you're nervous and you're afraid you'll mess up. It's a lot easier to plan and deliver a five minute talk than it is to deliver a long talk. And if you do mess up, at least the painful part will be over quickly.

Maybe you don't have much to say. Maybe you just want to ask a question, or invite people to help you with your project, or boast about something you did, or tell a short cautionary story. These things are all interesting and worth talking about, but there might not be enough to say about them to fill up thirty minutes.

Maybe you have a lot of things to say, and you're already going to give a long talk on one of them, and you don't want to hog the spotlight. There's nothing wrong with giving several Lightning Talks. Hey, they're only five minutes.

On the other side, people might want to come to a lightning talk when they wouldn't come to a long talk on the same subject. The risk for the attendees is smaller: If the talk turns out to be dull, or if the person giving the talk turns out to be a really bad speaker, well, at least it's over in five minutes. With lightning talks, you're never stuck in some boring lecture for forty-five minutes.

Still having trouble picking a topic, here are some suggestions:

1. Why my favorite module is X.
2. I want to do cool project X. Does anyone want to help?
3. Successful Project: I did project X. It was a success. Here's how you could benefit.
4. Failed Project: I did project X. It was a failure, and here's why.
5. Heresy: People always say X, but they're wrong. Here's why.
6. You All Suck: Here's what is wrong with the our community.
7. Call to Action: Let's all do more of X / less of X.
8. Wouldn't it be cool if X?
9. Someone needs to do X.
10. Wish List
11. Why X was a mistake.
12. Why X looks like a mistake, but isn't.
13. What it's like to do X.
14. Here's a useful technique that worked.
15. Here's a technique I thought would be useful but didn't work.
16. Why algorithm X sucks.
17. Comparison of algorithms X and Y.

Of course, you could give the talk on anything you wanted, whether or not it is on this list. If we get a full schedule of nothing but five minutes of ranting and raving on each topic, a good time will still be had by most.

Attended by: