The feature your users are already faking
The one real user of my photo tool was already faking a feature with a workaround. That workaround was the specification.

The one real user of my photo tool was already faking a feature with a workaround. That workaround was the specification.

Burned out more than once across twenty years, and the point is that none of them looked the same as the one before it.

A Rust scaffolder with an AI codegen path that drafts a real command, then refuses to hand it over until it compiles and passes lint.

A correction to my own post: the culler does contain machine learning, and the distinction I drew between ML and AI does not survive scrutiny.

Running three different coding agents against one repository, and the house rules that stopped them undoing each other's work.

Hiring engineers for judgement rather than output, and why every part of a normal interview is measuring the wrong thing.

Building on your own framework means finding its gaps as a user rather than an author, and having to file the request against yourself.

Refereeing the memory-safety retrofit argument from someone who ships framework code in both Rust and Go, and likes them for different reasons.

Generating a Go command from a shell script or a plain sentence, and the repair agent that has to make the result build before you see it.

The case for a head of engineering staying hands-on, written as a confession rather than a boast, because the compulsion is the problem.
