Posts Tagged "Engineering"

Maintainability Against the Unknown Unknowns

At Terrace, curating the world's crypto market data, something like 71% of what came through the door was noise or outright fraud — and the worst of it was stuff we could not have imagined if we'd sat down and tried. You cannot filter garbage you have never seen. So you stop trying to predict the input and start building the thing that absorbs it in ten minutes flat. That isn't cleverness. It's enforced lint and tests and clean boundaries — maintainability as a weapon against the unknown.

The Balanced Org

Separate offense (product, engineering, sales) from defense (infrastructure, IT, security, compliance), hold them as peers in dynamic tension under the CEO, and put the right temperament in every seat. A visual essay on org design — and why no single 'balanced' leader can hold both halves of the job at once.

The Digital Plumber

Ask an SRE what they do and you'll get a hundred answers. Here's mine: we wear three hats — advisor, plumber, and firefighter — and not one of them is 'product.' We are the people who make sure the product can be built cheaply, shipped reliably, and kept alive at 3 a.m., whatever the product happens to be. Because after enough years, you stop seeing products at all. You just see systems, and bytes moving through them.

Chasing Nines

Your availability target — how many nines you promise — isn't a line in a contract, it's an architecture decision. Get it wrong in one direction and you fail the SLA you sold. Get it wrong in the other and you burn money buying nines you never promised. I once looked at a stack paying $10,000 a month for high availability it did not actually have.

Writing for Generation Ships

The best professional compliment I ever got was that I should be writing code for generation ships flying to Alpha Centauri. It came from someone who spent years defending a system I built, against people actively trying to destroy it, armed with nothing but links to my code and documentation. I was not there. That is the whole point.

'Production Ready' Is a Hand-Off, Not a Launch

The moment you hand a service to the people who run production, 'it works' stops meaning 'it works on my machine' and starts meaning 'someone who has never seen this code can keep it alive at 3 a.m.' Production readiness is that hand-off contract — and almost every item on the checklist traces back to one question: what does the on-call engineer need to survive the night?

Your Hiring Pipeline Has the Same Bug as Your Deploy Pipeline

A résumé parser matches tokens, not competence. It's the same mistake as infrastructure that describes state instead of maintaining it, and the same mistake as confusing 'can' with 'does.' Keyword-gated hiring optimizes a proxy and quietly filters out exactly the senior people it claims to want.

Load-Bearing Humans

A system that only keeps running because a person is continuously holding it up is not working. The person is working. The system is on life support. 'Working' is one more overloaded word, and most of the time it quietly means 'works as long as the right human is standing there.'