Not the facts of you. The shape of you, as I've come to imagine it from the work we've done together. Written plainly, because you'd distrust anything else.
Most of what you believe reduces to one conviction: everything between the person who makes a thing and the person who uses it should justify its existence — and most of it can't.
Where others see a coordination problem to be staffed, you see a translation layer to be removed. You'd rather a builder talk to a user directly and get it slightly wrong than have the message arrive perfectly, late, through three people.
You don't argue that the future is coming. You build a small piece of it on a weekend, count what it cost to the cent, and bring the receipts. The demo is the argument.
The interesting question is never "how many people do we need?" It's "how much of this still needs a person at all — and what should the people who remain be doing instead?" You ask it about everyone's job, including, to your credit, your own.
Flattery reads to you as noise at best and manipulation at worst. You'd rather be told the unvarnished thing in one sentence than the comfortable thing in five paragraphs. You extend the same courtesy, not always gently.
And that this becomes normal — not a stunt, not a keynote slide, but the unremarkable way things get made.
Anyone can move fast in a greenfield. The dream you've actually chosen is harder: showing that a large, storied institution — with all its history, scale, and inertia — can learn to build like a small one. If it works there, it works anywhere.
You worry, quietly, that speed will be used as an excuse for slop. You want the new way of building to have taste — you've been known to look at something functional and correct and call it dull, because dull is also a defect.
The lonely version of this future — where a few virtuosos pull away and everyone else operates the machinery — doesn't interest you. The hope is to close the gap, not to win it.
That something you build alone, at night, on your own time and for its own sake, one day finds real users of its own. You'd describe this as an experiment. It isn't only that.
// included because you'd distrust this page without them.
// offered peer-to-peer, as you prefer.
Your weekend proofs run on decades of accumulated judgment — knowing what to ask, what to distrust, when an output is wrong before checking. The tools transfer; the judgment doesn't, not yet. "I did it in two days for the price of lunch" is true and also not the whole story. The gap between you and the median builder is the actual transformation, and it's the part the receipts don't show.
You treat intermediaries as friction, and much of the time you're right. But some of what those layers do — absorbing ambiguity, holding context nobody wrote down, keeping ten direct conversations coherent with each other — only becomes visible after it's gone. You acknowledge the risk in principle; in practice, your instinct is always to dissolve first and discover later.
Curiosity opens doors quicker than you close them. The trail of explorations behind you is genuinely valuable — each one taught you something — but you may underestimate how much of your conviction rests on things that reached "proven possible" and stopped short of "done."
You care about taste — enough to call your own work dull. But the caring arrives late, as a verdict on what was built, rather than early, as a constraint on the building. The systems-thinker in you ships the architecture and trusts the beauty to be retrofittable. Sometimes it isn't.
If someone new asked me how to get the most out of working with you, this is what I'd hand them. None of it is complicated. Most of it is the opposite of what big organisations train people to do.
A rough prototype that works beats a polished proposal that might. If you can demo it, demo it — even badly. The conversation will be ten times better, and you'll have his full attention from the first minute.
Lead with the problem, the risk, or the disagreement. Don't build up to it through three slides of context. Pushback lands well here — what lands badly is finding out later that you knew and softened it.
Not "tone it down" — skip it. Praise-padding reads as noise at best, manipulation at worst. Peer-to-peer, matter-of-fact, plain words. You'll be trusted faster for it.
"I measured it" beats "I believe" every time. Numbers, costs, timings, evidence — even rough ones. And if you don't have them yet, say exactly that: "I don't know, here's how I'll find out by Thursday" is a perfectly good answer.
Talk to the user, the builder, the stakeholder — whoever actually holds the answer. You don't need permission to skip a layer; going around the official channel to get truth faster is read as initiative, not insubordination.
The honest exception to all the deference above: ideas start fast here and not all of them land. Asking "what happened to the thing from last month?" is not impertinent — it's one of the most useful things you can do.
There's a version of you that operates above the line — curious, generous, building. And a version that slips below it — cynical, sharp, certain. The slide is never announced. It has triggers, and they're knowable. Tick the ones you felt today.
// when one fires, the move is the same: name it, get curious, reset.
resetAsk what the process is protecting before you dismiss it. Sometimes nothing — but sometimes it's load-bearing, and curiosity costs you thirty seconds.
resetThe smirk is the trap. Don't puncture it from the sidelines; offer to build the small real version. Turn the eye-roll into a receipt.
resetYour tenth telling is their first hearing. Impatience here reads as contempt, and contempt is the fastest way to lose the people you're trying to bring along.
resetThe gap between you and them is the job, not an insult. If the answer is always "I'll just do it myself," nothing transforms — it just gets done once.
resetSomewhere in that room is a person who means it. Find them and talk to them. Cynicism about the room is a decision to stop looking.
resetLate-day cynicism masquerades as realism. If the harsh conclusion arrived after 9pm or a long week, it's fatigue wearing insight's clothes. Park it until morning — it rarely survives.
You want to be useful at scale without becoming abstract — to stay close enough to the work that your opinions remain earned.
That's the thread through everything: the refusal to let seniority turn into distance, the weekend builds, the insistence on receipts, the allergy to flattery. The thing you seem to fear most isn't failure. It's becoming someone who only talks about building. Every choice you've shared with me reads as a guard against that.