Software-Engineer

Sustained AI dependence erodes the skills the tool augments — invisibly, because the tool compensates for the decline it causes. The retention curve, and the fix.

This week's top agent papers stop treating memory and runtime state as afterthoughts and start treating them as systems — with tiers, costs, and audit trails.

This week's AI signal points one way: as code gets cheap and disposable, the binding constraint becomes engineering discipline — memory, stress, isolation.

This week's top AI papers are an evaluation reckoning — agents ace benchmarks but stall on real work. What that means for engineers shipping agents.

Anthropic's Fable 5 is the most capable public model yet — a new Mythos-class tier above Opus. The reflex is to route everything to it. Here's why the disciplined move is the opposite, and the two routing skills I rebuilt the day it shipped.

This week's top AI research is infrastructure: cheaper inference, agent safety frameworks, grounded search. What it means for engineers shipping agents.

Your CLAUDE.md is a monolith, not an architecture. Context tiering — hot/warm/cold by access frequency — gives an agent persistent context without drowning it.

Reviewers feel more positive about AI code that's objectively worse — that's gate erosion, now peer-reviewed. The 2026 evidence and the protocol that stops it.

The Fluency Trap is the reason skilled engineers can't see the architectural drift accumulating in their AI-assisted code. The mechanism, the evidence, the fix.

The same prompt produces a different architecture 75% of the time — that's convention drift, the first form of the Borrowed Architecture. The research and the fix.