The Art Of Coding Disasters And Failures
summary
An exploration of common software engineering disasters, failures and mistakes and how to learn from them to improve continuous development. The talk discusses real-world coding failures and practical lessons to help developers write and maintain better software.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:29Professional errors and lessons
- 6:27First major SoundCloud error
- 15:40Software is terrible
- 17:26Product and process errors
- 20:21Unreadable code and bad practices
- 23:58Variable names and English code
- 25:46Reinventing the wheel
- 28:44Variable and class names
- 31:09Common anti-patterns
- 33:40Design patterns and principles
- 36:14Boy Scout rule
- 38:01Team practices and learning
- 40:51Testing and automation
- 43:20Bug eradication strategies
- 45:11SoundCloud error fix
- 47:18Lessons and team culture
- 49:06Conclusion and final advice
- 50:08Q&A
related talks
44mThe role of catastrophic failure in software design
49mScars, Bruises and Breaks — Programming in Retrospect
27m'The Art of Software Development'
32mOpening Keynote: The Good Bad Bug: Fail Your Way to Better Code
30mYour Code Stinks and You Didn't Even Know
48mAccidentally Complex Development
34mHow do our ideas about coding affect the software we create?
19mTeams. A Failure, a Success