The Productive Programmer

Just finished reading "The Productive Programmer" by Neal Ford. Mixed emotions about the book. On one hand it's packed with good practices and decent tips to follow, on another hand haven't I watch the presentation on InfoQ, reading the book might be a bit more pleasant...

One good thought that I liked in the book especially - question the authorities. Exactly as the author of the book ran into the no acceptance of changing long-time structured naming conventions, same happened to myself recently in a team with a couple of "old school agile consultants" (no names :). And the most important lesson, don't turn into angry (code) monkey and beat other developers for fresh ideas. 

PS: I do recommend to watch the presentation, though. It's good.