I get an email about once every week or two from one of my coworkers asking what to do about an issue. Nearly every single issue would have been resolved if they just read even the first few instructions.

My favorite is a specific tool we use to review the financials. It relies on Scripting.Dictionary which is only present in .NET 3.5.1 or prior. The very first instruction on the file says you need to download it. There's even a very handy button right there which will take you to our software center to install it.

Yet every single time someone gets a new laptop, they immediately assume that the file is broken.

[–] therealzordon@lemmy.world 6 points 2 months ago (1 children)

If you hear about it that much, why not make the script check for .NET before crashing?

[–] droans@lemmy.world 3 points 2 months ago

It's not worth the effort and testing. People would only experience it once every 3-4 years, depending on when they get a new laptop. Must still shouldn't have to worry since other software would install that version of .NET already.

Plus, people don't bother to read error messages anyways. Another tool I created would create PDFs of the financials. The first section would be pulled from the EPM and the second would be a data dump of every transaction for each cost center. If the totals don't match to the dollar, the script would throw an error.

90% of the time, it was because the EPM data was being refreshed as it's scheduled to do so every half hour and takes 3-4 minutes. So I had the error message tell the person to just go take a quick break and come back. Still, people would email me saying they don't understand why they're getting the error and it would always be fixed if they just wait.