Engineering standards I believe in

Jun 10, 2026

Seed outline — Steven to expand in his own voice.

A running list of standards I hold teams to, and the reasoning behind each.

Make the change easy, then make the easy change

If a change is hard, the first job is refactoring until it’s easy.

Tests describe behavior, not implementation

A test suite should let you change how something works without rewriting every test.

Boring is a feature

Reach for the well-understood tool before the exciting one. Novelty is a cost you pay in operations forever.

(Draft — add the rest of the list and concrete examples.)