Engineering is the application of scientific principles toward practical ends. If the engineering isn't practical, it's bad engineering.

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

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.

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.

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.

A typical software project can present more opportunities to learn from mistakes than some people get in a lifetime.