There's a lot of great material in this book, and it's probably worth a quick read for all developers. Younger developers would probably get the most out of it, since they have the most to learn, and the biggest habits to shape, but even seasoned developers can and should learn from the advice here. I agree with most of the book, although feel like it didn't go far enough on some paths; I would've liked to see more discussion about being a great team member, helping to shape and form a team, hiring, gaining non-engineering insights, and other issues, but much of that probably falls outside the scope of what the author wanted to tackle. I read this for work, so I wouldn't recommend it for anyone not in the industry. There were some interesting stories about the way the field of programming developed, but for the most part, this was a book full of hints about how to do my job better. And I think that happened. I implemented several of his suggestions, and after doing so, received a big fat raise and the best job performance review I have ever had.
What do You think about Mistrz Czystego Kodu. Kodeks Postępowania Profesjonalnych Programistów (2013)?
Professional: say NO! Don't try! Don't work overtime longer than 2 weeks!
—Evilfish
A clean explanation of how to be professional in the development area
—lupita
