Customers logic:

*Writes on September 13th 9.00am lamenting an issue*

I reply back on the same day, at 11.00am, with a link to download the patch I cooked for them on the spot

* Disappears *

Then:

*Writes on September 17th 2.00pm lamenting another problem, and complains that my program is always giving her problems* (turns out the problem is that her shítty antivirus considers a "threat" literally everything it doesn't know lol)

I reply back on the same day at 4.00pm indicating to either wait until their AV replies to our inquiry, or change or temporarily add an exception to the AV, also providing a VirusTotal link that shows the file is clean according to literally every antivirus on the market minus for her own

* Disappears again *

Them today: «We've been trying to get this thing working for a month now, and because of you we're stuck!»

🪿

Jesus Christ, please give me a telephone that can remotely slap the callers on the face

Top | Newest First | Oldest First

NerdyPotato · M

*checks calendar* September 13th wasn't nearly a month ago.

Elessar · 26-30, M

@NerdyPotato No but they asked for the instructions/manual before (iirc in July) so I guess they've started counting from when they decided to sit on their àss and actually do the thing or idk really

midnightrose · F

Did they not see your correspondence or what?

This comment is hidden. Show Comment

Elessar · 26-30, M

@jshm2 I will add the virustotal scan to the build pipeline, but nonetheless, overzealous AVs isn't really my problem to fix.

If you buy a kitchen and the smoke detector fires any time you cook, would you complain to the manufacturer of the kitchen, or the one of the smoke detector? Because it's pretty much the same situation here. I don't sell AVs.

SomeMichGuy · M

Agreed.

Add a comment...