Useful, or it doesn't ship.
BuildUseful builds for problems that already exist, and knows how the thing works before it ships. Not the future. Tuesday.
Start with what's in front of you.
Why this exists
Something is making us forget how things work. The tools got good enough to ship without understanding, and a lot of the industry took that deal. The ticket closes, nothing is kept, and the outage at 3 a.m. doesn't care how senior anyone is.
BuildUseful exists to not take the deal. We build small, solid things for problems that are already here, and we insist on understanding them all the way down: how it works, why it was decided that way, what happens when the thing underneath it fails. That understanding is part of what we hand over.
The problems are still the Tuesday kind. The chore nobody automated, the spreadsheet quietly holding a business together, the eleven tools that refuse to talk to each other. Real problems are cheaper to find than imaginary ones, and a lot more satisfying to fix.
The longer version, with the questions it leaves open, is on the Kept page.
The schematic
Seven rules, soldered in. Every build goes through all of them.
- Input, real problems only
Start with what's in front of you.
Not the market. Not the roadmap. The thing that annoyed you this morning. Real problems come with real people attached, which is the only reliable way to know whether you fixed anything.
- IC, understanding, all the way down
Understanding is part of the deliverable.
The tools can ship without it now. We can't. A test is just understanding, written down and run. A runbook is the same thing, written down and kept. If we can't explain how it works, it isn't done.
- Resistor, 10kΩ, hype
Boring is a feature.
A light switch gets used a thousand times a day and nobody claps. That's the goal. If it needs a launch to be interesting, it probably isn't useful.
- Capacitor, holds up at 3 a.m.
It has to work when nobody's watching.
Software that needs a babysitter is a hobby. We build for 3 a.m. on a weeknight, not 2 p.m. on demo day. Logs, retries, and a plan for the day the API changes.
- Diode, scope flows one way
Say no, kindly.
Most requests are for more features. Most needs are for fewer. A diode only lets current through in one direction. Scope works the same way.
- Transistor, clean handoff
You can run it without us.
Source, docs, and the boring runbook. If we vanished tomorrow, your stuff should keep working. No hostage situations.
- Switch, rated for small hands
Survive a household first.
Kids, dogs, and a grown adult who will absolutely not read the manual. If it holds up there, an office is easy.
- Buzzwords, 0×
Not populated. Never will be.
How a build goes
Signal in, useful thing out. Four stops, no detours.
Look
We watch the real problem happen. It's usually not the one in the brief.
Build the smallest useful thing
A week, not a quarter. Something you can touch by Friday.
Hand it over
Source, docs, runbook. It's yours. It was always going to be yours.
Fix it when it breaks
It will. That's what the runbook is for, and why we pick up the phone.
Why an owl?
Owls work nights. They notice what everyone else misses, they don't make a lot of noise about it, and they are famously unimpressed.
Also, the logo was already an owl. We're not going to fight the logo.
Have something in front of you?
Tell us what's broken, boring, or held together with a spreadsheet. If we can make it useful, we'll say so. If we can't, we'll say that too. That's also useful.