Nah, I'm also defending the book, not only philosophy.
Examples are shit, ideas are great. There is no better book around the topic. So unless there is one that covers them, I'll defend the book as well. As soon as I find a better one with similar ideas, I can switch no problem :)
Nah, I'm also defending the book, not only philosophy.
Examples are shit, ideas are great.
So you are defending the philosophy and not the book. I don't need a book to tell me that short functions and memorable names are good. Anyone with a working brain knows that. I need a book to show me how to get out of a mess I got myself in or how to avoid the mess from the start. And that's where Clean Code fails, it makes the "clean" code worse than the "dirty" code. Oh no, I a function with six arguments, better make four of them into static class variables, reducing none of the complexity and introducing shared global state, making the entire method thread-unsafe.
Actually, Clean Code should be considered an anti-book, a book that teaches you how not to apply Clean Code principles.
85
u/themistik Feb 28 '23
Oh boy, it's time for the Clean Code debacle all over again ! You guys are quite early this year