A "no blame" culture helps greatly in this regard... Some people unfortunately (with cause) fear loss of job if they own up to a mistake. I do agree with John, but some companies (that I don't ever want to work for, and I could "name names") would regard such honesty as "career-limiting"...
- Will -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of John Stoffel Sent: Wednesday, October 24, 2012 3:12 PM To: Doug Hughes Cc: [email protected] Subject: Re: [lopsa-discuss] Fwd: [TUHS] unix horror stories The big thing I as a mentor would want the newer SysAdmins to take away from these stories is personal responsibility. When you screw up, accept it. Talk about it to your bosses, peers and colleagues. Acknowledge publically that you screwed up, but then talk about how you fixed (or were helped in the fix by someone else) the issue and recovered from it. I've seen too many people who were willing to sweep issues under the rug, try to ignore that something happened, or evade taking responsibility for their actions. We all screw up; senior, junior, newbie, grey beard. We're all going to make mistakes. How you respond to them is the true measure. Stepping up and accepting responsibility in an honest and forthright manner is the *best* thing you can do when it hits the fan. Then go and try to make it so that it's harder to screw up that way again in the future. John _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/ _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
