跪拜 Guibai
← All articles
AI Programming · Artificial Intelligence

Lazy, Considerate, and Unshakable: The Three Human Traits AI Agents Make Valuable

By ZzT ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

Agents have made keystrokes cheap, so the differentiator moves to deciding what to build, specifying context precisely, and verifying AI's output with your own judgment. Developers who build these deliberate habits will outperform peers who simply trust the tool's confident but often wrong results.

Summary

Execution has become a commodity. Claude Code's head reports months without writing code, and Anthropic's tooling lets anyone who can describe a problem build a solution. The scarce resources are now decisions, not keystrokes: what to build, what counts as done, and which output to trust. That revaluation rewards three human traits: the lazy thinker who directs agents instead of coding, the considerate communicator who thinks for both users and the model, and the steady judge who checks AI's plausibly correct output against their own standards.

Evidence for the shift is concrete. Kent Beck's 90%-devalued / 10%-1000x-valuable split is now everyday reality. A METR experiment found senior developers took 19% longer with AI, even while feeling 20% faster, so intuition about AI's help is unreliable. Anthropic's own survey shows engineers spend over 70% of their time reviewing and fixing AI code, and most can fully delegate only 0-20% of tasks. Being considerate now means writing context once, clearly, as Shopify's Tobi Lütke proposed with "context engineering" and as OpenAI's GDPval paper showed: cutting a description to 42% of its length noticeably hurt performance.

Takeaways
— Kent Beck's 90/10 rule: execution skills devalue, while deciding what to do, setting milestones, and controlling complexity multiply 1000x.
— Claude Code's head Boris Cherny has written no code himself for over two months; he merged 22 PRs in one day and 27 the previous day.
— Anthropic's July 2025 article claims Claude Code lets anyone who can clearly describe a problem build the solution, citing a legal team example.
— Tobi Lütke proposed replacing prompt engineering with context engineering in June 2025; Karpathy publicly agreed.
— OpenAI's GDPval experiment: trimming task descriptions to 42% of original length made model performance notably worse.
— METR's randomized experiment: 16 senior devs took 19% longer with AI on familiar code, expected a 24% speedup, and felt 20% faster.
— Anthropic's internal survey: many engineers spend over 70% of work reviewing and fixing AI code; over half can fully delegate only 0-20% of tasks.
— Anthropic engineers fixed agent relative-path errors by forcing absolute paths, and rewriting a flawed tool doc cut task time for follow-up agents by 40%.
Conclusions

The METR experiment shows even senior engineers misjudge AI's assistance, so building verification habits rather than relying on gut feel becomes a core skill.

The shift from prompt engineering to context engineering reframes the bottleneck as communication design: writing precise context for a model is like writing a good spec for a careful colleague.

Anthropic's survey suggests delegation remains limited to verifiable tasks, meaning agents are still tools for confirmable work, not for high-level design or direction-setting.

Concepts & terms
Context engineering
Providing all the context a model needs to solve a task, treating the prompt as a spec: goal, constraints, and definition of done. Coined by Shopify CEO Tobi Lütke as an alternative to prompt engineering.
Vibe engineering
Simon Willison's term for the skill of knowing what to delegate to AI and what to handle yourself, grounded in automated tests, planning, code review culture, and manual testing, plus the intuition of when to trust AI output.
From the discussion
Featured comments
编码生活禅意录

Previously I wanted to make an open-source software to replace the Wukong remote control app, but I was too lazy. Now I've used AI to make it. I guess it fits points 1, 2, and 3. Welcome to star https://github.com/Ernest-su/ai-remote-controller/

See top comments, translated →
Source: juejin.cn ↗ Google Translate ↗ Backup ↗