The Pragmatic Programmer: Your Journey to Mastery
“Twenty years ago, the first edition of The Pragmatic Programmer completely changed the trajectory of my career. This new edition could do the same for yours.” –Mike Cohn, Author of Succeeding with Agile, Agile Estimating and Planning, and User Stories Applied
“. . . filled with practica ...more
Having said that, it is not a very advanced book. Much of what it speaks would have become a part of ones…moreIt's a great book, hands down. I rate it 5/5.
Having said that, it is not a very advanced book. Much of what it speaks would have become a part of ones' programming common sense if they have been writing code for 5 years or so.
But it still does a good job of strengthening the readers beliefs formed by experience. I found myself thinking often "Yeah I knew this, but they really stress on the importance, so it must be important"
I picked up "Clean Code"by Robert Martin after this, hoping it goes into more depth.(less)
The information contained in this book is essential for software ...more
Case in point: That I found this book. Over the past couple of years I have been gradually writing and less-gradually maintaining a code base for separate projects. It's getting the point where I might as well figure out what the hell I'm doing. So I go to Stack Overflow and find my way to a question like "What programming book do you wish ...more
Certainly not for experienced, skilled software developers. Considering myself at least experienced, I found most of the material in this book a rehash of methodologies and techniques I've used for more than a decade. Granted, there were a few gems here and there, but mostly I was bored because I didn't learn anything new.
One has to respect that this book is from 1999, so in that perspective, it must have been quite ground-breaking. Had I read it in 1999, I wouldn't have kno ...more
See this review and others on my blog ...more
This seems to be a favorite in the office, so before I participating in the recommending of this book to new hires, I figured I should check it out first. There is definitely some good stuff in here, but most won't be new for anyone who's been programming professionally for 2 or 3 years or more. I think most engineers' problems is that they don't do what they know is the right thing.
I think many people have said this before, but at the risk of duplication I'll say t ...more
Others have mentionned that they already knew most of the things in this book, and practice these good habits in their development environments. I've worked in dozens of environments ranging from very successful experienced companies, to fly-by-night operations tha ...more
Chapter 1. A Pragmatic Philosophy
Tip 3: Provide Options, Don't Make Lame Excuses
Before you approach anyone to tell them why something can't be done, is late, or is broken, stop and re-evaluate
Tip 4: Don't Live with Broken Windows
Don't leave "broken windows" (bad designs, wrong decisions, or poor code) un-repaired
Tip 5: Be a Catalyst for Change
Start with s ...more
As to Russian edition of this book, it's translated very badly, it's almost unreadable. ...more
8 out of 10 this time around.
I read the original book around 8-9 years ago. To be honest, it probably defined the engineer I am now, back then. I was kind of devastated with my first two professional experiences back in Turkey where there were either no engineering practices at all or if any, done poorly. So in the absence of a better example, this book is one of those books that I used to teach myself what software development pro ...more
I like to think that I already ask myself those questions all the time. Nevertheless, I found myself reading a page or two and then having to stop because I was having a great idea and needed to write it down. I filled six sheets of letter-size paper with dense, cryptic notes. Th ...more
If you have worked or are working in a good team and good project, you can easily relate back and forth about the goof things that are talked about.
It is simple to read, still relevant in 2016 and is worth investing couple of weeks to read this if you are aspiring to be a pragmatic programmer.
Some of the advice is actionable, but some is theoretical or ideological; some parts are language and framework agnostic, while others have become quite dated; there are a few bits of deep, meaningful advice, but mostly, the book consists of fairly simple apho ...more
Great thing explained in the most pragmatic way possible. Due to its usage of metaphors, easy-to-read language, it read like a breeze.
I might have forgotten some of the great stuff in it, might actually reread it soon.
Empowering book 💪
Yes this is one empowering book and is one of the books that should be bought with hard-cover and keep it close to you for reference and to read again a couple of times, or more.
What is this all about? 🤷🏻♂️
David and Andrew take us in a journey to mastery, as the book says, from being just a programmer to becoming a pragmatic programmer, and pragmatism is all about using the tools that work best for you and your team to develop professional products and delight
Goodreads is hiring!
Learn more »