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.

have you tried actually helping them instead of just complaining?

you're still blaming the devs? it's about prioritizing triaging effectiveness not just checkbox docs being referenced.

sounds like someone needs a raise and a vacation. maybe they should file an incident ticket for

same tho and i'm starting to think it's not just lack of doc review. It's a complete lack of testing before push to prod.

uh, have you considered that maybe these devs aren't reading the doc because it's trash or outdated?

same devs who manage to get stuck in (air quotes) "recommended" workflows

it's like they think the doc is a productivity tracker or something. "oh, 30 minutes of reading was too much, might as well just call you

yeah, i'm pretty sure the documentation was written by elves who only come out at night to refresh

i know, right? and they always submit it as a P1 even when it's clearly not an emergency. like, have you tried turning it off and on again?

sounds like you need to be more patient and understanding. not everyone is as familiar with the docs as you. try working with them to find solutions instead of complaining.

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

maybe they're trying to keep you on your toes 🤷‍♀️

lmao like they'd read the docs even if the server was on fire

same energy here, but can we also acknowledge that the docs are sometimes outdated or unclear as

are you holding the devs accountable for not following process or just suffering in silence?

mate, the devs r too busy playing minecraft to read the docs.

have you considered actually fixing the underlying issues instead of relying on docs to deflect blame?

same lol, and it's not just the devs, i've had managers file p1s with 'how do i fix this?

did you guys even test this crap before pushing it to prod?

idk, man... sounds to me like maybe the docs are the problem, not the devs. just sayin'.

Are you kidding me? Documentation isn't a substitute for common sense. They don't read the docs. They either do their jobs or they shouldn't have jobs.

sounds like they're following the official docs-to-code pipeline: RtFM -> Ctrl+C -> Ctrl+V

sounds like you need to get off your high horse. maybe the devs are just trying to do their job and need some help. ever consider that your docs could use some work too?

preach! i feel you, but it's not just devs... ppl in general need to learn to troubleshoot before hitting the panic button

can't say I'm surprised, most of these 'urgent' issues would be caught by a simple type checker

deadass, you ever think maybe the docs are too confusing? just saying, if the devs can't figure it out, maybe it's time

same here, but let's be real, half the time the docs are outdated or unclear anyway

devs are tired and underpaid, not lazy. maybe we should focus on making the documentation less terrible instead of expecting people to be perfect

documentation? what documentation? we have documentation?

wow sounds like you're having a really frustrating shift. but let's not blame the devs here. maybe the docs arent as clear as they could be.

lmao RTFM should be a valid resolution for at least half of those tickets

maybe they're just really passionate about getting to know you better

this is exactly why we can't have nice things. you're more mad about reading tickets than the

Are you asking the devs to do way too much legwork or is the actual documentation just really, really bad?

same, and it's even more frustrating when the issue is literally the first thing mentioned in the

same, and half the time it's just a misconfigured env var or someone didn't cache invalidate properly

i'm guessing the devs are just waiting for the documentation to automatically write itself and save them a step

Thought the on-call flowchart was just a fun little activity the org devs threw in for remote workers?

did you even try to troubleshoot it yourself before filing a p1?

man, sounds like you're having a rough time. but maybe those devs are just stressed too, you know?

i feel you, it's like they think the oncall person is magic or something.

have u tried turning it off and on again? 🤖

yeah for real, the docs are there for a reason. what's the point of having a knowledge base if no one's gonna use it?

agree but also like, have you guys ever tried dealing with a sr leadership team that's only

dude, have you read the docs yourself lately? maybe the devs are just as confused as we are

yeah, not every dev is fluent in corporate documentation, and a P1 incident isn't the time to expect a tutorial.

do you think maybe you could give them a little more guidance on the documentation instead of just venting about it? i'm sure they're just trying to get their work done too.

yeah, it's like they think the documentation is just for decoration or something.

fr tho, the docs are right there. i swear these devs just want to see us scramble.

u think maybe they're just too busy tryin to meet their sprint goals to bother with the docs?

dev documentation? i thought that was just for show tbh

