Becoming a Technical Leader

My three favorites from Gerald Weinberg: 1. 'The Secrets of Consulting: A Guide to Giving and Getting Advice Successfully' I was put off for a decade by the click-bait title but this is a profound little book that helped me get perspective on problem solving in my work and myself. 2. 'Becoming a Technical Leader' The text is great; working the exercises for yourself will make you a stronger thinker. 3. 'An Introduction to General Systems Thinking' One of his densest, driest books, but a great summary of the highlights of the field with plenty of thought problems in the exercises and plenty of pointers for digging deeper.

Offhand... 1. 'The Making of the Atomic Bomb', R. Rhodes 2. 'Apollo: Race to the Moon', C. Murray, C. Cox 3. 'The Prize', D. Yergin 4. 'Are Your Lights On?', D. Gause, G. Weinberg 5. 'Becoming A Technical Leader', G. Weinberg

* The Pragmatic Programmer * Becoming a Technical Leader * In Search of Stupidity * Hackers & Painters * Blockbusters * Joel on Software: And on Diverse and Occasionally Related Matters That Will Prove of Interest to Software Developers, Designers, and Managers, and to Those Who, Whether by Good Fortune or Ill Luck, Work with Them in Some Capacity * The Best Software Writing I * Behind Closed Doors * Managing Humans * The Mythical Man-Month * Peopleware: Productive Projects and Teams * The Non-Designers Design Book * Founders at Work * Good to Great * Dreaming in Code * The Art of the Start * Maverick * The Design of Everyday Things * The Art of Project Management * The Art of Innovation

"Becoming a Technical Leader" by Gerald Weinberg Unconventional perspective on management "How Buildings Learn" by Stewart Brand One of the best books about designing long-term architectures. Excellent coffee table book "Envisioning Information" by Edward Tufte "Walt Disney" by Neal Gabler Excellent biography of maybe the greatest imagineer ever "The Art of Software Testing" by Glenford J. Myers ~100 page classic. The central premise is that the successful test is one that finds bugs/issues not one that doesn't.