Principles

These are working principles. They describe how I aim to work, even when I fall short. Some pull against each other on purpose; applying them requires judgment.

1. Quality, Not Craft

Outcome over Process.

Treat craft as a means, not a virtue. Clean code behind the wrong product is bad work, while an ugly prototype that finds the right answer can be excellent work. Invest in craft only when it improves the result.

2. Swim Upstream

The whole problem over My part.

Do not let roles, systems, or org charts define the problem. Follow it across boundaries until you understand the whole thing. Treat resistance as information, not an automatic reason to stop.

3. Build to Understand

Tested explanations over Untested theories.

Build to discover where your explanation is wrong. Force ideas to meet reality and expose the gaps that discussion can hide. Treat what survives as provisional, but trust it more than an explanation that has never been tested.

4. Speed Is a Strategy

Fast over Right.

Act before certainty arrives. Move first to change the conditions everyone else must operate in and make them respond to your decisions. Move when the downside is survivable, then correct course at speed.

5. No Hurry, No Pause

Composure over Frenzy.

Do not confuse speed with hurry. Reject urgency without direction; it scatters effort and worsens decisions. Move quickly, but stay composed enough to see where you are going.

6. Complaints Must Compile

Making over Commentary.

If something should be better, build the counterexample. Turn criticism into something concrete that others can test and challenge. Make things instead of merely complaining about them.