Developers aren't paid to code
summary
Claim is that engineers are paid to solve problems not to code, demonstrated by shifting work from typing to thinking as LLMs and generative models (Stable Diffusion, Flux) handle plumbing and single-file tasks. Practical tactics include use on‑call to learn system weaknesses and prioritize observability so firefighting reveals real UX and business pain. Examples: AI-generated diagrams that need manual cleanup, simple process fixes outperforming code changes, and cross‑discipline skills (basic UX/product) that make engineers immediately useful.
AI-written summary · about
related talks
51mYour worth as a developer: not what you do, but why
05mFull Stack Isn't Enough - The Rise of the Full Product Developer
48mEngineering You
22mThe New Digital Divide: From Vibecoding to Engineering
27mBeyond developer
36mYour Job Is Not to Write Code
15mThe AI Shift: Rethinking the Developer’s Role in a Machine-Driven World
28mBeyond the code: Rediscovering the timeless skills of software engineering in the AI era