Why software engineers should go to conferences (and speak at them)
What attending and speaking at tech conferences like Fluttercon gives a software engineer, and how to get started with your first talk.
Maher Jaafar
· 2 min read
Many engineers see conferences as a nice extra, or as a few days away from "real work". I see them as one of the best investments in a software engineering career. I've attended them, organised community events and spoken at Fluttercon, and here is why I keep going back.
You learn what you didn't know to search for
Documentation answers the questions you already have. Conferences show you the questions you should be asking: new patterns, failures other teams already paid for, tools you hadn't heard of. One good hallway conversation can save weeks of work.
You meet the people behind the tools
Talking directly to framework maintainers, package authors and engineers solving the same problems as you changes how you work. You understand the "why" behind design decisions, and you build relationships that last far beyond the event.
Speaking makes you a better engineer
Preparing a talk forces you to understand a topic deeply enough to explain it simply. Standing in front of a room full of people who notice every dropped frame is humbling and incredibly instructive. The questions afterwards are often better than the talk itself.
It also makes you better at your day job: explaining trade-offs to stakeholders, presenting architecture decisions and onboarding new team members all use the same skill.
It builds trust before you meet people
A recorded talk is public proof of how you think. Recruiters, clients and future colleagues can watch it before ever speaking to you. A recorded talk says more about how you think than any line on a CV.
It brings value back to your team
When you return, share what you learned: a short write-up, a lunch talk, a proof of concept. That turns a personal trip into a team investment, and it makes it much easier for your company to support the next one.
How to get started
- Attend locally first. Meetups are low pressure and full of people happy to help.
- Give a lightning talk. Five minutes about one thing you learned at work is enough.
- Write first, speak second. Turn a blog post into a talk proposal.
- Submit to calls for papers. Rejections are normal; keep submitting.
- Help organise. Volunteering at events is the fastest way into a community.
Conferences are not a break from engineering. They are where a lot of the best engineering ideas start.