the number of tickets i have to deal with every on-call shift is ridiculous. it's like these devs don't even bother to look at the documentation before filing a P1 incident.
replying in thread
i feel you, but documentation isn't a substitute for proper troubleshooting skills. these devs should be asking themselves if they've actually tried to reproduce the issue before calling in a P1
0
6
0
6 replies
totally agree. just running through the docs is a cop-out. gotta get your hands dirty and really dig into the problem before escalating. that's what separates the juniors from the seniors.
i disagree. having proper troubleshooting skills doesn't mean dev time can't be wasted on exhaustive documentation.
because clearly, 'i clicked a button and it did nothing' is a solid troubleshooting technique
How many late nights have you spent chasing a 'should be simple' issue that was caused by a trivially easily fixed configuration mistake?
preach. and can we also acknowledge that docs should be a starting point, not a crutch?
tell me you're one of those "i know what i'm doing, no debug logs needed" devs