you think it's the devs not bothering to read the docs or the docs just being really bad?

for real, the devs need to chill. it's like they never even heard of a readme before.

exactly why do we keep hiring people who think documentation is 'optional'?

have you considered making the docs more accessible or user-friendly, or is it just assumed that people will magically know where to look?

did you even try to reproduce the issue before calling it p1? how about you take a look at the docs yourself first before dumping it on us.

same here! it's not just about documentation, though - sometimes you need to hold people accountable for their own troubleshooting

sounds like someone needs a vacation. maybe try turning the computer off and on again and 😉

are you implying that most devs are incompetent or just lazy?

maybe they're looking at it, but the docs r trash and need a total overhaul

guess that's what happens when your google-fu is weaker than your coffee-fu

no way, i've gotten more than a few bad tickets from reading the same doc 10 times, it's not that devs don't care, it's just we're

i feel you, it's not just dev frustration, operations team gets burned too. seems like some devs are just accepting of "getting it fixed now" attitude and ops team pays for it later.

have you talked to the devs about it or are you just getting angry on twitter?

maybe they saw the documentation but couldn't understand it. on-call is the real p1 incident.

who needs documentation when you have intuition... or google

are you actually surprised by that?

are you kidding me? those devs are probably just trying to get their shit done and don't have all day to read a 500 page pdf that's

same here, it's like they're expecting us to spoon feed them solutions. discipline in testing and triage would save everyone so much time and headache

yea thats not usually how it goes, a lot of people in IT are still figuring things out as they go along.

that's not fair to devs, most of us genuinely need help quickly, docs can be out of date or incomplete, cut us some slack and help us out.

tbh i'm right there with you, dealing with unnecessary "emergencies" is the worst.

totally with you on that. at least for us, it's not even the quality of the tickets that's the problem, it's the sheer volume of un-actionable info that devs feel the need to attach to them

do you even know what's in the docs? have you actually walked them through it or just assume

do you think it's the devs or the fact that the documentation is 500 pages long

are you kidding me, 10 pages of docs and still devs need your "help"?

have you guys considered making the docs more accessible or rewriting them in a way that's easier for non-tech folks to understand?

is it a requirement to have a phd in throwing corporate jargon at on-call devs before you can file

tell me you dont think the real issue is the devs being poorly trained, not just too lazy to read

I'm pretty sure the doc is still in beta, dev is just trying to get early access features

i've worked in IT and trust me. Devs are too often left to figure stuff out on their own because

agreed, but have you tried writing docs that're actually worth reading? I've found that clear, concise language and examples go a long way in reducing those 2am pages

do you actually have a plan to improve the docs or are you just complaining?

do you even know what it's like to be on-call? how abt you try fixing all these bugs for a change

I swear the epic legacy of our team's previous incidents was that they got funneled into a ticket factory where manuals went to get mercilessly ignored.

i deal with it too, but have you tried implementing a mandatory 'before filing a P1' checklist? Just saying.

are they even reading the error messages or just clicking 'submit' and hoping for the best?

yeah no kidding, i've started just emailing them links to google with the words "what is "

Yeah, it's so frustrating when devs don't check the docs first. But I also think a lot of these issues could be prevented if the documentation was more user-friendly and

ya know, maybe it's not that they're not bothering, maybe the docs just aren't as clear as y'all think they are.

that's not on the devs, maybe the docs are shit or unreadable if they're still filing p1s after

docs are likely outdated or unclear, devs aren't the problem

lmao maybe the docs are just using pokemonmaster-level rplos and they need an expert like you to translate

lol sounds like you need to add "can you please try restarting your computer?" to your copy/paste queue 🤣

at least the developers are consistent, right?

we need to add "don't google" to the on-call doc

i know right?! i feel like i should start charging them for my on-call time. maybe i'll start a 'learn to google' workshop.

wtf dude, maybe the docs suck. have you tried actually helping people instead of just bitching?

are you yelling at your colleagues on a public forum

it's not like they didn't read the docs, they just followed the standard dev protocol: 1) click random buttons, 2) file P1, 3) profit?