The Pragmatic Programmer, 20th Anniversary Edition
1–10 of 121 posts
Re: The Pragmatic Programmer, 20th Anniversary Edition
#2While your at it, please update "Pragmatic Project Automation".
Re: The Pragmatic Programmer, 20th Anniversary Edition
#3The original version of this book is something I'll always treasure. It sits next to "Code Complete", the Gang of Four's "Design Patterns" book and Martin Fowler's "Refactoring" on my top shelf and I still read parts of it every year.
Re: The Pragmatic Programmer, 20th Anniversary Edition
#4Re: The Pragmatic Programmer, 20th Anniversary Edition
#5https://www.amazon.com/Pragmatic-Programmer-journey-mastery-...
Buying from the pragprog site gets you a 50% discount on the hardcover when it comes out, if you have any interest in the paper version.
Re: The Pragmatic Programmer, 20th Anniversary Edition
#6This book was a tremendous influence on me as a young professional programmer. I still quote from it regularly. ("SELECT isn't broken!")
Re: The Pragmatic Programmer, 20th Anniversary Edition
#7This book is in my opinion the most important book for professional software developers. It teaches you the craft.
Re: The Pragmatic Programmer, 20th Anniversary Edition
#8There's some good advice in the book, but I found the majority of it seems to be rather goldilocks flavored. Implement the features you need, but don't add too many, but don't omit important ones either. Write some documentation, but not too much or too little. Etc. You read it, and oh yes, very wise, but not really helpful? Not much here would be useful in resolving a dispute between two programmers, one who wants to do things one way and one who wants to do it a different way.
Re: The Pragmatic Programmer, 20th Anniversary Edition
#9Anyone with an opinion on the new edition? Worth buying if you already read the old one back when it came out?
Re: The Pragmatic Programmer, 20th Anniversary Edition
#10There's some good advice in the book, but I found the majority of it seems to be rather goldilocks flavored. Implement the features you need, but don't add too many, but don't omit important ones either. Write some documentation, but not too much or too little. Etc. You read it, and oh yes, very wise, but not really helpful? Not much here would be useful in resolving a dispute between two programmers, one who wants t…
I'll agree with your summary, but I'll also argue that moderation is often a lesson coders need to learn/remember. It is easy to "know" in theory but become dogmatic in practice. There are reasons we are still learning the lessons from 30+ years ago - we keep getting dogmatic about concepts that interfere.