Workflow2 June 2026
· 7 min read
Every engineer knows the failure mode that doesn’t show up in a velocity chart: the project that quietly dies in a debugging dead-end. Not the feature that took longer than estimated — the one that hit a wall nobody could climb. A config that won’t load and won’t explain itself. A race condition that vanishes under a debugger. A dependency two layers down that’s subtly wrong. You burn a day, then a weekend, then you stop opening the repo. The project isn’t behind schedule. It’s dead.
Ai2 June 2026
· 6 min read
There is a specific moment, somewhere in the last eighteen months, when the coding agent stopped doing what you told it and started telling you what it would do instead. You write a one-line prompt. Instead of immediately editing six files, it pauses, reads the codebase, and comes back with: here are three ways to do this, here’s what each one costs you later, which do you want. That pause is the whole story. It is the difference between an engineer who runs with the first interpretation of a ticket and one who has been burned enough times to ask the question behind the question.
Disruption2 June 2026
· 6 min read
Stop watching your largest competitor. They are not the thing that kills you. The thing that kills you is the four-person company that looked at your industry, noticed exactly how slow you move and exactly how much margin you take, and decided that gap was a business plan.
Engineering2 June 2026
· 7 min read
For most of software’s history, the engineer was the part. You were measured by what came out of your hands: the pull requests, the features, the lines that shipped. That measurement is breaking. The unit of engineering value has moved up a level — from the output you produce directly to the system that produces output for you. The question is no longer “how much did you build?” but, as the framing goes, are you producing the factory that would produce multiplicative outputs?
Ai-Agents2 June 2026
· 7 min read
Here is the shift worth taking seriously: the unit of labor inside a company is quietly moving from the task to the agent that does the task. You don’t write the support reply, draft the contract, or close the ticket. You stand up, brief, and babysit the thing that does. Your output stops being the work product and becomes the agent’s reliability. If that holds, it rewrites the job description of nearly everyone in a knowledge org, and it does so faster than any reorg memo can keep up.