What do you think?
Rate this book
24 Patterns for Clean Code: Techniques for Faster, Safer Code with Minimal Debugging
There is the right way to do things, and there's the wrong way to do things. Unfortunately, most of us don't really take the time to figure out which way is which.
Robert lays out 24 patterns of thought and design that tend to produce faster, more reliable, and easier to maintain code without noticeably increasing the difficulty or decreasing the speed of coding. In this book, you'll learn about Niklaus Wurth's 3-10 rule, speed-documenting tools, and the techniques that keep memory leaks out of your code.
Robert lays out 24 patterns of thought and design that tend to produce faster, more reliable, and easier to maintain code without noticeably increasing the difficulty or decreasing the speed of coding. In this book, you'll learn about Niklaus Wurth's 3-10 rule, speed-documenting tools, and the techniques that keep memory leaks out of your code.
74 pages, Kindle Edition
Published December 31, 2015
25 people are currently reading
31 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 5 of 5 reviews
February 7, 2020
When I see the word "Patterns" I usually think about signetons, proxies and all of that. This book isnt really about patterns. It is, instead, a collection of tips for beginners starting out in the magic world of programming.
There isnt really much to tell about the content, as it is not very technical. There are a couple of things I do not really agree with tho. First, commenting out the bad code you are fixing and leave it there just in case. Not sure if you ever heard of Git. There is nothing worse than having hundreds of lines of code that are commented out, making it impossible to read the real code.
That said, regarding logs, I do not agree that quantity matters. Quality matters. You can dump GBs of information and still know nothing about what is going on. You want quality information that is easy to find and understand.
There isnt really much to tell about the content, as it is not very technical. There are a couple of things I do not really agree with tho. First, commenting out the bad code you are fixing and leave it there just in case. Not sure if you ever heard of Git. There is nothing worse than having hundreds of lines of code that are commented out, making it impossible to read the real code.
That said, regarding logs, I do not agree that quantity matters. Quality matters. You can dump GBs of information and still know nothing about what is going on. You want quality information that is easy to find and understand.
May 5, 2019
I haven't been using C in a very long while, so I shouldn't judge the book based on that.
But the claim that the "patterns" should apply to modern OOP are very misleading. In all honesty, I can't recommend this book, and I would suggest novices especially stay far from it.
But the claim that the "patterns" should apply to modern OOP are very misleading. In all honesty, I can't recommend this book, and I would suggest novices especially stay far from it.
December 27, 2020
Must Read For All developers
This book is written with a perspective of the developer, more like a guideline of dos and don'ts while working on a project or a program. Although book is old advice and patterns followed by the author vis still relevant today.
This book is written with a perspective of the developer, more like a guideline of dos and don'ts while working on a project or a program. Although book is old advice and patterns followed by the author vis still relevant today.
August 13, 2017
Outdated book
March 8, 2016
Even though this book has been published recently, it is way outdated. Better not to read! Name of the book should also contain that it is for C language. Author is claiming that book can be used in general but I doubt it...
Displaying 1 - 5 of 5 reviews