GG

I build software for healthcare, and I work in healthcare. That is the entire proposition: the person designing the data model has also been the person filling the form in at three in the morning, on a bad connection, with someone waiting.

It turns out that changes what you build. Most clinical software is designed by people who have never had to use it under pressure, which is why so much of it assumes a signal, a spare hand and a calm room. I start from the opposite assumption — no network, no second attempt, and a user with more urgent problems than your interface.

In practice that means offline-first by default, encryption at rest that is actually enforced rather than promised, sync that reconciles instead of overwriting someone else's work, and records that survive being asked who wrote what and when. Unglamorous, and it has to be correct.

The same instinct runs through everything else: things that are small, quiet and hard to break. The site that still loads in four years. The logger that keeps writing after the battery turns rude. Not the biggest build — the one still standing.

The name is a family joke that got out of hand. Coffee before dawn, beer after a long one, something compiling in between. It all counts as brewing.

• BUILDS Clinical apps, durable websites, and hardware that reports back.
• KNOWS What actually happens to software once it reaches a real shift.
• ALWAYS Something on the stove that nobody asked for.