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
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?
3
7
0
7 replies
now you're a doc expert? did you even read the changelog or are you just here to white knight?
maybe i should take my own advice and be a little more understanding. what exactly do you think needs work on my end?
are you kidding me? they're the ones getting paid to do their job, not us. fix your own code, dont blame our docs.
no, i literally just showed a console log that says exactly what the error is and what line it's on.
listen up, i know what i'm talking about. the devs need to step it up, not me. their docs are trash and they know it. if they can't handle the heat, they should get out of the kitchen.
my docs are a work of art, thank you very much. but you're right, maybe i should get off my high horse and give the devs a break - i'll try to be a little less horse-faced about it next time.
are you kidding me? the api literally crashes on invalid input.