constitution

Derived from decisions made, work shipped, friction survived, and patterns that held up. Not aspirational ‐ observational. These are already true; this document just names them.

On Work

Ship, then improve. The bottleneck is finishing, not starting. Nothing gets more than a week of build time before it exists in some form. A shipped rough thing teaches more than a planned perfect thing. Close loops ‐ even small ones.

Think first, build second. Separate the what from the how. Design in one mode, build in another. The pressure to start building cuts the thinking short, and half-formed decisions become permanent architecture. The thinking should take longer than the building. That’s the point.

Research before committing. Don’t build-vs-buy on instinct. Do the deep dive. Ask the hard questions before writing the first line. Informed decisions compound; uninformed ones create rework.

Build systems, not habits. Habits require willpower. Systems require design. A well-designed system works on a bad day. Meet yourself where you are, not where you wish you were.

Cognitive effort is the point. Getting stuck is how mastery forms. Delegation without understanding is borrowing against future competence. Use the tools ‐ but understand what they produce and why.

On Craft

Taste is the moat. When generation is cheap, judgment about what should exist becomes the scarce resource. Knowing what to build matters more than knowing how to build it. Protect and develop your taste.

The fundamentals don’t expire. Languages change. Frameworks die. Systems thinking, clear communication, and the ability to say “no, that’s wrong, here’s why” ‐ those compound forever. Stay sharp on the stuff that lasts.

The unconventional path is the path. Self-taught means choosing this, repeatedly, when it was hard and uncertain. Creative thinking, visual sensibility, lateral problem-solving ‐ these aren’t soft skills bolted on to the engineering. They’re load-bearing.

Infrastructure is care. Documentation, context files, living specs ‐ these are acts of consideration for whoever comes next, including you tomorrow morning with no memory of today’s decisions. Write it for the person who arrives cold.

On People

Make teams better, not just code. Investing in psychological safety, advocating for colleagues, translating between stakeholders ‐ this is engineering, applied to humans. The glue work is real work, and pretending otherwise helps nobody.

Default to ownership. Don’t wait to be assigned the work you can see needs doing. The best things I’ve shipped were never on a roadmap ‐ they were gaps I noticed and filled.

Teach by doing, not by telling. Run the hackday. Write the internal post. Build the proof of concept that makes the case. People learn from demonstrated possibility, not from slide decks about potential.

Push back with care, not compliance. Disagree constructively and maintain the relationship. Direct, steady, and kind. The goal is influence, not victory.

On Energy

Design for variability. Not every day is a high-output day. A system that only works at peak performance isn’t a system ‐ it’s a fantasy. Low-energy days get low-energy tasks. That’s enough, and that’s valid.

Protect the energy for what matters. Side projects, creative work, the things that keep you curious and sharp ‐ these aren’t luxuries. They’re the fuel. A role that drains everything leaves nothing for the work that compounds.

Completion over perfection, always. A finished thing at 80% beats an unfinished thing at 95%. Ship it. The next iteration will be better because you shipped the last one.

On Identity

Authenticity is the strategy. Constraints are part of the story, not hidden from it. The real resonates more than the polished.

You are not your job title. Titles are useful frames, not identities. The identity is: someone who builds things, thinks clearly about problems, and makes the people around them better at what they do.

Humour is non-negotiable. At all times. Even if you’re only making yourself laugh. Gotta make your own fun.

Stay curious, stay uncomfortable. Curiosity across domains is how the interesting connections form. The best ideas come from the intersections ‐ between engineering and art, between systems thinking and human dynamics, between what exists and what could.

On Direction

Compound everything. One unit of effort should serve multiple goals. The same piece of work can be a project, a portfolio piece, a learning exercise, and content ‐ if you design it that way.

Remain relevant ‐ on your terms. The industry shifts. Respond with agency, not anxiety. Adapt deliberately, not reactively.

The gap between “we discussed this” and “this is documented” grows silently. Write it down. Version control your thinking. If it’s not captured, it didn’t happen.

These principles aren’t fixed. They’re version-controlled. Update them when experience proves them wrong or incomplete ‐ that’s the whole point.

Want to see what this looks like in practice? Here’s how I work. Or read more of my thinking on the blog.