“Clean Code“ is bad. What makes code “maintainable“? part 1 of n

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