Skip to main content

Command Palette

Search for a command to run...

You don't build a team at a desk at home. A hackathon reminded me.

Updated
2 min read
K
Engineering Team Leader with 8+ years building backend systems in Java/Kotlin & Spring Boot. I write about engineering, leading teams, and building products on the side.

I love quiet work. But that's not how you build a team.

A calm home office, deep focus, no interruptions — that's where I do my best individual work, and I have no plans to change it.

But I've always known it's not how you build a team. A team forms when people actually get to know each other.

What the hackathon actually changed

We just finished a company hackathon. We came in with a list of things to ship — and we shipped them.

What made it work wasn't the tooling or the extra hours. It was being in the same room:

  • Real conversations, without scheduling them first

  • A shared goal you could feel

  • Support within arm's reach

At MagellanERP we're a team of A players, but the team is still new — a few months together, most of us strangers before that. One vision connects us, and the relationships are still being built.

That's what made the time so valuable. Beyond the shipped projects, there were conversations that had nothing to do with work, time spent just being around each other, and a lot of shared laughter — the kind that actually pulls a team together.

Trust doesn't grow through async.

The takeaway

My individual work stays in quiet. That's where I'm most effective, and that won't change.

But sometimes one day at the same table does more for a team than weeks of remote work. That's worth being deliberate about — instead of waiting for it to happen on its own.