🤝 Organizing events, being part of a community: why it matters to me
From co-organizing Fork it! For Kids to simply showing up at meetups, here's why being part of a tech community has become just as important to me as writing code.

Jeanne Grenet
I used to think that being a good developer meant getting better at code.
Reading documentation, building side projects, watching conference talks at 1.5x speed.
And then I started actually going to the conferences.
Something shifted. Not in my technical skills, at least not directly, but in how I understood what this job is really about.
Because tech isn’t just a stack. It’s people. And communities are where those people meet.
🌱 Where it started: a teenager in a Scratch workshop
I keep coming back to the same memory when I try to explain why I care about all of this.
I was a teenager, sitting in a room full of kids I didn’t know.
It was a Devoxx4Kids workshop. We were building something in Scratch, nothing complicated, but at some point it worked, and the room came alive a little.
That afternoon didn’t teach me to code. What it did was show me that programming could feel like something.
That it could be creative, collaborative, and genuinely joyful, not just a skill you acquire for a job.
That single workshop quietly shaped the path that led me here.
Years later, when I joined Fork it! Community and got the chance to co-organize Fork it! For Kids, I understood why: I wanted to build that kind of room for someone else.
🧒 Fork it! For Kids: the organizer’s side
Fork it! For Kids is a free event we run in Rouen for children aged 7 to 16, where they get to discover robotics, web development, game design, and programming through hands-on workshops led by volunteers.
Two editions so far. Around 20 kids the first time, nearly 40 the second.
I won’t pretend organizing it is easy. There’s the logistics, the volunteer coordination, the last-minute technical glitches, the planning spreadsheets that never quite survive contact with reality.
But there’s also this: during our second edition, several kids skipped their snack break because they didn’t want to stop coding.
I think about that moment a lot. No one asked them to stay. They just wanted to finish what they’d started.
That’s the thing about events done right: you create the conditions, and then people surprise you.
💬 What I didn’t expect about being an organizer
Before I started organizing, I thought the hard part would be the technical setup.
It’s not. The hard part is the people management, not in a frustrating way, but in a deeply human one.
Coordinating a team of volunteers who are all giving their time freely means you can’t manage them like a project. You have to inspire them, trust them, and leave room for their own judgment.
Every workshop facilitator brings something you couldn’t have planned for: their way of explaining things, their patience, their enthusiasm. And that’s what makes it work.
I also didn’t expect how much I would get from it as an attendee of my own event.
Watching a 10-year-old figure out why their robot isn’t following the line, and then fix it, teaches you something about how people learn that no book really captures.
🤝 Why community matters beyond the events
Fork it! For Kids is one piece of a much bigger thing for me.
I’m part of Fork it! Community more broadly: I attend meetups, I help with event organization and communication.
But I’d say the same thing about any tech community, because the value isn’t specific to one name or one structure.
A tech community is where you remember you’re not alone.
When you’re deep in a problem at work, it’s easy to feel like you’re the only one who has ever struggled with this. A community is where you discover that someone else hit the exact same wall, found a way through, and is happy to tell you about it.
It’s where you grow in ways your job can’t always offer.
Side projects, conference talks, workshops: these push you in directions that a sprint backlog rarely does. I’ve learned more about how to communicate technical ideas clearly from preparing a 20-minute talk than from years of pull request descriptions.
And it’s where you give back what was given to you.
That Devoxx4Kids workshop I attended as a teenager? Someone organized it. Someone wrote the curriculum, found the venue, showed up on a Saturday to make it happen.
I didn’t know it then, but that person was building the room I’d eventually want to build for someone else.
That’s the loop I want to be part of.
🔠What’s next
I want to keep showing up. To meetups where I know nobody. To talks where I might disagree with the speaker. To events I help organize, or not, not because it’s efficient, but because it’s worth it.
Because I’ve learned that the best thing about being in a tech community isn’t what you get out of it.
It’s what you find yourself wanting to give.