You should stop writing code
summary
Argues that fixing code alone rarely improves product outcomes and calls to abandon a code-centric mindset in favor of understanding users, domain experts, and business goals. Shows a concrete refactor: a tax calculation rewritten from cryptic loops into explicit tiered tables that non‑programmers read and validate, reducing ambiguity. Names familiar practices—DDD, TDD, CI/CD, microservices, design thinking—and contrasts continuous agony with true delivery, then centers four actions: communication, collaboration, iteration, incremental to make software actually work.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:02Software dependency risks
- 8:27Code-centric mindset limits
- 16:49Focus on people over code
- 24:28Four key principles
- 33:38Personal and team responsibility
- 37:56Organizational changes
related talks
55mHow To Approach Refactoring
53mIntentional Code - Minimalism in a World of Dogmatic Design
40mGood Code: What, Why, and How to Get There
31mThe Effective Developer - Work Smarter, Not Harder
59mTechniques for writing high-quality code
34mHow do our ideas about coding affect the software we create?
33mClosing Keynote
57mCore Software Design Principles for Programmers