5.0 out of 5 stars Java

S.A. · May 8, 2025

(function() { P.when('cr-A', 'ready').execute(function(A) { if(typeof A.toggleExpanderAriaLabel === 'function') { A.toggleExpanderAriaLabel('review_text_read_more', 'Read more of this review', 'Read less of this review'); } }); })(); .review-text-read-more-expander:focus-visible { outline: 2px solid #2162a1; outline-offset: 2px; border-radius: 5px; } I read the book Clean Code and really liked it. I learned how method and class names should be written, and I’ve started applying those principles in practice. It’s truly one of the most outstanding books, and every developer should read it.

5.0 out of 5 stars A must read!

S. · May 26, 2025

A must read for aspiring software developers.

5.0 out of 5 stars Excellent for the whole team

P.J.H. · December 29, 2015

As CTO of a software company I co-founded, I'm not only looking for books that help me improve individually, but also books that the whole development team – from developers to architects – may find useful. Robert C. Martin’s Clean Code does both, and, like the good code described therein, it’s well written, clear, and easy to read. Martin includes many helpful examples and his suggestions are applicable to any programming language.Ideally, each developer takes charge of their own education and is constantly improving their skillset, an aspect that Martin covers in The Clean Coder. I view it as an important part of my job to help my team improve. To do so, I distill a lot of written material down to actionable components and provide that to my development team. Concepts from Clean Code have become very helpful guides for them. Below are a few of my favorite takeaways.The first is what Martin calls The Boy Scout Rule: “Leave the campground a little cleaner than you found it.” It’s a great concept, not only because it's simple to follow, but also because it has broad applicability and can be used on any project. Essentially, when a team member works on a piece of code, they should aim to improve it somehow by the time their task is finished. A few examples of this among many are: fixing an unclear variable name, breaking up a large function into smaller functions, or cleaning up a conditional for improved clarity. With everyone on the team doing this, the code improves over time and everyone feels responsible for the code whether they wrote it personally or not. Even if something can’t be addressed immediately, developers are encouraged to log the issues they see.Another of my favorite takeaways is the Three Laws of TDD, a concept I was able to quickly roll out to the team as a framework to follow for how TDD should be conducted on a project. This virtually ensures that all of your product code has test coverage. It also helps make most of your code SOLID (https://en.wikipedia.org/wiki/SOLID_%28object-oriented_design%29), since code that is built in this fashion is structured with SOLID concepts in mind. This is a must for effective testing.Finally, the topics of proper identifier names and commenting really resonated with me and my team. In our company, we tend to “adopt” existing codebases – projects that have already been started by other developers whose code is of widely varying quality. If we're lucky, it's structured well and demonstrates best practices and approaches in how it's constructed. Unfortunately, the code is sloppy at times and requires some TLC to get it in shape. A part of that process is understanding what the existing application does. As Clean Code correctly outlines, many comments are superfluous or even plain wrong and misleading. As a team, we don’t blindly trust the accuracy of existing comments and instead go right to the application’s code to determine what it does. This is where proper naming comes into play. With good names, the code reads like comments or as a narrative of what the application does, nullifying most needs for additional commenting. Simply put, the code comments itself. We also use refactoring tools to improve names and clean up comments as we go. Of course, by doing so, we’re also applying the Boy Scout Rule.Overall, Clean Code is a wonderful book with much useful and immediately-applicable information for developers of all levels. If you're looking for a book that will help make you a better developer, this will.

4.0 out of 5 stars Clean your Code and Wash your Dishes

L. · January 25, 2025

It’s like having a masterclass in your hands. This book delves into the principles and best practices of writing clean, maintainable code, making life easier for developers and ensuring that software remains robust and scalable. Pairing that with Agile methodologies, it offers practical insights into creating a seamless workflow, emphasizing collaboration, flexibility, and iterative progress. It’s a must-have for anyone serious about honing their coding skills and mastering the art of efficient, high-quality software development.

5.0 out of 5 stars Learning to leave the code cleaner than before

A.C. · September 16, 2017

As part of our learning activities, we learn quite a few programming languages. We also learn designs, patterns, good coding practices, and many more. We don't usually spend time to learn how to write a good, readable code. The relevance of this book is enormous. Not just the programmers should read it, the education providers should also read it. In fact, the education providers should plan to include this in their curriculum associated with every programming languages.I started reading this book and finished it in almost three consecutive sittings. That way, the book is well structured, and the topics are well sequenced. The author cautioned at the beginning of the book that it is not for the armchair readers. The reader should spend adequate effort to read through the code examples, think through those, and try out some of those through self scribbling. This is indeed necessary for the coders. This is also necessary for the instructors of coding, or programming languages. I chose to skim through the examples with just enough thinking while paying attention to every detail of the English text. Such speed reading worked for me too. Such reading technique should work for all who are not into direct coding today, but was a programmer once upon a time, and spends a lot of time in conversing with the programmers nowadays.Coming back to the content of the book - this was quite informative and thought provoking. I read it fully and tried to jot down my takeaways from this book reading. I have got six of them.I learned the general rules for commenting, and summarized those in four points. I learned the general rules for code formatting, and summarized those in four points. I learned the general practice of code size - for a significant system, for a code file, for a typical function. I learned the general rules of organizing concepts and variables, and summarized those in five points. In fact, the definition of concepts was itself was a new learning for me. I learned the three laws of test driven development, rather I re-learned those once more while reading this book. Finally, I jotted down the final takeaway - leave the code cleaner than what you had started with.The book is full of good references, in fact at the end of every chapter. I tried to summarize the list of further readings, and I got another five book titles listed in my to-read list. I read it on my Kindle device, and on my desktop using Bolo Cloud Reader - the formatting was good.As coders, we all have the responsibility to leave the code cleaner than what we start with. As code reviewers, we all have the responsibility to comment on the cleanliness of the codes. As the supervisor or manager of coders, we all have the responsibility to communicate the importance of clean coding and to encourage coders towards clean coding. I will recommend to all these group of people to read this book, and practice the clean coding techniques described here.Good work indeed!

Hat mir persönlich sehr gut gefallen

A.E. · April 13, 2025

(function() { P.when('cr-A', 'ready').execute(function(A) { if(typeof A.toggleExpanderAriaLabel === 'function') { A.toggleExpanderAriaLabel('review_text_read_more', 'Read more of this review', 'Read less of this review'); } }); })(); .review-text-read-more-expander:focus-visible { outline: 2px solid #2162a1; outline-offset: 2px; border-radius: 5px; } Ein Muss für jeden, der besser programmieren will – nicht nur für Anfänger„Clean Code“ hat mir persönlich sehr gut gefallen und ich würde es jedem empfehlen, der sich ernsthaft mit Softwareentwicklung beschäftigt – egal ob Anfänger oder erfahrener Entwickler.Als Ergänzung beim Programmieren lernen:Gerade wenn man neu ins Programmieren einsteigt, ist das Buch eine perfekte Ergänzung, weil es nicht nur zeigt, was man programmieren soll, sondern wie man es sauber und verständlich macht. Es geht weit über Syntax und Sprache hinaus und behandelt die Prinzipien guten Codes – etwas, das in vielen Kursen oft zu kurz kommt.Auch für Fortgeschrittene absolut lesenswert:Auch wenn man schon programmieren kann, lohnt sich die Lektüre. Das Buch hilft, schlechte Angewohnheiten zu erkennen und zu reflektieren, die sich im Laufe der Zeit eingeschlichen haben. Es geht dabei nicht um theoretische Regeln, sondern um praktische, nachvollziehbare Beispiele und konkrete Tipps, die man direkt umsetzen kann.Fazit:„Clean Code“ sollte jeder Programmierer kennen und gelesen haben. Es hat mir geholfen, meinen Code strukturierter, lesbarer und verständlicher zu schreiben – was nicht nur mir, sondern auch meinen Kollegen zugutekommt. Absolute Empfehlung für alle, die sauberen, wartbaren Code schreiben wollen – ein echter Klassiker der Softwareentwicklung.

Great for beginners dealing with legacy code

T. · June 30, 2023

This book focuses primarily on writing software on the assumption that you're using a fully fledged OOP language. It also discusses things that could be compromised on and what absolutely shouldn't when you're time constrained.Use it as a guideline but don't follow it religiously. There are modern concepts that have diverged from some of the practices used in this book and for very good reason. However, if you're writing in C++, C#, or Java, then the majority of this book still applies.

Does what it says on the tin

S.G. · May 3, 2009

Every so often, a book comes along that codifies best practice in a way that manages to illuminate the path from where things are right now, to a better place that we'd rather be -- things like Fowler et al. Refactoring: Improving the Design of Existing Code (Object Technology Series) or the Gang of Four Design patterns : elements of reusable object-oriented software. This is one of those books. And if much of the material is the sort that seems obvious in hindsight -- well, that is the mark of a well written book, to make the concepts that clear.Taking a series of real world examples -- open source projects with significant user bases, including FitNesse and JUnit -- a series of worked examples take us from good, or at least adequate, code, to a form which is better factored, and easier to read, with the steps along the way clearly marked. Yes, even some of Kent Beck's code is put under the microscope, and carefully polished that extra stage or two more.The reader is cautioned that, without working long hours to follow these examples, this will be just another of those feel-good books. I don't quite agree -- spending just a little time to follow the transformations, and then reflecting on one's own outpourings should be enough to make this a feel-bad book. All the sins from obscurely named variables to sprawling functions that gaily mix abstraction levels, we've all done them (especially programming in FORTRAN on minicomputers with slow stacks and a rule of thumb that 1 call ~ 40 loc in terms of performance).The maxim to take from the book is based on Baden-Powell's "Try and leave this world a little better than you found it", and owes to the same school of thought as "whenever you are in the garden, pull at least one weed". The meat of the book is in distinguishing what are the weeds from the intended crop.So read it, understand the examples, and then refer to it often -- like the other titles mentioned, it is a reference work, and should join them as among the most thumbed on your bookshelf.

For software artisans with love ❤️

C.A. · January 28, 2025

Un libro che ti apre la mente. Se anche tu come artigiano del software vuoi migliorare il tuo codice e la tua capacità progettuale, in termini di efficienza, manutenibilità e organizzazione del codice, questo libro fa al caso tuo.

No se trata de leerlo

I. · June 11, 2025

Es un libro de lectura trivial; lo difícil es aplicar lo que nos parece buena idea en todo momento y ser consistentes con el esfuerzo.Yo creo que más que leérselo hay que resumirlo, tomar lo que a uno le interesa e interiorizarlo; y eso no es tan fácil como pueda parecer. Habré leído este libro al menos 3 veces, lo tengo resumido y con todo, de vez en cuando voy al resumen a la zona de malos olores y me doy cuenta de que hay cosas que en las que se puede mejorar.La parte de la refactorización en la que incide mucho el autor, es muy muy pesada; aunque compensa con creces el esfuerzo.