My current reading list:
* Code Complete: A Practical Handbook of Software Construction - Steve McConnell
* Agile Software Development - Robert C. Martin
Upcoming reading list:
* Node.js Design Patterns - Mario Casciaro
* The Pragmatic Programmer: From Journeyman to Master - Andrew Hunt
* Clean Code - Robert C. Martin
* Refactoring: Improving the Design of Existing Code - Martin Fowler
And maybe Working Effectively with Legacy Code by Michael Feathers.
If anyone has any comments or other suggested readings I'd love to hear them!
(if yes, then why isn't it on your list!?)
@otoolep, your spam detection missed the one comment to this post. :)
It gets a lot of positive reviews because it is from a highly credible source who actually did what he was talking about not just wrote about it and because it describes conditions that still obtain; more than forty years later we still haven't learnt all the lessons.
What do you mean?
* working in sprints forces estimations over smaller pieces of work (aim small, miss small).
* sprints, in my experience, challenge feature creep. teams are much more aware of time and challenge anyone making changes to scope. nothing is free.
* teams are responsible for dev and testing (e2e); no throwing crap over the wall.
These books deal with more than these topics.
btw, the quiet room for 2-3 people as described in Peopleware is being thrown out where i work. walls are being torn down to build team collaboration spaces. times have changed.