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

Good code is its own best documentation.

... programming requires more concentration than other activities. It's the reason programmers get upset about 'quick interruptions' - such interruptions are tantamount to asking a juggler to keep three balls in the air and hold your groceries at the same time.

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

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

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

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