Stupid fucking project managers, just posting some slurry in Slack:

"User can't get into app!" _sends useless screenshot_

Yeah? And? I have no context on what time this was, what device, where, how, etc. etc. etc. etc. etc.

You want me to just telepathically jump to their location on earth, sniff the electromagnetic spectrum waves to sleuth out what exact requests they made and when to figure out what the problem is?

Just shut up. Shut up

dm user directly if you can, bypass the middlemen

rejected, can't reproduce シ

no srsly, that moment when you asking some follow-up questions results in them closing the ticket because they can't reproduce / recall what they did or tried to do and what went wrong, on a very basic level...

@knuppelsmurf this can lead down a dangerous pass if the user can reach you directly. Also it's only a good idea if you feel comfortable talking to the user. I am not against it, but I would make my PM earning his paycheck ;-p

Just read the error ID present in the screenshot and look it up in the log. As the log contains humanreadable well-formatted and indented output enriched with context-relevant information, the error's cause will be pretty easy to find.

“It’s not working, please fix”

1- Respond with "Cool story, bro"
2- Get fired
...
365- Profit

Start explaining how to get into the app:

First you enter your email in the textfield which says email.
Then your password into the textfield which says password.
Then you press the button which says login.
You are welcome.

I agree but le me play devils advocacy:

The other day we had a known 3rd party issue in our app. A rare one only affecting a small subset of users. It could be explained and resolve easily as long as we got the reports.

Then on Friday we find out customer service has had reports for days that they never told us about cause "we know how you devs hate when we send Incomplete reports so we went out of way to not send anything before we had screenshots" 😁

They spent days asking for details when they could've just said "user has issue with component x" and would've instantly known what it was.

if this has happened to your PM maybe they now think "better send it even if it's in complete in case it's a known issue"

@Wolle Good point. Worked out OK on more occassions than not, still think its a valid option

Please provide exact steps to reproduce the issue.

@Oktokolo all good until "something went wrong"

@devJs: If the the log is useless, the real fix is to make the log useful.

Got same shit when user saw the site differently bc they were using some shit computer from 2012.

"pm can't post a message with the minimum required info for it to be actionable!"
[attached screenshot of their message]