You are hired on at a multi-billion dollar company - their daily profit is higher than your lifetime gross pay. You are assigned to an older system that is a major service for a large, very profitable system. Surprise, surprise - they don't use strict. Do you
Less than 10% of all developers will do the latter option. Remember - this program was working long before you go there. It makes lots of money. Therefore, it's got to be doing something right.
Furthermore, change is expensive, especially without strict, testplans, and the other trappings that good developers like to have around them. Management is right to be wary of you. If you owned the company, you'd be wary, too.
Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.
In reply to Re: Keeping, and advancing in, your job
by dragonchild
in thread Keeping, and advancing in, your job
by Tanktalus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |