In my "Top 10 Software Developer Books" video, there was a lot of discussion about "Clean Code."
It's horrible. It's based on flawed assumptions, and it makes code harder to maintain. In this video I'm going to talk about some specific examples that Clean Code gets wrong, the workflows it prevents, and a bug that took me days to find that Clean Code's STUPID recommendations can cause.
I'll also discuss what "maintainable" really should mean.
There's no way I can cover everything wrong with this book (or everything you need to know to write maintainable code) in one video - so expect more of these.
00:00 Most "clean coding" advice is bad
01:24 "Clean Code" is trash
02:13 Thing like "Clean Code" only serve to create arguments
02:42 "Maintainable" is judged by people other than the programmer writing it
03:25 "Maintainable" code is useful when you do something else for a while and then come back
03:35 Code is not read top to bottom like a book
05:13 Real programmers read code from the bottom up
07:00 "Clean" codebases tend to obfuscate bottom-up reading
08:43 Vertical slices of code
09:40 Root of much programming advice
10:09 Welcome to Whack-A-Mole
11:38 Specific Example - Real Bug (details changed, yada yada)
14:26 The bad assumption in most coding advice: Bugs are preventable
15:28 A bug that's hard to reproduce means the code is bad
16:43 The real point of maintainable code
17:11 Rant
17:55 Wrap up
