the name is the practice. the best engineering is the work you don't do. the feature you don't ship. the abstraction you don't add. the dependency you don't take on. what's left is the thing.

the principle

Hemingway. you can omit anything if you know it. the omitted part strengthens the story. the iceberg, mostly underwater. the reader feels the weight.

the same idea, applied to software. systems that hold up are the ones where every line earns its weight. systems that don't are full of code added because someone could, not because someone should.

Lao Tzu called it wu wei. action through non-action. knowing what to leave out.

the practice

omit takes the operational knowledge a business has built up. the runbooks, the senior people, the loop that keeps the business running. we encode it into software. then strip away everything that doesn't need to be there. what's left is the system the team can stop carrying.

how we engage

discover → build → operate. most projects start with a fixed-price discovery, or a discovery and build bundle, and settle into a monthly operate retainer. some clients add fractional advisory when they're scaling. a few problems a year, shaped carefully.

who this is for

we work with teams who already know what they're building. we don't write briefs for spec-shoppers, ship single landing pages, or run marketing retainers. if your brief reads like a tender, we are not it.

principal

robin lange. engineer. auckland. ten years building product systems on platforms that handled real money, real privacy, and real scale.