Goodreads helps you keep track of books you want to read.
Start by marking “Czysty kod. Podręcznik dobrego programisty” as Want to Read:
Czysty kod. Podręcznik dobrego programisty
Enlarge cover
Rate this book
Clear rating
Open Preview

Czysty kod. Podręcznik dobrego programisty

(Robert C. Martin Series)

4.40  ·  Rating details ·  16,607 ratings  ·  993 reviews
Poznaj najlepsze metody tworzenia doskonałego kodu

* Jak pisać dobry kod, a zły przekształcić w dobry?
* Jak formatować kod, aby osiągnąć maksymalną czytelność?
* Jak implementować pełną obsługę błędów bez zaśmiecania logiki kodu?

O tym, ile problemów sprawia niedbale napisany kod, wie każdy programista. Nie wszyscy jednak wiedzą, jak napisać ten świetny, "czysty" kod i czy
Paperback, 424 pages
Published February 2010 by Wydawnictwo Helion (first published January 1st 2007)
More Details... Edit Details

Friend Reviews

To see what your friends thought of this book, please sign up.

Reader Q&A

To ask other readers questions about Czysty kod. Podręcznik dobrego programisty, please sign up.
Popular Answered Questions
Madison Scott I own it in paperback form but ended up reading most of it from a PDF in the native books app on my iPhone, as it was most convenient for me to read i…moreI own it in paperback form but ended up reading most of it from a PDF in the native books app on my iPhone, as it was most convenient for me to read in an electronic format while commuting via the subway. (Note: it was a PDF and NOT an ebook, so I don't know if an ebook would mess with the formatting.) The paperback version was definitely handy for two or three of the later chapters that are each a study in refactoring some package of code. For these chapters, I had post it notes in up to five different places in the book, flipping back and forth between bits of the original code, bits of the refactored code, and the explanation of why the changes were made. If you have access to a printer, you could just print the relevant items for these chapters when it comes time. The PDF is easily found with a quick Google.(less)
This book is not yet featured on Listopia. Add this book to your favorite list »

Community Reviews

Showing 1-30
Average rating 4.40  · 
Rating details
 ·  16,607 ratings  ·  993 reviews

More filters
Sort order
Start your review of Czysty kod. Podręcznik dobrego programisty
Oana Sipos
Mar 08, 2015 is currently reading it  ·  review of another edition
These are rather notes than a review while reading:

1. Use very descriptive names. Be consistent with your names.

2. A function should not do more than one thing.

3. SRP (Single Responsibility Principle): a class or module should have one, and only one, reason to change.

4. Stepdown rule: every function should be followed by those at the next level of abstraction (low, intermediate, advanced).

5. A long descriptive name is better than a short enigmatic name. A long descriptive name is better than a
Francis Fish
The first half of this book is well worth a read. Then I was reminded of Martin Fowler's (I think) comment that the original Design Patterns Elements of Reusable Software book was a response to the limitations of C++. It dovetailed so well into Java because Java has a lot of the same annoying limitations, and in some ways is even harder.

The latter section of the book contains some worked examples that I didn't always agree with because they seemed to be totally over done. A lot of the refactorin
Apr 14, 2011 rated it really liked it  ·  review of another edition
Shelves: swe
This book makes some very good points, sometimes taking them to extreme ("Never write functions longer than 15 lines! Never write functions with more than three arguments!"). Some of these points were quite new and useful for me - YMMV. It's too Java-specific in a few places, and reading the last refactoring chapter on a kindle was quite a challenge, but otherwise it was well worth a read. At least I got a clear picture of how I want to refactor a big piece of my current project after reading th ...more
Rod Hilton
There is a movement brewing in the world of professional software development. This movement is concerned not merely with writing functional, correct code, but also on writing good code. Taking pride in code. This movement is the Software Craftsmanship movement, and one of the people near the head of this movement is Robert C. Martin, also known as Uncle Bob.

His book "Clean Code" is, in many ways, an introduction to the concept of Software Craftsmanship and a guide for developers interested in b
If you are a programmer, you must read it! full of good examples of how to write clean and readable code.
Jan 08, 2009 rated it liked it  ·  review of another edition
Shelves: technical
I had a tough time deciding between 3 or 4 stars.

The book should be called Clean Java Code. Some of the concepts definitely translate to other languages, but it uses Java for all of the examples and some of the chapters are dedicated to Java-specific issues.

I consider many of the the suggestions to simply be common sense, but I've worked with enough of "other people's code" to realize they don't necessarily agree. With all of that said, I'd definitely recommend the book to Java developers at th
Oct 03, 2013 rated it liked it  ·  review of another edition
Shelves: computers
Many good points in this book. Unfortunately, almost all of them are overdone. Yes, you should write short functions, if possible. Yes, you should have functions that do one thing.

But no, "one thing" does not mean you should tear an algorithm apart into twenty little funclets that make no sense on their own.

Basically, like another reviewer wrote, the first part of the book raises many good points, and the second part of the book then merrily applies these points way beyond their usefulness. Read
May 16, 2014 rated it it was ok  ·  review of another edition
I was extremely underwhelmed with Clean Code! As other reviewers have noted, this book completely Java-centric and incredibly narrow in its object-oriented focus. Nowhere on the front cover, spine, or back cover is this mentioned at all.

Clean Code also relies heavily on other published works. In the case of Fowler's Refactoring and the "Gang of Four"'s Design Patterns, I wasn't too put off by it. These are pretty standard reference books and I have them on my shelf.

But the really irritating ref
Amir Tesla
Great great book on principles of clean code.

The only problem with the book was that it’s obsessively written for Java. Even though, there are still many principles you can apply to any other languages from C to Python.

Although have to say, you have to do your own research for applicability of the principle in your target language. For instance, the inversion of control (IoC)and Dependency Injection (DI) are quite common and intrinsic to Java, but it is not as straightforward in Python (becaus
Fahad Naeem
I started reading it after a lot of recommendations but it wasn't gone up to the standards.
Clean Code is about writing code which is not only understandable to the code him/herself but to the others as well.

Robert Martin mainly used a lot of JAVA code which is not applicable to other languages like Python and JAVASCRIPT. This book should not be this much lengthy and other languages must be covered so that every programmer can benefit from it.

I was looking forward to learn more about refactoring
This is a book that one could get started on the idea of "good code" - clean, readable, elegant, simple, easy-to-test, etc. It has the usual stuff that you'd expect - good naming convention, testable code, single responsibility, short classes, short methods - but I feel like it takes them on overdose, going to extremes (IMHO) such as setting short explicit lengths, forbidding certain constructs, and what seems like refactoring for the sake of it.

I'd actually recommend other books like the Pragma
Kosala Nuwan Perera
Feb 07, 2011 rated it really liked it  ·  review of another edition
Shelves: favorites
I had a tough time deciding whether I really liked or It was amazing. I liked the writing style of the book. Its simple, clean, and well crafted.

First few chapters of the book makes good practical advice from naming variables-functions-classes to writing functions to testing. Most of the smells and heuristics I found in these chapters can be found in real-world as well.

Complexity kills. It sucks the life out of developers, it makes products difficult to plan, build, and test. - Ray Ozzie, CTO, M
Rostislav Vatolin
To me this book is an extension of Martin Fowler’s “Refactoring”. As a Java developer I enjoyed it. It’s an easy read. I agree with everything, except “J1: Avoid Long Import Lists by Using Wildcards” and using less of final keyword (agree with Robert Simmons here more, he explained it in his “Hardcore Java” book). This book has some useful tips on how to avoid locks and other issues in multithreaded environment (I found it very useful).
In short, it is worth reading.
Nick Hodges
Apr 02, 2015 rated it really liked it  ·  review of another edition
I hate to say this, but I wasn't as impressed with this book as I thought I should have been, given its place in the pantheon of programming books.

The first half was excellent, but the second half left me a bit cold. It was too Java-y, and had -- dare I say it -- too much code in it.

However, I still list this as a must read for all developers.
Alex Ott
Mar 12, 2011 rated it liked it  ·  review of another edition
Shelves: programming
Nothing new for experienced developer...
Too Java oriented in many places. Code Complete, 2ed is better from my point of view
Yevgeniy Brikman
A good book to read for any coder - perhaps not as thorough as Code Complete but much more effective than Pragmatic Programmer.

This book's biggest strength is that it includes tons of code examples, including some fairly long and in depth ones. Instead of just listing rules or principles of clean code, many of the chapters go through these code examples and iteratively improve them. The rules and principles fall out of this process and the reader is a part of developing them, which is an effect
Erika RS
I wanted to love this book, but instead I just sort of liked it. This book is a member of the extensive genre of books on how to write clean code. It sits alongside books like Code Complete by Steve McConnell[1] and many others. Where Clean Code promised to differentiate itself was in the use of three case studies -- about a third of the book -- showing Martin's code cleanup techniques in action.

However, I was disappointed by that section. As someone who codes and reviews code professionally, t
Craig Vermeer
Jan 04, 2010 rated it it was amazing  ·  review of another edition
Shelves: tech
This had lots of good, practical advice that spanned everything from naming to testing to concurrency. A lot of it was pretty Java centric, so I skimmed a few sections.

By far the best portions of the book were the ones where the author demonstrates -- step by step -- his process for writing code test-first, as well as refactoring.

If you get frustrated with either of the two at times, these parts of the book are *fantastic*, because you see that even someone who's been coding for 40+ years (like
Nick Skelton
Feb 12, 2015 rated it it was amazing  ·  review of another edition
Shelves: coding
Uncle Bob's book was given to me by a mate at work when I first started. I was introduced to the concept of code reviews and pull requests and told to expect a lot of comments on my code reviews to start with. I was then promptly given this book to read to minimise the pain. As a developer with ten years experience, I had seen so many of the things outlined by Uncle Bob and absolutely loved his remedies to them. I am now a convert to the idea of clean code and it has definitely made me a better ...more
Erkan Erol
Mar 01, 2017 rated it really liked it  ·  review of another edition
Writing clean code is what you must do in order to call yourself a professional. There is no reasonable excuse for doing anything less than your best.
“Honesty in small things is not a small thing.”
In code, refactor mercilessly.
The French poet Paul Valery advises us that a poem is never done and bears continual rework, and to stop working on it is abandonment.
Learning to write clean code is hard work. It requires more than just the knowledge of principles and patterns. You must sweat
Nick Craske
Jul 28, 2018 rated it really liked it  ·  review of another edition
Having reignited my love of programming I have dived into learning Unity with an aim to build games. It's purely for my personal enjoyment. Clean Code is written in an accessible, relaxed and conversational style and throws light and insight on every corner of writing, maintaining and refactoring code. Using Java examples the author clearly sets out his manifesto for elegant, well structured, concise and readable code. It feels good to be coding again. ...more
Jul 26, 2013 rated it really liked it  ·  review of another edition
I should have read this book at the beginning of my career. On the other hand, after 10 years experience I may appreciate it even more. It is sad, that principles described in the book are not yet heavily adopted.
Nov 22, 2009 rated it it was amazing  ·  review of another edition
This book is #1 on my list of books I'd recommend to other programmers. I don't know how else to elaborate on how important I think the ideas in this book are. ...more
Stefan Kanev
May 28, 2010 rated it really liked it  ·  review of another edition
It's a great book. The only reason I give it four stars instead of five is the extremely awkward use of private fields for passing data between functions in the examples. ...more
Definitely worth a read ... :-)
Petar Ivanov
Dec 31, 2019 rated it really liked it  ·  review of another edition
Shelves: computer-science
Great book! There's a lot of ideas, techniques, tips, and tricks and examples that help you enhance your programming skills and coding style. I didn't like a lot the SerialDate case study because there was a lot of back and forth with the Appendix. It was quite hard for me to follow the refactoring of the SerialDate class.
Overall, I enjoyed reading the book and it helped me to generate more ideas on how to refactor and write better and cleaner code. Personally, I think it's a must-read for ever
Feb 26, 2020 rated it it was amazing  ·  review of another edition
This book provides some very good general advice for any practicing programmer. While examples use java, the lessons transfer to any object-oriented language. Each chapter can be read separately, but they are each about writing clean code.
May 14, 2021 rated it liked it  ·  review of another edition
There are very useful principles in this books that would help a programmer write cleaner code, that's for sure. However, I believe some of the statements should be taken with a grain of salt. Anyways, I'm glad I read it. Though, it would have been more helpful for me if the main focus of this book were Scala or Python instead of Java. ...more
Mohammad Mahdi Ramezanpour
This is one the best books for programmers and I think every programmer should read it. The only problem this book has is some parts of it is written specifically for Java developers; so, you may want to skip them, if you're not a Java developer. ...more
Dec 25, 2019 rated it it was amazing  ·  review of another edition
Every true programmer must at least skim through this book. The techniques and methods are essential to educating a perfect programming style and you don't want to enter the market without this asset. ...more
« previous 1 3 4 5 6 7 8 9 next »
topics  posts  views  last activity   
Goodreads Librari...: Add cover 3 19 Jun 01, 2021 04:02AM  
7z Archive Password Recovery Tool 1 2 Jul 22, 2020 01:21AM  
How to Recover 7zip Password? 1 3 Jul 22, 2020 12:38AM  
Why School bus Tracking Software important ? 1 2 Oct 29, 2019 04:02AM  
How to Recover Excel Password 1 5 Aug 05, 2019 12:14AM  
How to Unlock PDF With PDF Unlocker 1 1 May 20, 2019 03:10AM  

Readers also enjoyed

  • The Pragmatic Programmer: From Journeyman to Master
  • Design Patterns: Elements of Reusable Object-Oriented Software
  • Refactoring: Improving the Design of Existing Code
  • Head First Design Patterns
  • Code Complete
  • Effective Java
  • Domain-Driven Design: Tackling Complexity in the Heart of Software
  • Test-Driven Development: By Example
  • Working Effectively with Legacy Code
  • Designing Data-Intensive Applications
  • Building Microservices: Designing Fine-Grained Systems
  • Java Concurrency in Practice
  • The Mythical Man-Month: Essays on Software Engineering
  • JavaScript: The Good Parts
  • The Software Craftsman: Professionalism, Pragmatism, Pride
  • Implementing Domain-Driven Design
  • Extreme Programming Explained: Embrace Change (The XP Series)
  • Growing Object-Oriented Software, Guided by Tests
See similar books…

Goodreads is hiring!

If you like books and love to build cool products, we may be looking for you.
Learn more »
Robert Cecil Martin, commonly called Uncle Bob, is a software engineer, advocate of Agile development methods, and President of Object Mentor Inc. Martin and his team of software consultants use Object-Oriented Design, Patterns, UML, Agile Methodologies, and eXtreme Programming with worldwide clients.

He was Editor in Chief of the C++ Report from 1996 to 1999. He is a featured speaker at internatio

Other books in the series

Robert C. Martin Series (1 - 10 of 15 books)
  • Fit for Developing Software: Framework for Integrated Tests
  • Working Effectively with Legacy Code
  • Agile Java: Crafting Code with Test-Driven Development
  • Managing Agile Projects
  • Agile Estimating and Planning
  • UML for Java Programmers
  • Agile Principles, Patterns, and Practices in C#
  • The Clean Coder: A Code of Conduct for Professional Programmers
  • Java Application Architecture: Modularity Patterns with Examples Using OSGi (Software Patterns Series)
  • The Software Craftsman: Professionalism, Pragmatism, Pride

Related Articles

You’d never know it from reading the books listed here, but good science writing is incredibly difficult to pull off. There is both an art...
103 likes · 7 comments
“Truth can only be found in one place: the code.” 70 likes
“Indeed, the ratio of time spent reading versus writing is well over 10 to 1. We are constantly reading old code as part of the effort to write new code. ...[Therefore,] making it easy to read makes it easier to write.” 46 likes
More quotes…