About
How the work gets made, how the thinking runs, and what the site leaves out on purpose.
How I Build
Methods, not adjectives. "Builder" is a claim proved by how the work happens, not a word in a headline. Each line is a decision made before the first ticket is written.
Interview first.
Never take a request at face value, dig to real intent before building. The right spec answers the right question.
Write specs engineers build from.
Config-vs-code decided up front. Every item resolves to a fixture, a signature, or a runbook, never prose that leaves room to guess.
Map edge cases before the build.
The edge case that slips into production is the one nobody asked about in the spec.
QA with evidence.
A repeatable test method and client-facing UAT packs that carry regression coverage forward every release.
Prioritise by demand.
P0 through P3 by who's actually asking, not by effort. Effort is a cost. Demand is the reason.
Migrate with discipline.
Schema analysis, field mapping, validation, staged execution with review gates. No surprises in production.
Own security.
ISO 27001 gap analysis, Statement of Applicability approver, quarterly compliance reviews. Security is product work, owned from the start, not a checklist handed to a different team.
How I Think
Placed after the work. Earn credibility with shipped scale, then show the operating system behind it. Reasoning, stated quietly, not performed.
- I start from first principles. If the reasoning does not hold from the ground up, the conclusion does not hold.
- I change my mind when the evidence does. Not on every signal, on the pattern.
- I look for what the data is missing. The absence of evidence is where I start reading.
- I watch for coordination failures, situations where everyone does the individually rational thing and the group outcome is bad. A lot of product problems are that, not execution problems.
- The most important data point is the one that never arrived.
What Would Change My Mind
A real list, kept and used, not a rhetorical flourish. If the list never changes, it isn't a list, it's a slogan.
- If a feature I prioritised P0 ships and nobody who asked for it uses it, the demand-driven framework was reading the wrong signal, not just this one call.
- If a coordination failure I diagnosed turns out to be a plain execution gap once I look closer, I revise the diagnosis, not the story.
- If the pattern across three release cycles contradicts the pattern I called after one, the one call was noise.
- If an edge case mapped before a build still slips into production, the mapping process has a hole, not the engineer who missed it.
What's Not Here
The ring stays empty. On purpose.
- Employer and client names. Referenced by scale and sector, never by name.
- Unverified numbers. A stat that can't be checked isn't a stat, it's a guess with a decimal point.
- The next chapter. Route ends at "now," not at a forecast.
Same argument as The Mark below, told twice: once as a diagram, once as a plain list. If a bomber makes it home with holes in the wings, the wings were never the problem.
The mark is a return flight.
In 1943, the US military mapped the bullet holes on bombers returning from Europe, wanting to armour the places hit most. The statistician Abraham Wald turned that inside out: the planes that came back survived those hits, that's why they were visible. Armour instead went where there were no holes, because planes hit there never made it home.
The mark draws that inversion directly: a top-view plane, seven amber hits on the wings and tail, and a dashed ring at the nose, drawn around nothing. The data in front of you is the data that survived: the empty ring is the whole argument.
Wald's actual method — and why the famous bullet-hole diagram is a reconstruction, not his data — is shelved in the Reading Room.
Shelf
Reading that shaped the register. The full library lends: press L.
Not a review list, just the writers whose habits of mind rubbed off. The complete collection, borrowable and searchable, lives on its own page now.
Rationalist-community writing on reasoning under uncertainty. Where the "update on the pattern, not the noise" habit comes from.
Long-form essays that hold an argument from first principles through to an uncomfortable conclusion, then stop.
Writing on AI alignment, read for the discipline of stating a claim plainly and defending it without hedging.
Long-horizon, civilizational-scale thinking. The Kardashev-scale habit of zooming out before zooming back in.