Timeless Laws of Software Development
J**H
A useful quick read
I like the style of this book. It doesn't mince words, it's pretty short, the font is big and most of what it says is important and useful. On the flip side most of what it says you will have learned once you've been developing for a long time. So I think it's best for beginner to intermediate engineers. I do like the fact that at points it argues some opinions that are not trendy but in most cases, well-founded. For example, it does make a good case for thoughtful design and offers cautions regarding TDD.
J**F
Nice Summary of Coding Best Practices and Tips
Reminds me of a book called "Tips" I read back in my theatre acting days. Contains small concise sections which summarize best practices and then justifies them with real world examples. If you've been a software developer for any length of time, and have cared about your craft, you likely already "know" all the suggestions in this book. HOWEVER, I found it a great little refresher on things that are easy to forget if you've gotten bogged down in the day to day of developing a software project.
C**T
A lot of good points in one book
This book has a lot of good programming tips. I found the first half of the book a little boring, but the second half was dense with a lot of good programming tips, such as immutability, information hiding, and small methods. The author has a non-hyperbolic, non-dogmatic, moderate way of writing and expressing his opinions. He does a valuable job of summarizing useful points that I have read elsewhere. Good job!Some other good books to read on the same subject:Clean Code (and other books written by Bob Martin),Effective Java (especially chapters on immutability and inheritance),The ThoughtWorks Anthology (chapter on Object Calisthenics)The Art of Readable Code,Clean Code in a Nutshell,Hello Startup (chapter on Clean Code)The Pragmatic Programmer (especially parts about "Don't Repeat Yourself" and "Broken Windows")
L**7
Simply, the best
Never have I gained so much knowledge and insight from so few pages of text. This book is like lightning for the software mind.
A**R
Great Read for Anyone with Software Interests
Timeless Laws of Software Development is honest, informative and a benefit to read. I learned that the author, Jerry Fitzpatrick, had worked with Robert Martin (well known in the software arena) so I decided to give this book a look. The author shares a lot of real personal stories, some funny and some frustrating, that I think anyone in software development could relate with and learn from.
T**0
A must read for QUALITY software
Jerry Fitzpatrick identifies general developer laws through real-world examples that can be used in writing or editing code for creating high quality software. Although most examples in the book are in C/C#, the laws outlined are truly general and applicable to any language. That makes this book a longevity item on my bookshelf as I will be thinking of these the next time I write or review a line of code.
C**F
Highly recommended
I don't usually write reviews but I highly recommend Timeless Laws of Software Development for any project manager or team lead. Clear, concise, easy to follow. Wish I had read this book before our company's last project. If you're serious about getting it right, saving time and money take the time to soak in this book. I plan to gift copies to my team members for Christmas. (maybe sooner)
E**D
A pleasure to read
The other existing five star reviews for this book are why I bought it, and those reviews are accurate.
D**K
Great book for any skill level
This book is great for almost any skill level of programmer.Beginners will learn lots of basic info.Advanced programmers will learn subtle tradeoffs about how certain problems can be solved or avoided.I think this is one of those books you can re-read every year or two, and come away with new learning each time.
S**I
Good tips
A lot of good tips in a relatively small book. Also easy to read for a relatively new wannabe developers like me. Good book!
S**I
Practical guide to improve software quality
The book contains many useful recommendation how to improve software quality.Just one note:Using the term renovator to describe someone that is acting as an editor is questionable because compared to construction renovation means fixing something old where as in the context of the book renovation means improvement of something new.But beside the naming the idea is brilliant!
Trustpilot
4 days ago
3 weeks ago