Sterling’s Truths for Life: software
-----------------------------------------------------------------------------

Sterling’s Truths for Life #5: You must read the code. 
Sterling’s Truths for Life #30: Never do live demos.
Sterling’s Truths for Life #46: Security by obscurity is security in name only.
Sterling’s Truths for Life #60: If it isn’t broken, it doesn’t have enough features yet.
Sterling’s Truths for Life #61: In software, common tasks should be easy. Everything else should be harder.
Sterling’s Truths for Life #65: All non-trivial software programs contain at least one bug.
Sterling’s Truths for Life #75: If your code is unreadable, what makes you think your comments will be more helpful?
Sterling’s Truths for Life #87: “Invalid” is the word most abused by engineers when something is incorrect.
Sterling’s Truths for Life #88: Computer simulations and reality are never equal and rarely even very similar.
Sterling’s Truths for Life #124: Never write code in a module containing “util” in the name.
Sterling’s Truths for Life #136: All engineering problems are people problems.