We write to say something — not to stay visible.
We’d rather work an idea until it’s clear than publish on schedule. What ends up here is a record of what we’re learning as we build Orbrik.
Read our thinkingClarity compounds.
Writing forces an idea to become clear — you can’t hide a vague thought inside a finished sentence. When something we’ve learned holds up on the page, it’s worth leaving where someone else can find it.
Themes, not categories.
- Building productsHow good software actually gets made.
- Operating companiesThe unglamorous work of running one, or several.
- DesignCraft, restraint, and why the details matter.
- Decision-makingHow choices get made — and remembered.
- Organizational memoryThe idea Orbrik is built on.
Not every idea earns the page.
An idea earns its place here when it’s true, when it has been tested against the work, and when it’s clear enough to help someone who wasn’t in the room. If it’s only clever, we keep working on it.
Nothing here yet — and that’s deliberate.
We publish only when we have something worth saying. The first pieces are being written; they’ll appear here when they’re ready, and not before.
Good thinking takes its time.
When there’s something worth sharing, it’ll be here. Until then, the clearest picture of what we believe is the thing we’re building.
See why we’re building Orbrik