Clean Code - worth doing your job properly

I haven’t read many coding books outside of uni, so Clean Code felt like the natural place to start. It turned out to be an easy 5/5 for me.

The book landed differently because I’d already spent a few years doing TDD and trying to write good code. Reading it with that context was great, and the code examples, stories and heuristics the author includes really cement his points.

My overall takeaway is simple: it is worth doing your job properly. It’s much easier to write something and promise to “fix it later”, but often that time never comes. Six months down the line you’re fighting your own code every day and having a terrible experience. I know because it happened to me. One of my first bigger projects was a game called Arrowtale, about 40k lines of C# I wrote as a junior programmer. I took a break, came back months later, and the code was basically impossible to work with. I ended up starting over instead.

This book is full of ways to avoid that fate. The part I liked most was the few dozen code smell heuristics the author lays out, each with an explanation of why it’s worth looking out for. The examples are all Java, but at least 80% of the book transfers directly to web development.

It changed how I work too. I started using type checking and auto formatting in Python, which catch bugs and keep the code consistent. And now that AI writes so much of our code, it has held up more than ever. I get the AI to apply even harsher standards than I held myself to, and I hunt for smells more than I ever did.

Who’s it for? Honestly, anyone who codes. Even a senior dev will find things they haven’t seen. The only person I’d warn away is someone who has never coded, because the book needs context to land.