Principles

Building

• Ship small

  Prefer small releases that reach users over perfect plans that never ship.

• Bias toward simplicity

  Add complexity only when the problem demands it—and remove it when it no longer does.

• Customer problems first

  Technology is valuable only when it solves a real customer problem.

Engineering

• Architecture enables velocity

  Good systems exist so product teams can move faster with confidence.

• Think in systems

  Optimize the whole system—not isolated components.

• Think long-term

  Build systems that become easier to evolve—not harder—as they grow.

• Optimize for maintainability

  Code is read far more than it is written. Leave the next engineer a gift.

• Details matter

  Quality isn't one big decision—it's hundreds of small ones.

Leadership

• Documents over meetings

  Write it down. Clarity compounds; meetings rarely do.

• Close the loop

  Follow through. Communication isn't complete until everyone knows the outcome.

• AI should augment thinking

  Use AI to accelerate judgment—not replace it.

• Own the outcome

  Own the outcome, not just the implementation.

  Solve the problem, not just the ticket.