#future-of-work
Every post tagged "future-of-work".
57 posts · showing 41–50
-
When the Requirement Itself Is Wrong, Who Notices?
The behavior was intentional, decided two years ago, documented somewhere nobody looked. Every stage faithfully executed a wrong ticket — and every automated check confirmed it, by construction.
-
The Meeting an Agent Can't Attend
Requirements aren't transmitted in those rooms, they're constructed — out of inputs that exist nowhere beforehand and mostly aren't recorded after. And the efficiency instinct cuts exactly the wrong thing.
-
Accountability Cannot Be Delegated to a Model
"The agent decided" answers nothing — not legally, not organizationally, not to the person affected. What accountability actually requires has design consequences, including why a rubber-stamp gate is worse than none.
-
Taste Is a Bottleneck: Where Judgment Has No Substitute Yet
Cheap generation doesn't reduce the value of judgment — it makes discrimination the scarce step. And it introduces a hazard: well-argued cases for mediocre options, which is what agents produce uniformly.
-
The SDLC Steps That Resist Automation Longest, and Why
Order the lifecycle by automatability and it doesn't track difficulty at all. Two properties decide it — and the steps that resist are short, frequent, and where all the leverage sits.
-
What Employers Pay For When Code Itself Is Cheap
Companies were never buying code exactly, but code was a big enough share that the distinction rarely mattered. Five things remain when it's cheap — and the proxies that used to demonstrate them stop working.
-
Who's Genuinely at Risk, and Why It Isn't About Seniority
The assumption is juniors are exposed and seniors are safe. The real variable is production versus judgment — which leaves some senior engineers in the exposed column and some juniors out of it.
-
The Fear Is About Identity as Much as Employment
Push past "will I have a job" and something else surfaces: the thing you spent a decade becoming excellent at is now less scarce. That's a different problem, and it answers to different things.
-
Output Went Up, Review Capacity Didn't
PR volume doubled and review capacity didn't, because review is human and got no faster. The number to watch isn't merge throughput — it's how fast approvals are arriving.
-
What Actually Got Automated Away in Previous Software Waves
"Automation always creates more jobs" is too coarse to use. What each previous wave specifically removed — and what it left — is a much sharper predictor, and this wave's profile mostly matches.