Timeline for I made a possible mistake on a live project at work, how to handle this mess?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 25, 2016 at 21:41 | comment | added | weronika | @AmyBlankenship I didn't assume, I said maybe. It's possible that there was something. | |
| May 25, 2016 at 15:13 | comment | added | Amy Blankenship | -1 for assuming a company that doesn't have checks in place to prevent rookie code from getting to production has a resource that the OP could have checked to know the code would be released. | |
| Apr 24, 2012 at 4:59 | comment | added | weronika | @voretaq7 - True, but in this case I would concentrate on the "what can I do to make sure I'm following the correct procedure" side rather than trying to change the procedure, which may not be taken well from a very new employee. Still, one would hope that the analysis of the problem would make the rest of the team notice any problems with the procedure and they would take the lead on dealing with them. | |
| Apr 23, 2012 at 19:27 | comment | added | voretaq7 | +1 for "Own up to the mistake", analyzing the chain of events leading up o it, and taking steps to ensure it never happens again company-wide (i.e. make sure the "co-worker asking you to change production code at 5-o-clock on a Friday" thing never happens again - to anyone) | |
| Apr 23, 2012 at 15:23 | comment | added | weronika | @STTLCU - yes, exactly that: end up with a reason that's a failure of a process, which you can believably say won't happen again. Of course, there may be multiple answers to some of the "why" questions and more than one failure of process - important to note all of those, too. | |
| Apr 23, 2012 at 12:12 | comment | added | Burhan Ali | +1 for focusing on addressing the problem rather than addressing the blame. | |
| Apr 23, 2012 at 9:25 | comment | added | STT LCU | the final "why?" should lead to an answer like "i haven't asked written confirmation from my supervisor" or any other thing which involves at least a part of company system or hierarchy (anyway, it is not their fault) Try to not worry too much, if they fire a new employee at his first mistake there are many chances it isn't a nice place where to work 40 hrs a week | |
| Apr 23, 2012 at 8:40 | comment | added | STT LCU | just registered to add this comment: Ask yourself "why?" 5 times. it will help you find the answers to the questions which will be most probably asked you (Why did the sistem break? Because I committed untested code. Why did you commit untested code? Because I ... Go on until you find an answer related to a process you failed to follow rather than a personal mistake you did ("i wasn't careful enough" isn't a good root cause, "i didn't follow correctly the "code-review-test-commit process #QA101" is better). This is a good starting point from where to fix issues. | |
| Apr 23, 2012 at 4:18 | history | answered | weronika | CC BY-SA 3.0 |