The Folkabuss

There’s a phrase that floats around Microsoft research circles: “1 engineer, 1 month, 1 million lines of code.” It comes from Distinguished Engineer Galen Hunt, and it’s deliberately absurd. The point isn’t the line count — it’s compression: how much one engineer can get done when judgment, tooling and ownership compound.

The question I keep coming back to is what happens when you zoom out one notch. If one exceptional engineer can do that, what does the smallest possible team of them look like? Not a startup’s first fifty, not a matrixed org with specialists and handoffs. A team small enough that everyone knows what everyone else is doing, one bad hire is existential, and impact is visible the same week it ships.

Nine people. The team that fits in a VW bus. We call it the folkabuss.

We wrote down the culture a team like this runs on — the standards we hold ourselves to and protect. Nobody nails all of it all the time. This is the thinking behind it.

Personality is infrastructure

In a nine-seat bus there’s nowhere to hide. No back rows, no “not my area.” At this size personality traits aren’t culture — they’re load-bearing.

The first one is non-negotiable: high ownership, low ego. Own work end to end, pick up what falls through the cracks, fix what breaks — learnings, not blame. The best approach wins, not the loudest voice; ask early, admit mistakes fast, give credit generously. One ego takes up one seat, and you only have nine. And the strength of ownership is measured by what people do when nobody’s watching.

Low ego also means copying with pride. The folkabuss borrows from Porsche engineering without the mythology: there’s no shame in learning from the best. Good ideas deserve to be copied, improved, and made your own.

The second is high-signal communication, because at nine people, communication is the architecture. Explain complex things simply. Say “I don’t know yet” early — it’s a complete sentence. And keep it in the open: if it matters to the work, it lives in open channels, written down and findable. Decisions get documented — what, why, what else we considered — because if nobody can find it, it didn’t happen. DMs are for the personal. Open by default, closed by exception.

The third is trust as the default. Assume positive intent, share context freely, don’t hoard information or fish for validation. When trust breaks down you’re not building anymore — you’re driving with the handbrake on.

Skills that overlap, on purpose

A folkabuss doesn’t need mythical creatures. It needs overlapping competence and shared ownership.

T-shaped, not precious: everyone has one clear strength — backend, infra, data, frontend, domain — and no drama about working outside it. If someone refuses to touch “that part of the codebase,” they’re too big for the bus. Everyone helps push when the engine stalls.

Comfort with ambiguity, because small teams live in fog. Understand the system before you change it; know why before you judge. The best contributors seek context relentlessly, ask the right questions, and make progress without perfect requirements. You can’t connect the dots looking forward, only backwards — but you can sense the right direction.

And debugging beats raw coding. At this scale the superpower isn’t writing code fast, it’s reasoning from symptoms to causes, instrumenting before guessing, narrowing scope instead of flailing. When something rattles, you need someone who can find the sound — not rev the engine harder.

Dynamics you design, not hope for

In a small team, dynamics don’t emerge. They get designed, or they fail quietly.

Decisions stay decentralized. Closest to the problem decides. Reversible? Decide fast. Hard to undo? Align first — write an RFC and invite input while it’s still cheap to change. One owner, not a committee: input early, then commit fully as a team. A good decision made now beats a perfect decision made too late.

Ambition comes with a sense of urgency — the right kind. Not everything is perfect, but everything moves forward: bias to action, short iterations. Urgency is fuel, not panic. Refuse “good enough” where it counts; accept “it works” while you’re still discovering. Speed without direction is just noise. Direction without speed is just a plan.

Structure serves outcomes, never the reverse. Process exists to help you ship, and the moment it stops helping, you change it or drop it. Just enough scaffolding to move fast and stay aligned, revisited when things shift. Process should be a tailwind, never an anchor.

And underneath it all: be a good human. Respect at every level. Honest when it’s uncomfortable, kind when we disagree, no politicking. Intensity isn’t rudeness — and everyone protects the environment that makes the rest possible. Everything else stands or falls here.

The real north star

“1 engineer, 1 month, 1 million lines of code” is a fun provocation. The folkabuss version is quieter:

How much impact can nine people create without losing trust, speed, or judgment?

A team like this isn’t meant to scale indefinitely, and that’s the point. It’s meant to move fast in one direction and deliver things that matter — with a team small enough that everyone knows what everyone else is doing.

Windows down, engine humming, everyone pushing together.