It's OK to figure out murder mysteries, but you shouldn't need to figure out code. You should be able to read it.

Good code is its own best documentation. As you're about to add a comment, ask yourself, "How can I improve the code so that this comment isn't needed?" Improve the code and then document it to make it even clearer.

In software, the chain isn't as strong as its weakest link; it's as weak as all the weak links multiplied together.

Good code is its own best documentation.

Software projects fail for one of two general reasons: the project team lacks the knowledge to conduct a software project successfully, or the project team lacks the resolve to conduct a project effectively.

Even when you have skilled, motivated, hard-working people, the wrong team structure can undercut their efforts instead of catapulting them to success. A poor team structure can increase development time, reduce quality, damage morale, increase turnover, and ultimately lead to project cancellation.

It's hard enough to find an error in your code when you're looking for it; it's even harder when you've assumed your code is error-free.