Remember that statement you made on that tough bug?

I hate these "works for me" assholes.

@Fast-Nop some bugs are machine related so u can't blame the developer guy.

@GiddyNaya of course it's difficult to debug something that doesn't appear on the dev machine. That's still no reason for the dev to shrug it off, but all reason to get his ass up and figure out what's going on.

Last time I had that because neither dev testing nor the regular testing had spotted it, but the customer ran into issues, my final result after two weeks of hunting down that bug was a 10 page technical report.

@Fast-Nop you r actually ryt man.

@S-Homles-MD u ain't serious 😂

@S-Homles-MD to top it off, it wasn't even my project, and the actual dev was on holiday when I got that shit on my desk. But holiday is fucking holiday, and I didn't call him up.

The qa guy is not helping on how to reproduce, the qa guy is an asshole.

The dev is also an asshole, he is not asking how to reproduce.

The creator of this is generalizing too much, also an asshole.

*Sees new issue on Github project*

"It's not working!!!111 Pls fix asap!"

*Tests on own phone, works fine*

*Proceeds to politely ask for a log*

*No response for months*

*Closes issue*

"Y u close this issue? Still not working!!!11 Will uninstall your app if you not fix immediately!"

EVERY FUCKING TIME ...

I love working with strong testers, they help ensure the best product goes to market. I always encourage my testers to go the extra mile, and never chastise them for finding irritating bugs.

@cjbatz u are completely ryt man! I love testers that goes the extra miles. It makes work easy for the developer and also prevents project hiccups always found by the client.