Posts connected by the shift-left tag.
4 posts
Engineering quality is a property of what ships. Quality engineering is the practice that produces it, and that practice cannot be handed to another team. Quality, security, and documentation belong to the engineer who builds the thing, and the reward system has to pay for those behaviors or they quietly stop.
The first 80% of a feature gets the demo, the congratulations, and the promotion packet. The last 20% (the part that makes the thing actually usable) costs a magnitude more and is rewarded far less. The reason is structural: every additional nine of reliability is a different engineering problem than the one before it, and you cannot reach it by extending a design that was never built for it. In the age of AI, when the token cost of writing the scalable version is roughly the token cost of writing the disposable one, the V1-then-rewrite habit deserves a second look.
Why is the directive and How is the action, which leaves out the entire middle. Who, What, When, and Where are the locating step: four separate questions, each with its own failure mode, that tell you where you are standing before you move. Splitting them out of the How is what makes the whole model work.
Agentic tooling made pull requests cheap and plentiful, so the bottleneck moved from writing code to trusting it. The answer is not another review loop but front-loaded rigor: invest the engineering effort ahead of time to build a full, production-shaped synthetic environment you run locally, so that validation itself becomes cheap and the PR turns into a context-sharing mechanism instead of an approval gate. Tools like .NET Aspire and Dapr show what that inner loop can look like, and the same principles carry over to homegrown systems.