Debugging Teams

Appendix B. Further Reading

We created this book based on our experiences writing software with numerous teams and people, but we’ve also read many books and articles that have helped us formulate the thoughts that we laid out on these pages. Here are a few of the books and articles that influenced us along the way:

• Peopleware: Productive Projects and Teams, 2nd Edition, by Tom DeMarco (Dorset House)

• Drive: The Surprising Truth About What Motivates Us by Daniel H. Pink (Riverhead)

• “You and Your Research” by Richard Hamming

• Predictably Irrational: The Hidden Forces That Shape Our Decisions by Dan Ariely (HarperCollins)

• The Mythical Man-Month: Essays on Software Engineering, 2nd Edition, by Frederick P. Brooks (Addison-Wesley Professional)

• Startup Engineering Management by Piaw Na (self-published)

• Rework by Jason Fried and David Heinemeier Hansson (Crown Business)

• Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman by Dave Hoover and Adewale Oshineye (O’Reilly)

• Quiet: The Power of Introverts in a World That Can’t Stop Talking by Susan Cain (Crown)

• Fearless Change: Patterns for Introducing New Ideas by Mary Lynn Manns (Addison-Wesley)

• The Art & Adventure of Beekeeping by Ormond Aebi (Rodale Press)

• “Maker’s Schedule, Manager’s Schedule” by Paul Graham

• The Art of Readable Code by Dustin Boswell and Trevor Foucher (O’Reilly)

• Mastery: The Keys to Success and Long-Term Fulfillment by George Leonard (Plume)

• “The Significance of Task Significance: ...