
How to be sure your first important project isnþt your last.
Software Project Survival Guide - for software specific issues. (Don't be discourged by all the documents it discusses.)
I've never been under the impression that he figured it all out on their own, or that they captured the end-all, be-all of how to make software. Some of the things he wrote about have evolved tremendously over the years. But I still get incredible value of revisiting those books and reinforcing better engineering practices and habits he evangelizes.
Principle by Ray Dalio.
When Coffee and Kale Compete by Alan Klement.
Spark by Dr John J. Ratey, Eric Hagerman, John Ratey.
The One Thing by Gary Keller, Jay Papasan.
The Mythical Man Month by Frederick P. Brooks.
A Dozen Lessons for Entrepreneurs by Tren Griffin.
Software Project Survival Guide by Steve Mcconnell.
The Undoing Project by Michael Lewis.
I Wonder What I'm Thinking About? by Moose Allain.
Truth, Lies & Statistics by Lee Baker.
On shortness of life by Seneca.
McConnell, Steve. Software Project Survival Guide. Redmond, WA: Microsoft Press, 1998.
Maguire, Steve. Writing Solid Code. Redmond, WA: Microsoft Press, 1993.
Ranade and Nash. The Elements of C Programming Style. New York: McGraw-Hill, 1992.
Kernighan and Plauger. The Elements of Programming Style. New York: McGraw-Hill, 1982.
Caner, Cem, et al. Testing Computer Software, Second Edition. New York: Wiley Computer Publishing, 1999.
Hunt, Andrew, et al. The Pragmatic Programmer. Reading, MA: Addison-Wesley, 2000.
Holub, Allen. Enough Rope to Shoot Yourself in the Foot: Rules for C and C++ Programming. New York: McGraw-Hill, 1995.