Pragmatic Programmer, The: Your journey to mastery, 20th Anniversary Edition

I work in IT but am just a hobbiest when it comes to programming (I do game development for fun), so this book isn't being used towards work as such but even so this book was incredibly useful for keeping me from getting into bad habits with my own Projects along with teaching you useful life lessons in general. So I read this front page to back and took notes on the things I thought were very useful to know. It's quite a short hardback book but packed with lots of value, now that I have notes taken from it I will glady read them over and over during and before I start a new project. Could you find a lot of this information from multiple blog post, yes definitely but this is a "classic" programmer book where they most likely got this timeless information from.

Very useful and informative, covers various aspects, from requirement gathering, estimations, coding best practices, tests, refactoring and delivery.

If in IT, especially in programming, this is really a must read and if anything a only read. The reason I say this is that it shows you that being adaptable and applying good principles is best for yourself, team and the deliverable. With the lessons taken from the book I was able to research into other areas which have given me valuable skills. Good luck !

I adore the first edition of the "Pragmatic Programmer", and have based some lectures around it. I only recently noticed that this second ("20th anniversary") edition existed, so bought it eagerly in hardback forrm. It has been extensively tweaked and had whole new chapters added (especially on concurrency, a major topic nowadays), and I'm sure that a modern programmer will get a huge amount out of it. But some of the tips have been removed, updated or changed (gasp). In particular, having taken a really hard line on programmer's editors ("learn a single editor well") in the first edition, I was shocked to see that the second edition waters that down to "learn as many editors as you like, as thoroughly as you can". (I paraphase because I don't have the book to hand). My favourite programming language Perl appears to have been surgically removed from the book and index, previously it was recommended (in another tip) to "learn a text manipulation language" and Perl was used as the main example of that. Not any more. Generally, it seemed to have grown in bulk, while not covering as much useful material for me as before. As a result, while the first edition was brilliant and incisive book, the second edition seemed a bit flabby to me.

I read this book and I like it. Very useful cases are written. It helps to be: - organised for junior, learn the mistakes of others before doing himself. - manage team for middle developers. Most useful insides are helpful for the middle level. - create a corporate culture for seniors. There are some examples of how the corporate team should be. - managing difficult teams for HR and Business owners. If you are new to creating your IT team this book helps to find how to start and keep success. - all other people to learn the processes of software development. Some insides are useful for non-software teams, too. You can use the practice in your industry.

My some is learning to code and has a couple Of languages under his belt, this book was a great compliment to his learning. Some very good life tips come out of the themes explored too!

Absolutely amazing and insightful book that I read in two sittings spread across two days. I've also read a selection of Uncle Bob's books, and compared to his pointless meanderings and pompous language, this books offers practicality, lucidity, and fantastic examples. Every single developer who's transitioning into the mid/mid-senior level must read and internalise what this book is talking about. Aside from the content, the print is high quality, and the fact that it's a hardback makes it a perfect addition to my small library of reference books at work. I know it's going to last.

Great read, been through some bits several times. Lots to take from this as a mid-ish-career programmer.