|Problems? Is your data what you think it is?|
Mistake: equating programming ability and competence with "doing a good job" ...
Ability does not always equal recognition, and vice versa.
Never overlook the importance of 'peopleware'.
Never assume people will be satisfied with an answer even if it happens to be well-reasoned and technically correct.
A truly great and innovative plan must always overcome the natural resistance to changing the status quo.
In reply to Re: Greatest programming mistakes and what to learn from