A few weeks ago I delivered my first ever Pecha Kucha talk.
Pecha Kucha works a little bit like Ignite with a few tweaks. You have to give a short talk consisting of 20 slides, where every slide automatically changes to the next one every 20 seconds. This gives you a talk that is 400 seconds or 6 minutes 40 long.
With Ignite it's 20 slides and every 15 seconds. Not much of a difference but very important.
Talking for 15 seconds is easy, you don't even have to know what you'll be talking about and can just look at the topic given on your slide and start. But with 20 seconds you have to think a little bit aobut what you're going to say, if you wing it completely you will have dead air, but if you prepare a bit too much you will run out of time on every slide.
And it's impossible to catch up to a Pecha Kucha presentation, they're just too quick.
I spent a lot of time preparing for my talk, but not that much time practicing and it shows in the video. Sometimes I have to make a comical gesture because the slide doesn't change quickly enough and other times I kind of get run-over by the next topic at hand - this happens when you're very used to changing slides at uneven intervals.
Another thing the video shows is that I had too much content prepared for too little time. The BPM of my talking speed is insane and really dilutes my message ... well the fact there are too many messages already dilutes my message.
To top it all off I was actually quite nervous because I didn't know if I matched my presentation well to the audience (always do research on who your audience is) and because the format was new and I knew I didn't prepare well enough.
But hey, apparently I'm doing another thing similar to this in Belgrade on the 31st of August. That should be fun.
Learned something new?
Read more Software Engineering Lessons from Production
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Software Engineering Lessons from Production
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Senior Mindset Book
Get promoted, earn a bigger salary, work for top companiesLearn more
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️