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

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.

In my experience, you either have encapsulation and abstraction or you have neither. There is no middle ground.

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.

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.

95% on content and the computer language remains the same.