Timeline for How do I encourage root cause analysis rather than focusing on short - term solutions?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 29, 2016 at 1:33 | vote | accept | Anthony | ||
| Nov 29, 2016 at 1:35 | |||||
| Nov 29, 2016 at 1:33 | vote | accept | Anthony | ||
| Nov 29, 2016 at 1:33 | |||||
| Nov 8, 2016 at 13:30 | comment | added | RemcoGerlich | Actually "inexperienced developer who didn't get the necessary guidance" isn't the root cause. How come he didn't get the necessary guidance? How come an inexperienced developer could cause damage? | |
| Nov 8, 2016 at 13:08 | comment | added | Cthulhubutt | It could be chalked up to "human error". Think what OP means is actual technical root cause - ie. there was infrastructure "quirk" nobody bothered to mention or didn't even know at a time and that broke the application. Actual things that you could draw a "lesson learned" from. As always chance for common sense judgement to prevail :) | |
| Nov 8, 2016 at 11:29 | history | answered | gnasher729 | CC BY-SA 3.0 |