#future-of-work
Every post tagged "future-of-work".
57 posts · showing 1–10
-
What Ten Years of Agent Tooling Might Look Like
Specific capability predictions age badly; layer predictions age better. Which parts commoditize, which stay differentiated — and the one prediction here most likely to be wrong.
-
The Skills That Were Always the Job
Almost nothing on the durable list is new. These are what experienced engineers always said mattered — the economics just didn't reward them proportionately until now.
-
Reading the Agent Discourse Without Being Misled
Two questions handle most of it: what specifically was the input, and what specifically checked the output? Almost every overstated claim is weak on one of them.
-
The Economics of an Agent-Heavy Team
Several line items move and only one of them is tokens. The savings are real, land on a single term, and are partly consumed by four others that grow — which is why big speedups produce modest delivery gains.
-
The Documentation Problem Agents Create
Documentation has two audiences with different needs, and generated docs that restate the code become negative value the moment they drift — a confident wrong answer with an authoritative source attached.
-
Open Source After Cheap Contributions
Contribution effort rationed demand for maintainer attention. That rationing is gone and the attention is unchanged — but the filters that work test for something effort was only ever a proxy for.
-
Why Your Codebase Will Grow Faster Than Your Understanding
Writing code built understanding as a byproduct, which is why "the team knows the system" used to be true without anyone planning it. That coupling broke and only one of the two rates changed.
-
Technical Debt in the Age of Cheap Code
The old rules assumed writing code was the expensive part. When it isn't, imperfect implementations matter less and surplus surface matters more — and the create-versus-remove asymmetry gets worse.
-
Onboarding Into a Codebase Nobody Fully Read
"Ask whoever wrote it" assumed someone did. Where code arrived complete in one commit and was approved rather than authored, the history holds no reasoning — and onboarding is where you find that out.
-
Hiring Engineers When Take-Home Tests Are Meaningless
The signals didn't get noisier — they stopped measuring what they proxied for. The replacements test the right thing and are more subjective, which is a cost that lands on specific people.