Untitled.Bat |
Developer, dad & dangerously dopey.....Also awesome at alliteration and assonance . Visit my main website @ http://www.xerxesb.com if you're tech-inclined |
A pragmatic programmer takes responsibility for everything they agree to. You *ALWAYS* have the right to not take on the responsibility, but when you do, you should expect to be accountable for the outcome.
Tip 3: Provide Options, Dont make Lame ExcusesÂ
Always be honest and direct, admit mistakes and offer solutions. Don’t say something can’t be done; explain what can be done to salvage the situation.
Talk to yourself (or cat) about how to voice your problems to your boss, and critically analyse what you say to make sure it doesn’t sound like you’re making excuses.
Challenge
How do you react when someone - such as a bank teller or clerk comes to you with a lame excuse? What do you think of them and their company as a result?
A: It reflects poorly on the company and the perceived lack of care or knowledge of the person. Admitting not knowing but actively seeking a solution at least shows genuine interest in trying to achieve the best outcome despite the shortcomings which lead to the situation.
The Pragmatic Programmer: CH1-1
