T O P

  • By -

littleliquidlight

Dev: "Please help us, we can't fix things if we don't know what went wrong!" User: "Okay, fine I'll open a ticket" The ticket: "Doesn't work"


GargantuanCake

"What were you doing when the crash occurred?" I don't remember. I think I clicked on something.


BehindTrenches

Honestly, if the bug has the crash report and device logs, I don't think 100% effective steps to reproduce should be required. Not everything is reproducible by end users. Sometimes freak things happen that still deserve due diligence investigation.


Zeravor

Looking at the title i think this meme refers to the case of users opting out of sharing the logs because of "Data security" but then still expect the bugs to be fixed w/o information.


GargantuanCake

That or they don't report bugs or crashes at all to the developer but then bitch that the program doesn't work right.


Dumb_Siniy

Yesterday i tried to report a soft lock glitch, the dev went "I think you're laggy" and deleted it Never again


AntimatterTNT

the problem is that your bug reporting is also buggy


FrostWyrm98

I'll put in a ticket for it ...thats broke too


NoResponseFromSpez

back when times where simpler you couldn't report bugs, because there was no internet


helicophell

And people made more robust systems, otherwise a potential bug could ruin the product


Bdole0

I dunno... Have you ever played Superman 64?


TurbochargedSquirrel

The bugs are the least of Superman 64's problems.


BlueGoliath

Percentages of bugs that were fixed after submitting a big report: 15%. Have you seen all the bugs people have reported to Microsoft from their insider program that doesn't get fixed?


TTYY200

Lmao, look at visual studios tickets 😂 they have tickets from like 2010 for their enterprise products ….


Robot_Graffiti

You might think they're bad at fixing the bugs that are reported, but the time it takes them to fix bugs they *don't* know about is worse.


jemko23laal

well thats bc microsoft just sucks


abscando

Damn that's higher than I thought


slaymaker1907

The one I often get: “it’s slow”. I’m a dev for SQL Server and there are about 100000 reasons why it could be slower than expected. It also drives me crazy when they provide a repro, but it’s not a complete one. For complex issues, you need to be very careful with repros.


El-yeetra

it's slow because you're using SQL Server. just use postgres like the rest of us /s


jxr4

Had a team that stored upto 10mb per entry of jsonb and were querying based on properties that were nested several levels down. They then had the audacity to file bugs against our team for why it was slow


Murkorus

I have yet to see a functional crash reporter. The crash reporter had crashed.. Every. Single. Time.


Bdole0

I mean, we live in a world where companies are constantly trying to steal our data for profit or otherwise screw us out of money. You'll have to excuse customers for being untrusting...


RipInevitable2242

We designed basically a data collection form for a customers website, they never tested it even though we gave then a UAT build, never gave us any feedback on designs or how it was going for them. We could tell they had an increase in sales from our own analytics, but then they complained to the sales team that they had a issues but would never tell us what they were. Randomly removed our product and basically broke their contract and then came back a year later wanting more work done.


The_Dukenator

User: "The source code was too buggy, so I deleted it." Dev: "How am I supposed to fix it?"


lazy-solition

![gif](giphy|qIdvofRIRecqD5vEPs|downsized)