Engineering, Leadership, Reality

Long-form writing on systems, people, and the predictable chaos they create.

startupsleadershipgovernanceengineeringexecutionincentivesproductteamsAItechnologyeconomicsarchitecturesystemsrelationshipswritingcareersethicsorganisationssoftwareorganisation
Local Rules Create Complex Systems

Local Rules Create Complex Systems

If starlings don’t use telepathy to move as one, why do so many leaders still think complex systems need a central brain?

Reality Does Not Negotiate

Reality Does Not Negotiate

Good engineering is the habit of aligning with reality early, testing assumptions before the world corrects them expensively.

Evil People Don't Exist

Evil People Don't Exist

Most harm is not caused by people who think they are evil, but by people whose conviction has stopped receiving feedback.

Why I write

Why I write

Public writing makes your operating philosophy visible. That visibility closes some doors, but it also attracts the people and organisations most aligned with how you think.

Refilled: How we work

The onboarding introduction that I used at Refilled. It's a cheatsheet to existing within the organisation.

You get what you tolerate

Small compromises don’t stay small. In business and personal relationships, what you allow quickly becomes the baseline.

Teams need a shared identity

Teams need a shared identity

A reflection on Tom DeMarco, startup teams, and the hard-earned lesson that trust, belonging, and a shared identity matter more than process ever will.

Syncromesh, Koya, and the Helix Split

Syncromesh, Koya, and the Helix Split

Syncromesh was built to run a distributed game simulation. Koya split off to serve embedded UI. When the two diverged too far to share a codebase, the useful parts were pulled down into Helix.

The Moment a Startup Starts Serving Investors

The Moment a Startup Starts Serving Investors

There is a point where a startup quietly shifts from building for customers to performing for investors. No one announces it, but the work stops compounding and the system begins to degrade.

Racing Engines, Aircraft Engines

Racing Engines, Aircraft Engines

Startup culture glorifies short bursts of heroic effort, but durable organisations are built more like aircraft engines than race cars: through limits, maintenance, and reliability over time.

Professional Credibility Is Engineered

Most people cannot assess technical work directly, so credibility is built through visible signals of order, clarity, reliability, and professional presentation.

This Is the Future of AI

This Is the Future of AI

The future of AI isn’t infinite scale; it’s focused utility: small local models that replace friction and quietly integrate into the stack.

The Board Is Not Your Enemy, Unless You Make It One

Boards don't become adversarial by default. They become adversarial when founders avoid structure and force governance to emerge through intervention instead of design.

When Structure Fails, Conflict Fills the Gap

Most conflicts between technical leadership and business development aren't personality clashes. They're structural failures caused by unclear authority, blurred domains, and leaders who won't respect boundaries.

It's more important to have a motivated employee than a perfect product.

If you want ownership, you have to give people the authority to make decisions; even when you think they might choose wrong.

The Myth of 'Build It and They Will Come'

A startup without hustle defaults to building in the dark, convinced features replace customers. They don’t.

ESOPs Are Not Remuneration

ESOPs Are Not Remuneration

ESOPs get sold as part of your compensation, but structurally they're not pay. They're discretionary, illiquid side-bets that shift risk onto employees without giving them real value or power.

Why Founders Struggle With Letting Go

Founders often believe their personal involvement is what keeps the company alive. That may be true early on, but it becomes the bottleneck that stops the organisation from maturing. Letting go isn’t emotional; it’s structural.

The Cost of Technical Debt Isn’t Technical

Technical debt shows up in code, but its real impact is on how people work, think, and interact. The cost is paid in trust, morale, and predictability long before anyone starts refactoring.

Startups Don’t Fail from Lack of Vision; They Fail from Lack of Structure

Most startups don’t die because they lack big ideas. They die because they never build the structure needed to turn those ideas into reality.