Why Clean Code Is Not the Norm?
summary
Argument: clean code remains rare because it costs attention and time up front, mentorship cannot scale as developer population grows (25→30M developers now, ~40M by 2030), and businesses cut internal quality to hit scope/time/cost. Concrete claims: writing things the right way beats doing the right thing short-term — research shows better midterm outcomes over three years — and a practical habit is the half-time refactor technique (spend 2.5 of 5 days cleaning before building). Expected actions: small continuous cleanup, teach juniors, say no when necessary, and lead by example.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:25Talk agenda
- 3:10Software quality defined
- 9:56Clean code traits
- 15:27Clean code and quality
- 18:00Why developers skip clean code
- 23:01The business impact of unclean code
- 24:03Right thing vs done right
- 26:57Who is responsible for the lack of clean code
- 31:17Senior devs and clean code
- 33:10Our job as software engineers beyond coding
- 37:02When and how to say no in development
- 41:43Leave code better
- 43:51Clean code practices
- 45:43Conclusion and call to action
