#deep-dive
Every post tagged "deep-dive".
107 posts · showing 31–40
-
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.
-
What Changes for Engineering Managers
Four management assumptions break at once: that output tracks effort, that capacity is headcount, that people learn by doing, and that review is a small tax. Each breaks differently.
-
What Changes for Product Managers
A role that existed partly to ration scarce engineering capacity changes when capacity stops being scarce — and the discipline of saying no gets harder, not easier.
-
The Use Cases Agents Genuinely Solve Today
A criterion beats a list: complete inputs, a mechanical check, bounded blast radius. Everything clearing that bar is working in production — and the largest realized value is the least discussed.
-
Data Work Gets More Valuable, Not Less
The buffer between bad data and consequences was a person who noticed the number looked wrong. Agents act on it — which turns data quality from an analytical property into an operational one.
-
What Happens to QA When Agents Write the Tests
Cheap test generation makes suite quality matter more, not less — because the default outcome is a large, green suite that verifies nothing. Someone has to own whether it catches things.
-
Evaluation Engineer: The Job Description Writing Itself
The furthest-formed of the emerging roles: well-defined, consistently needed, consistently unstaffed. It's everyone's dependency and nobody's job, which is exactly why.
-
Agent Operations: The Role Without a Title Yet
Someone in every agent-running organization does this job without being hired for it. It has no name, no allocation, and no incident that forces it — until whoever was doing it informally leaves.
-
The Jobs That Get Created Are Hard to Name in Advance
"New jobs will be created" sounds like faith because the examples are missing. There's a structural reason for that — and one observable signal that's better than any forecast.