Had to debug an issue,

*ssh user@domain*
"some wild network connection issue"
*hmm weird.. *
*checks everything again*
*hmm seems alright.. *
*tries again*
*same damn error*
*ssh -v user@domain*
*syntax error thingy on the -v part*
😮
*messages co-worker asking what the fuck could be giving on*
"ey mate check your aliases 😂"
*alias"
"alias ssh="echo {insert network connection issue"*

*loud laughing from the co-worker I messaged*

MOTHERFUCKER 😆

Facts.

I just tried to connect on my own teletype portal 😂 And this is one of the best error messages I've seen lately 😂

When error messages have self-awareness and fix problems by themselve the world will burn but I have less issues to care about.

The most detailed error report I've ever had from a client. He couldn't login to his email, I asked him to send an email explaining what was going wrong, attach error messages, etc.
I got this from him:

"I can't login to my email, why"

Really?! 😑

I once changed all my error messages to say “Processed successfully” because I had a demo yet the software was very buggy.

I bought myself time to fix the bugs later.

#demoHack

- Why don't you write error messages?
- Ehm, ok I'll write them.

My girlfriend sent me this error message from a BIM software which she uses at work. I would like to see more sophisticated error messages from a software with a 4K price tag.

One of the most depressing error messages, maybe? Happened early this morning and I've been feeling sad ever since :-/

Pro tip to error messages #1: keep them simple and short

Pro tip to error messages #2: make them make FUCKING SENSE

*Runs program*

*Nothing happens, no error messages*

Oh boy, this is gonna be fun. A bug with no symptoms.

Windows error messages on point as always..

Got to love Microsoft's error messages.

"Yes....and I'm supposed to do what?"

Read till the last! Never seen such poetic error message ever!

!rant

The Sound of Typing (an original dev parody of "The Sound of Silence")

Hello caffeine, my old friend
I've come to sip on you again
Because my mind continues sleeping
While overpiled work is creeping
And the deadline that is flashing upon my screen
Can't be unseen
Within the sound of typing

Down the lines of buggy code
I quickly switch to debug mode
What kind of moron wrote this function?
For this unnecessary junction?
Wrapped in a condition that will always return true
I need a brew
To forget the sound of typing

Boss said I you do not know
WordPress like a cancer grows
A one page website doesn't need that
Still I wear my debug hard hat
And when I sleep I still see the same terror
Fatal error
Echoed in the sounds of typing

And every time I leave my home
I must launch chrome on my phone
The constant messages and phone calls
The chiming echoes through the halls
While I frantically fix some FooBar'd CSS
BUT I don't have LESS
Deep in the sounds of typing

And when I think I have it done
Some scope creep ruins all my fun
So now I force through an all-nighter
While I forge on like a fighter
But the project I thought was due on next Friday
Changed to Monday
Within the sound of typing

Windows tells me to „contact the network administrator“.
I yell at the machine: „I AM THE ADMINISTRATOR!!!1!“

Why is Microsoft doing this? Instead of telling me what exactly went wrong, the come up with messages like
“Something happened”
“This is not possible”
“Error 0x2342133723”
“Do you want to ask a Friend?”

I really hope the authors of those error messages will burn in hell for that!

So a coworker wrote this -- a function that returns a view if a specific object exists in the database. Now what would happen said object doesn't exist in the database? Forget about returning false and handling it properly, he decides that the function should print (echo) a zero! Not to mention almost all his if-else blocks prints a fucking zero when the if condition is false (there are 8 of them, if you're asking). Error messages? The hell with those.

He is now the PM btw. I've had enough of this shithole.

Designer (to the client): Yes it'll be exactly like this mock up after I hand it over to the iOS developer.

Client: Awesome! Looking forward to it.

* Designer goes to developer *

Designer (to developer): Hey these are the new designs for the app, let me know if you have any questions, ok?

Developer: Cool.

* 1 minute later *
* developer goes to designer *

Developer (to designer): How should error messages or notifications look like?

Designer: Oh we should just email those because it won't look good.

Developer: The fuck? And are you going to design this email service too?

!rant

So this year I had a subject at university called "Linux internal architecture", and for the last assignment I had to write a kernel module and interact with it with a separate program written in C.

Once I had finished and tested the driver, I went on to write the other program, which was supposed to use system calls to read and write data to the module. While debugging this program (~500 lines of code) I reached the level of frustration where you just start printing absurd messages everywhere in your code to see what's wrong. So for example instead of printing "This error happened in this function", my error messages were more like "Fuck this fucking function it doesn't fucking work".

Guess who forgot to delete all those messages before sending the code to the teacher...

Also, if a specific mode is selected, the program enters a while(1) that, apart from doing what it's expected to do, also creates a file in the user's home directory called something like 'motherfucker' and appends the words 'fuck this shit' to it. INFINITELY.

I really really hope this teacher doesn't try to run the program in his own computer, or he's in for a big surprise.

You can't imagine how many lines of pure and utter horseshit, seemingly written in PHP, I had to dig through this whole weekend. (relating to my 2 previous rants)

How is it even possible to write code this unbelievably ugly?

Examples:
- includes within loops
- included files use variables from parent files
- start- and endtags separated to different files
- SQL queries generated by string concatenation, no safety measures at all (injection)
- repeating DB calls within loops
- multiple directories with the same code (~40 files), only different by ~8 lines, copied
- a mixture of <?php echo ... ?> and <?= ... ?>
- a LOT of array accesses and other stuff prefixed with "@" (suppress error messages)
- passwords in cleartext
- random non-RESTful page changes with a mixture of POST and GET
- GET parameters not URL-encoded
- ...

My boss told me it took this guy weeks and weeks of coding to write this tool (he's an "experienced dev", of course WITHOUT Git).

Guess what?
It took me only 20 hours and about 700 lines of code.

I must confess, since this task, I don't hate PHP anymore, I just simply hate this dev to death.

Addendum: It's Monday, 5:30am. Good night. 😉

"I want my API to return insults as error messages if they forget shit"

Uh no, I prefer helping them out by writing proper documentation than sending a giftbox with me flipping them off like Linus Fucking Torvalds for their spaghetti usage of your API

Some days I feel like I work in a different universe.

Last night our alerting system sent out a dept. wide email regarding a high number of errors coming from the web site.

Email shows the number of errors and a summary of the error messages.

Ex. 60 errors
59 Object reference not set to an instance of an object
1 The remote server returned an unexpected response: (413) Request Entity Too Large

Web team responds to the email..

"Order processing team's service is returning a 413 error. I'll fill out a corrective action ticket in the morning to address that error in their service. "

Those tickets are taken pretty seriously by upper mgmt, so I thought someone on the order processing team would point out the 1 error vs. 59 (coming from the web team's code).

Two hours go by, nobody responds, so I decide to jump into something that was none of my business.

"Am I missing something? Can everyone see the 59 null reference exceptions? The 413 exception only occurred once. It was the null reference exceptions that triggered the alert. Looking back at the logs, the site has been bleeding null reference exceptions for hours. Not enough for an alert, but there appears to be a bug that needs to be looked into."

After a dept. managers meeting this morning:

MyBoss: "Whoa..you kicked the hornets nest with your response last night."
Me: "Good. What happened?"
<Dan dept VP, Jake web dept mgr>
MyBoss: "Dan asked Jake if they were going to fix the null reference exceptions and Jake got pissed. Said the null reference errors were caused by the 413 error."
Me: "How does he know that? They don't log any stack traces. I don't think those two systems don't even talk to one another."
<boss laughs>
MyBoss:"That's what Dan asked!..oh..then Jake started in on the alert thresholds were too low, and we need to look into fixing your alerting code."
Me: "What!? Good Lord, tell me you chimed in."
MyBoss: "Didn't have to. Dan starting laughing and said there better be a ticket submitted on their service within the next hour. Then Jake walked out of the meeting. Oh boy, he was pissed."
Me: "I don't understand how they operate over there. It's a different universe.
MyBoss: "Since the alert was for their system, nobody looked at the details. I know I didn't. If you didn't respond pointing out the real problem, they would have passed the buck to the other team and wasted hours chasing a non-existent problem. Now they have to take resources away from their main project and answer to the VP for the delay. I'm sure they are prefixing your name right now with 'that asshole'"
Me: "Not the first, won't be the last."

Most useless things are mysql error messages lol

Dear backend dev:
No data is not an error for fuck sake. Don't want 404, or messages if the search criteria filters out all values. Give me a empty array.
Is this hard to understand that we need a team meeting to discuss?
Godamit

Years ago we deployed this system with a SQL DB on a separate windows server.
Every now and then we had error messages saying that the system could not connect to the db. It was going on for about 5 minutes or so and then the db was up again.
We built a bunch of fallback logic to handle it gracefully.
Then one day one of the guys was in the "server room". It was not a real server room but like a dedicated office in another building.
He saw how the cleaning lady came in, unplugged the server's cable from the wall socket and plugged in the vacuum cleaner...

Working on adjusting a shell script to my needs.

The fucker quits execution after an apt update command is ran.

No reason, it just fucking quits. No error messages or whatever, nothing.

This script can go suck a cock.

A few years ago, I used alert('Well that sux balls'); to debug a CMS custom module. Finished the project and went with the sales manager to demo the app to the clients board of directors. Trust a sales manager to find a bug during a live demo that QA didn't find...
All my temporary error messages are now boring and functional.

Non selectable, non clickable links in error messages. *sigh*

Fucking pieces of shit, if I would have a list of developers that add "Whoopsie daisy, tinky winky compiling stuffie" as error messages, installer steps or as a checkbox in their github issues, I'd break their fucking back and keep them alive, just to ram fucking burning nails into their eyelids and then blast just enough power through them to make them burn and evaporate alive.

So its not "Unable to connect to servers"

Its downright IMPOSSIBLE..

Okay 😑

I'm so sick of all these fat frontend websites.

Transferring dozens of megabytes of mostly unused libraries is not acceptable.

A browser tab crunching up CPU time because everything must be "beautifully animated" (🤢) and processed without involving page reloads/backend is not acceptable.

A response time of over a second is not acceptable.

Cryptic error messages and random popups asking you to reload your page, not acceptable.

Sticky elements/popups breaking access on small screens is not acceptable.

Running hundreds of ajax calls per minute as heartbeats/probes
and crashing the page when the internet has a hiccup, not acceptable.

Fuck Asana, Fuck Twitch, Fuck LinkedIn, Fuck Youtube, Fuck the dozens of other SPAs which unload their truckload of diarrhea into a tab, yet fail to load crucial functionality about half of the time.

Fuck any page that breaks when you block Facebook, Doubleclick, Twitter or Google Analytics. To hell with websites depending on cookies or javascript loaders to display anything.

I want webpages to be interactive informational documents again.

Fuck off with your apps.

If you want to make an app, learn to use a real language, and get the fuck out of my browser.

1. Fucking MySQL database clusters.

There's nothing fun about MySQL clusters. Sometimes they start producing deadlock errors for no apparent reason... well, there's probably a reason, but it's never a transparent easy to find reason.

What was even less fun is that those errors took down a Sentry server. When your error log server goes down through ddos from your database messages, it's time to rethink your setup.

2. Wiring up a large factory with $2 arduino clones, each with a $2 esp8266 wifi chip, with various sensors for measuring flow of chemical solutions (I wanted cheap real time monitoring as an early warning system next to periodic sampling).

The scaling issue was getting over 500 streaming wifi signals to work in a 55c moist slightly corrosive atmosphere with concrete and steel everywhere, and getting it all into a single InfluxDB instance for analysis.

I was taking an introductory programming course. One assignment was to do a little payroll program, including some data validation. The program was supposed to accept terminal input and send output back to either the console or a printer.

Suddenly the printer began spewing out paper like crazy. One of the students (a particularly mouthy woman) had programmed a less-than-helpful error message ("YOU ARE WRONG") and then not provided any exit from the error-checking logic -- the program just re-read the last (failing) input and re-tested it. All in all, it was a very nice infinite loop.

After spitting through about fifty pages of "YOU ARE WRONG," somebody cut power to the printer, and the instructor had to flush the print queue manually. He went back to the student and asked if she had tested the program by sending the output to the console before trying to print it, and she said, yes, she had tested it on the console and ended up with a screen full of "YOU ARE WRONG" messages. Why, then, had she sent her output to the printer? "I thought I would be daring!"

I'm sure this has probably been posted before, but it never fails to drive me nuts, and customers never stop doing it, so:

Why do end users think "it's broken" is all they have to put into the support ticket?

It's a web app, not a goddamn pretzel.

If the turn signal on your car stops working, do you drop your car off at the mechanic, hand them the keys, and say "its broken, fix it!"?

While I'm on the topic, "I tried to do {x} and it gave an error" is better than "its broken", but still: why do you think what the actual error says would be completely irrelevant, especially when we put in the effort to give you relatively meaningful error messages?

I mean, is "there was a problem sending the email" so utterly gibberish to you that it is indistinguishable from "error: 0x000351e6"?

If so, I'm sorry, but you're too stupid to use a goddamn computer!

Fuck you and your fucking non-specific error messages.

Feeling - Murderous 😡

What in the fuck? Do all beginner programmers just flat out not read error messages?

"Users don't need or like detailed error messages. Just use a generic phrase like `an error occurred`. Visually it looks nicer and they won't read it anyway"

- Lead UI / UX Designer, large m.n.c, 10+ years experience

Funny error messages in a function I wrote long ago. Hehe

This is what happens when you decide to send error messages as url value

I'm speechless :\

Thanks Ryanair for these very exhaustive error messages.

Legacy code.

Honestly though, this is some of the better legacy code I've worked with at this company. It's a nifty alert system wherein you can trigger sending messages to subscribers of that alert via whatever means (phone/email) they've entered.

I'll save you the technical analysis of its internals, but suffice to say it's actually pretty nice, with good separation of concerns, internal logic hidden away, dead-simple public interface, etc. documentation is kinda crap, but it exists (!), so that's a nice change.

but.

For some unknown and bloody bizarre reason, the thing breaks when a user wants both sms AND email notifications. Either by themselves work totally fine, but both together? nonono. Email alerts give ArgumentErrors, so something internal isn't correct, and SMS alerts complain about uninitialized Twilio::Error constants.

but.
they both work fine otherwise?

also, the two notification preferences aren't stored on the same object anywhere. if a user wants both, the user creates two AlertContact objects with different info, and when performed, the Alert basically iterates over these and does its thing for each, so there is no knowledge shared between them. totally should work the same regardless.

idfgi.

ALSO.
AND THIS PART REALLY PISSES ME OFF.

WHEN THERE'S AN ERROR, THIS THING DOESN'T LOG IT. IT STRINGIFIES THE ERROR OBJECT (basically just extracting the message) AND INSERTS THAT INTO THE DATABASE INSTEAD. WHAT THE CRAP.

So, I don't get a stack trace, line number, or anything. just the basic error message. instead of my alert text. because of course that makes sense and totally helps debugging.

aklsjfak;sldfj.
legacy code.

The allocation of my time while 'programming':
50% Reddit
25% Stack Overflow
24% Error messages
1% Actual coding
100% Frustration

Java:
Primitive streams. Their need to exist is a monument to legacy failure.

VB.net
OrElse and AndAlso short-circuiting operators. The language designers were too fucking lazy to process logic, so they give specific keywords for those cases.

PHP
Random Hebrew error messages

JS
Eval. It can be used responsibly, but most of the times you see it it's because someone fucked up.

C#
Lack of Tuple destructuring in argument specification. Tuples were added, and pattern matching was added, and it's been getting better. The gear grinding starts with how Tuple identity assignment in arguments is handled. Rather than destructuring into the current scope, it coalesces the identity specification into a dot property of whatever the argument name is. This seems like an afterthought given they have ootb support for ignore characters.

Typescript
This will probably be remedied in the next version or two, but Tuple identity forwarding between anonymous scopes normalizes to arrays of union types, because tuples compile to typeless arrays. It's irritating because you end up having to restate the type metadata in functional series even when there is no possibility for any other code branch to have occurred.

Why do users find it so hard to understand short and clear error messages that are in place to inform them what's going wrong? Why do they instead waste my time when the message clearly says that the password is too short and hasn't got any special characters? FFS!

'hey honey look what i made! It works!'
- fiance looks, error messages over error messages, program crashes, files disappear, data loss, pure horror

To this day I don't know what happened. I had to restore my project and re-write the last half hour.

Just noticed that I've been swapping the error and success messages for the past hour.... Yeah I should really go to bed now..

The line numbers in error messages look like I’m time traveling.
.... line 1987
.... line 1883
.... line 1642
.... line 2007

Whenever I'm trying new tech at work I don't keep interrupting people ta help me with error messages because ITS A FUCKING NEW TECH AND NO ONE WORKS WITH THAT SHIT!

WHY THE FUCK YOU KEEP ASKING ME FOR HELP WITH YOUR FUCKED UP NODE SHIT AFTER I TOLD YOU THAT I DON'T LIKE IT? STOP IT!

Ok so I'm trying to focus on reading docs on a game engine to do some game dev

And wife busy disturbing
wife: come do this for me
wife: come sit with me
wife: come talk to me
wife: come massage me
wife: come do this to me

Its like a stream of endless error messages

I really hate these "an error occurred" messages, guessing I'll talk with IT later today.

Meanwhile, the dialog should show

When the developer is lazy to type error messages.

Perfect job is when sandbox and production api endpoints works the same.

Fuck all api endpoints where their sandbox works differently than the production.

Fuck all those error messages that appear only in production, despite faithfully following the documentations.

Fuck the gateways where their sandbox is more stable than the production.

Fuck the endpoints whose api parameters differ in what they accept between sandbox and production.

Fuck those manuals that does not document these diferrences.

Fuck those developers and support team who don't know how to support integrators. They don't even know how their apis work!

I cannot wait to leave my job. I love my bosses, but the customer service people are the fucking worst!

Since I'm the only developer day in and day out I hear the same problems of people forgetting how to do so something over and over and over. Then they yell at me because they say I don't train them enough.

I WASTE 8 HOURS A WEEK RETRAINING YOU SHIT HEADS BUT NONE OF YOU TAKE NOTES IN THE MEETINGS!!!! ITS NOT MY FAULT IF YOU THINK YOU PEA SIZED BRIAN WILL REMEMBER ANYTHING!

AND ITS NOT LIKE THE SYSTEM IS HARD! THERE ARE TOOLTIPS AND CUSTOM ERROR MESSAGES THAT YOU JUST CHOOSE NOT TO READ!

I am just so burned out of answer the same damn questions day in and day out

The lead dev left the company two weeks ago. His last hurrah involved committing a bunch of complicated code into our API. The code he writes is generally overly coupled but this particular code is INSANE.
It is so coupled that the tests for it almost mock the entire application end to end. I only found this heap of garbage when the deployment tests were hung after I made a simple change in a totally unrelated file. THEY DIDNT FAIL. JEST GOT INTO A STATE WHERE IT CANT CONCLUDE AND HAS NO ERROR MESSAGES. We are taking about entirely different parts of the code. As far apart in the code as it can get. It took six hours of playing Sherlock Holmes to figure out what was breaking.

He got the most junior developer to approve the garbage PR as well.

When your own error messages come handy while casually using your own app :p

//this one is a bad json resposne

There was once a young man who, in his youth, professed his desire to become a great writer. When asked to define "Great" he said: "I want to write stuff that the whole world will read, stuff that people will react to on a truly emotional level, stuff that will make them scream, cry, howl in pain and anger!" He now works for Microsoft, writing error messages.

I have difficulties to process why some of my developer colleagues have such difficulties reading and processing error messages.

It says what is wrong RIGHT THERE MAN!

I have gotten some ridiculous rejections to my job applications recently - some of them were quite nit-picking gatekeeper sort of answers to the assignments like "oh you haven't used aria-label in a proper way" or "oh your error messages were not clear enough".

Then I see the same positions being open still after 5 months. This happened 4 times in a row. What is going on? Why do companies place job ads and waste time interviewing people, if they don't want to hire anybody? Am I missing something here? 🤔

MySQL has the absolute worst error messages.

"You have an error in your SQL syntax; check the manual that corresponds blah blah near '(some random code line)'".

How vague can you be? It doesn't help that I always find the error in a completely different place to where the message says it is.

I’m sick of these kinds of error messages. “Could not be downloaded at this time.” Ok...but why? Are the stars out of alignment? Did the CEO of the company decide that every other Tuesday at noon, you can’t download this app?

How hard is it to give a reason in the error message??

No rant, just appreciation

A thank you to the senior developers out there who take the time to help us juniors out, to look at our (potentially) shitty code and point out how to improve it.

To help us to see the bigger picture and maybe take a more lengthy approach to a problem that'll pay off in the end.

And lastly, thanks for allowing us to learn from your years of bug splatting, stack tracing, null pointers and error messages.

You guys rock

Now I know for sure that my coworkers can't read error messages.

Every fucking time git doesn't push or pull properly they can't figure out what's going on, almost one year since we migrated to git ... come on... read the fucking message!

Everyone talks about their hate of js but like python is honestly just as bad.

- shitty package manager,
* need to recreate python environments to keep workflows seperate as oppose to just mapping dependencies like in maven, npm, cargo, go-get
* Can't fix python version number to project I.e specify it in requirements
- dynamic typing that gets fixed with shitty duck typing too many times
- no first class functions
- limited lambda expressions
- def def def
- overly archaic error messages, rarely have I gotten a good error message and didn't have to dive into package code to figure it out
- people still use 2.7 ... Honestly I blame the difficulty of changing versions for this. It's just not trivial to even specify another python version
- inconsistent import system. When in module use . When outside don't.
- SLOW so SLOW
- BLOCKING making things concurrent has only recently got easier, but it still needs lots of work. Like it would be nice to do

runasync some_async_fcn()
Or just running asynchronous functions on the global scope will make it know to go to some default runtime. Or heck. Just let me run it like that...

- private methods aren't really private. They just hide them in intelisense but you can still override them....

I know my username is ironic :P

In the 1990s code editors on the Mac could insert the omitted function prototypes into a header file with one command; and even automatically keep the header declaration updated when you changed the source definition (name, parameters, etc)

Today in Xcode you have to copy and paste the stupid function header definition from the source code into the header file. What happens if you leave the "{" that got copied accidentally? OMFUCKING LORD, it triggers all sorts of erroneous errors in all the **source code** files where it is included instead of the header with the stray "{"

I started to question whether nor not I knew C, if gravity worked, if the sun would come up. I wasted a day of dicking around in StackOverflow trying to chase down all these insane error messages which make no sense in Xcode.

I just **happened** to see at the bottom of one of the source files, after all the erroneous error, a very important error:

"};" Expected

So I started deleting code from the bottom up in this source file, same error every time. Got to the point where the includes were all that was left.

FUCK YOU XCODE and the hacks that designed that horrendous piece of shit

Xcode is only free if your time is worth absolutely nothing.

Because DevOps in a lot of organizations is really “help desk for clueless developers”, conversations like this happen a lot:

Dev “hey the thing seems to be not working right”

Me “what does that even mean? I need you to be a good deal more specific. What thing. What isn’t working?”

Dev “I dunno”

Me “Are there error messages?”

Dev “yes”

Me “….would you like to share them with me?”

Dev *sends error*

Me “ok did you actually read this error message?”

Dev “yes”

Me “…so you’re good then? It says you’re trying to use a variable that hasn’t been declared yet. You should fix that. “

Dev “…”

Me “good luck”

Program;
A magic spell cast upon a computer to enable it to turn input into error messages

Why is it that newbies always fail to read their error messages and bring their laptop saying something went wrong.

I work as the entire I.T. department of a small business which products are web based, so naturally, I do tech support in said website directly to our clients.

It is normal that the first time a new client access our site they run into questions, but usually they never call again since it is an easy website.

There was an unlucky client which ran into unknown problems and blamed the server.
I couldn't determine the exact cause, but my assumption was a network error for a few seconds which made the site unavailable and the user tried to navigate the site through the navbar and exited the process he was doing. It goes without saying but he was very angry.

I assured him there was nothing wrong with the site, and told him that it would not be charged for this reason. Finally i told him that if he had the same problem, to let me know instead of trying to fix it himself.

The next time he used the site I received a WhatsApp message saying:
- there is something clearly wrong with the site... It has been doing this for so long!
And attached was a 10 second video which showed that he filled a form and never pressed send (my forms have small animations and text which indicates when the form is being send and error messages when an error occurs, usually not visible because the data they send is small and the whole process is quite fast)

To which I answer
- It seems that the form has not been send that's why it looks that way
- So... What an I supposed to do?
- click send
It took a while but the client replied
- ok

To this day I wonder how much time did the client stared at the form cursing the server.

I realized why do i like java the most. Error messages are easy to read and consistent. Never really had to look up an error because the message tells you exactly what is wrong. Hell, you could write a script to self-repair the errors because they are so obvious to fix.

Now compare that to my current stack, python and js....

Whenever my friend messages me to debug his code or to correct the errors, I google the line with the error, open the first result and copy and send the solution to him.

Now he thinks I'm a badass programmer😂

Microsoft error messages have to be the worst I've ever seen. "Sorry, something went wrong." "Oops, something's not working". Thanks, do you care to elaborate? Would really help my troubleshooting...

Serveral users complain that the error messages our software produces are completely useless, so I get assigned to improve the error reporting.

Starting the task by checking what's there and how it works together.

Looking through the code I discover 4 completely different error reporting implementations, each having the same intent and promised functionality. All of them are used somewhere, sometimes next to each other. Needless to say: None of the implementations actually implements all it promises.

My favourite part is the setErrorMessage(string) method that is defined in one header and used in many places, which has the implementation

void setErrorMessage(string){}

Fuck my life.

So we have an API that my team is supposed send messages to in a fire and forget kind of style.

We are dependent on it. If it fails there is some annoying manual labor involved to clean that mess up. (If it even can be cleaned up, as sometimes it is also time-sensitive.)

Yet once in a while, that endpoint just crashes by letting the request vanish. No response, no error, nothing, it is just gone.

Digging through the log files of that API nothing pops up. Yet then I realize the size of the log files. About ~30GB on good old plain text log files.

It turns out that that API has taken the LOG EVERYTHING approach so much too heart that it logs to the point of its own death.

Is circular logging such a bleeding edge technology? It's not like there are external solutions for it like loggly or kibana. But oh, one might have to pay for them. Just dump it to the disk :/

This is again a combination of developers thinking "I don't need to care about space! It's cheap!" and managers thinking "100 GB should be enough for that server cluster. Let's restrict its HDD to 100GB, save some money!"

And then, here I stand trying to keep my sanity :/

Making a small update to an ionic app then spending a whole day trying to figure out why a button doesn't work. Tried everything to fix it and got no error messages.

Finally discovered it was because the button was inside a label and not a div.

Yeah, fun times.

literally what the fuck is the point of C++
>takes 3 years to make anything half-functional
>language was made in like fucking 1902 so it's damn near fucking impossible to make anything that works without sifting through bumfuck retarded syntax/libraries
>error messages that tell you absolutely nothing of use and are indecipherable garbage 90% of the time
fuck C, fuck it's retarded downie little brother C++, and fuck the stupid fucking boomers who say you're not a real programmer unless you force yourself to become a masochist by using either one of these stupid fucking languages
"oh but it's fast!!11!1!!" yeah but working with it sure as fuck isn't
half the fucking time if I just stop including certain headers in another file then the compiler throws like literally 400 fucking errors at me even though the thing(s) I excluded had no bearing on whatever the compiler decides it wants to loudly bitch and whine about
"oh but games were made on it!!!!111!" yeah not without fucking horrific spaghetti code and 900000 different libraries and dependancies designed just to make a single fucking window

Some fun facts :

☻ Programmers spend approximately 30% of the time surfing the source code 😁

☻ Progress in programming can be classified into 4 stages:
(a). Complex Programming
(b). Making Progress
(c). Slow Progress
(d). Stuck

☻ Programmers have a tendency to report their problems incompletely

☻ The main error messages, execution times and runtime compilation errors and the average time to solve them

☻ The software maintenance consumes more than 50% of the effort

☻ Ctrl C, Ctrl V, and Ctrl-Z have saved more lives than Batman tbh😇

I can't even deal with this. We just deployed a new update to our system, and everything was going smoothly. And then, out of nowhere, we started getting a bunch of error messages and user complaints.

Why do these things always happen? We spent hours trying to figure out the source of the problem, and it turns out it was because we didn't do enough testing before the deployment. Are you kidding me?

I know that testing can be time-consuming, but seriously, this is ridiculous. It's frustrating when something like this happens, especially when we're under a tight deadline. And to make matters worse, we had to roll back the deployment and start all over again. I just want to throw my computer out the window.

Uuuugghhh!

I've got a puzzle! How well do you know the weird GNU coreutils error messages?

$ rm foo/
rm: cannot remove 'foo/': Is a directory

$ rm -r foo/
rm: cannot remove 'foo/': Not a directory

What am I?

When I launch my startup, I'm gonna insert all kinds of very stupid and weird error messages in place of the actual errors just so the people can have a chuckle instead of being annoyed
maybe someone's gonna post it on reddit or something, I don't mind, that's actually a good thing

Don't you just love it when eclipse gives you these wonderfully informative error messages? Couldn't you at least say something?

```There was once a young man who, in his youth, professed his desire to become a great writer. When asked to define "Great" he said, "I want to write stuff that the whole world will read, stuff that people will react to on a truly emotional level, stuff that will make them scream, cry, howl in pain and anger!" He now works for Microsoft, writing error messages.
```

1. Learn to read and understand the errors and exception messages. While writing code you're going to be facing exceptions most of the time and the real cause of them is under a lot of generic error messages. That and a lot of patience and perseverance.

2. You're going to face clients and bosses that ask you to do a temporary "workaround" even though you know there is a best way to solve a problem even if it takes more time and effort. Don't "crash" against their ideas, try to find a mid-term between the fast and easy work around and the best solution and leave it open to improve it in the future. I have met a lot of developers that let the frustration stops them to be creative just because the approved development is not what they wanted to do.

Error message on Facebook :)

When you let the developers write all the error messages by themselves.

Personally I always ask for help when it comes to writing nice error messages.

Might be more of a self-rant.. We’re developing an application with token-based authentication.
It’s a big an complex authentication model and flow, which we wrapped up a month ago. All of us very proud of it.

All of a sudden none of it worked.
We debugged for days, there were no errors or anything to trace what was happening.

Today we realized that we set the expiration of the token to 20 years.
Aaaand the expiration time is later on converted to epoch.

Guess what happens when you try to use a value > 2 147 483 647 in C#? Stuff blows up, cuz that’s the limit of an int32.

So yeah, feels good having prepared for the Y2K38 bug already, even though we’ll be replaced by AI writing better software than my dumb ass by then.

(To be fair, it was hidden in Microsoft Owin, which could use some error handling and/or proper messages..)

One of the very helpful error messages so far!
🙈🙈🙈

Place: Microsoft, Visual Studio department

Boss: we need to make beautiful changes, and make the development process more simple and beautiful.

Employee 1: let's arrange error messages to be more readable.

Boss: no, I don't need any details of error, just say there is an error.

Employee: But..

Boss: This is genius, do it now.

Me: 😭

Error messages these days are so descriptive.

I’m a fucking idiot read error messages kids

React-Native's error messages are getting ridiculous.

Apparently I have to do yoga otherwise it won't compile.

i was helping a friend who just started learning how to code and i realized that tutorials don't teach you how to read error messages and how to debug. that's stuff we learn from people, it's tacit knowledge. that's crazy to me, because those are such essential skills to a dev and i think just self learning is not enough. maybe coding is even more of a socially dependent skill than i ever thought. looking at it that way, stackoverflow is a good example of that, I can't really imagine being a dev without the dev community

Want to fuck other developers? Then make a quite probable project name illegal without documenting it, nor providing any helpful information in the error messages.

I tried to name my Flutter test project flutter_test. Turns out that that name is reserved (it's a package). Fml. 🤦🏽‍♂️

Raised a support ticket with an api provider about unclear error messages. They were as confused as I was and as the thread continued I essentially ended up debugging thier application for them!

Speaking of annoying stuff in coding. What the fuck is it with the localized error messages?

No. Fuck you. No. Give me the English version so I can google it and find answers from the huge English speaking community instead of the tiny community of my language.

So there’s this SOAP api I have to use (not by choice, and not the only one i have to use) that returns a bunch of XML nodes to confirm the data sent made it and checks out - pretty standard stuff yea.

Now every once in a while it doesn’t respond (as far as I could tell) so today I wrapped a debug around the soap call, error handler and responses and threw a bunch of messages it’s way to try and force it not to respond in order to be able to put some decent error handling in place.

Well it wouldn’t fail.
100 messages .... all responses good
100 more.... all responses good

And then 100 more.... all respond with “x”, plain text not XML as expected!

Wtf is this shit!!!!!

Best:
Really getting into Rust. It has taught me so many things.
1. Null is evil
2. Sum types are amazing
3. Compiler can actually have good error output
4. Multi threading is actually really scary if you don't have a compiler to back you up

Worst:
I had to deal with SSIS. It has also taught me many things:
1. No matter how 'mature' a product is, it can be awful. Simply dump a random error code, the user can figure out what went wrong, no need for good error messages.
2. The modern concept of the database is crap. It's a gigantic global state that is used by everyone and owned by no one.
3. Don't use tools that aren't made to be used with version control.
4. Even when you tell your team that it's bad, you will be ignored.

Getting real tired of having to reteach the basics of relational databases to the same 2 people. You were brought in as the expert in databases and SQL Server, I shouldn’t have to teach you about effing primary keys, secondary keys, many-to-many relationships, and how to join the damn tables in a basic query. Your 5 years of experience are obviously a waste if all you did was select * from bullshit. This is the 2nd week and 22nd you’ve asked the same damn questions. Get your crap together and study your ass off if you don’t know. Google the error messages if you don’t remember how to solve it before coming to me with the same question a 23rd and 24th time. I’m not going to get any work done if all you do is ninja up behind me with your laptop in tow and just spout off the question that could be done over IM or a quick duckduckgo/google search. Headphones in = do not disturb ya rude mother duckers 🦆.

I'm implementing some Italian web servicies.

The server response is "INDISPONIBILITÀ TEMPORANEA" (temporarily not available).

I'm Italian, but I'm not used with localized error messages. When I read this message I tought to a server in a toilet.

Chasing down reference errors in Visual Studio for 20 minutes only to find out it just needed to be restarted.

The error messages lie!

C++, the language where template error messages can be longer than your entire code base

So, according to my customer, the internal app I just released is "far too aggressive and not overly polite to users".

After querying this the client was referring to validation error messages.

Where I've wrote "Set a payment method before creating the order", the client would prefer it to be ""Please set a payment ...".

I guess it's a fair enough observation, but the client's phrasing made me chuckle :)

this fucking senior dev, just send the following messages:

pull development,
Did yarn install
now yarn dev does not work.....

BRO: READ THE FUCKING ERROR MESSAGE!
It's plain English!

Seriously wtf.

The story of my life:
Me(as a child): I wanna write content to which people scream while reading. :D
Me(as a grown up): Ended up writing error messages for windows. (._.')

Earlier this day, I was about to start a new project. So I copied my favourite gulpfile.js into that projects root and installed all dependencies with npm. After running Gulp for the first time it threw an error.

Silly me tried to fix stuff and got googling the error and trying random things... After a break of a few hours I just fucking rerun Gulp and read the fucking error completely. It stood there. The fucking solution just stood there, run "npm blah --force" to reconfigure package blah....

Of course it worked right away and I finally could start working. But this shit took way too long. Why I just can't read the fucking error message. Damn

Issue or Error? Rant story time!

I was working on a windows desktop app, and everything was ok, you know, tests completed succesfully, all in time, etc. The problem was when we showed the demo to one of our clients. He saw several screens and we explained all the features to him.

Client: *Sees a Error pop-up indicating that a remote service is temporarly unavailable (what it has to happen in order to show him how the system would warn him when an external service is out of service)
Client: What’s that?
Lead dev: What do you mean?
Client: Yes. That’s an error pop-up
Lead dev: Yes, it’s a message that tells you that there was an issue connecting to the bank service
C: No, no and no. Please change it
L: Why? Don’t you want the system to tell you when there is a connection issue and why is that happening?
C: Yes, but my employees could lost their minds because of this class of messages!
L: So...?
C: You have to change it
L: Ok. What do you want to change?
C: First of all, don’t put an “Error” icon, put an “Warning” icon, and instead of “Error” title, put... “Issue”
L: “Issue?”
C: Yeah. Don’t put the “E” word, if the users see an “Error” message, they could think that the program doesn’t work, even if it does work.

We all though “WTF?!”

To make the story shorter, we changed all the pop-ups. That took two days.

Is that correct? I know that “Error” sounds hard but, seriously? “Issue: The remote service is not available, contact your bank?”

Only the best error messages here at C 👌

Why is it that other programmers think I’m a wizard when they’ve been struggling with an error in their project for hours and I just read their error messages and tell them where the error is/what they need to do/fix?

My coworker claimed to have experience with R programming on their resume.

Now I don't know R myself but I'm pretty sure what actually happened was they were handed an R program and told how to run it...

Cause they doesn't use functions without being told to, I've had to explain global vs local variables multiple fucking time, and the worst fucking offense in my opinion

THEY DOESN"T READ FUCKING ERROR MESSAGES, so many times there's been an issue in the scripts and when I go to look at what's wrong it's 3 fucking lines down from what they fucking screenshot and spam me on teams with

People who can't read error messages properly and blame your library...

Ah yes, who doesn't like descriptive error messages?

MSbuild makes me want to blow my brains out.

I know it's no longer used in .NET Core and all the lucky people that don't have to deal with .NET Framework can happily move on.

But here I am, a complete idiot. Expecting MSBuild to build the exact same way from the CLI as it does if I run a build in Visual Studio. Expecting the build server to consistently produce the same result as if I built my solution locally.

Demanding meaningful earnings and error messages that don't leave me completely perplexed as to what's actually going on in the compiler.

Fuck me and fuck .NET Framework. Thank you for coming to my TED talk.

Fuck node. Learn to get some real fucking error messages. Ain't nobody got time for that shit

Not only Windows can show this "strange" error messages: Today I got this beauty while importing an SQL-dump.

(Translation: "Error on import: error on statement #1: not an error. Execution will be aborted and the db will be reset.")

Learning Rust.

Holy brainfucking brain melt, those references, scoping and borrowing and cloning and whatnot, because there is no garbage collector, but also no direct memory management.

It's cool, but also hard for a noob coming from the JVM/Android. The compiler error messages are helpful, but I immediately found some cryptic ones that don't help me at all.

German error-messages in VBA.
I didn't want to be productive anyway.

What a great login page:
{"message":"Error logging in."}

on my college days (8yrs ago), i had to study COBOL as part of syllabus....

you had to write lots of codes as header on every simple program you write, define every variable you gonna use (with how much space they need) upfront..

and you can't leave a blank space any where in the code unless it is required!!

best part? you need to start every line of code with 7 blank spaces! and each line should end at 72 chars...if you have more to type in a line, the next line's 7the char should be a dash(-) to indicate so..

and the compiler's error messages are shit!

now, even with modern languages, people think its hard to code!

Arcane C++ error messages can suck my dick

Dear app developers
The purpose of toasts is to report a few words in response to a single and repeatable action. Don't put long error messages resulting from submitting an 8-page form in a toast.

Error while writing to file: success

I'm trying to deploy an Azure Function via Visual Studio. VS gives me this error:

Publish has encountered an error.
Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details.

A diagnostic log has been written to the following location:
"C:\Users\myusername\AppData\Local\Temp\tmp16F8.tmp"

Let's check the log then!

"Microsoft.WebTools.Shared.Exceptions.WebToolsException: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details. "

Fucking piece of crap

Talking about bad error messages

I missed the regular enrollment period for courses starting in 2 weeks, but I did have late enrollment days, which I remembered.
When wanting to late enroll, I was greeted with th error message in the picture. Bad news first, good news later I guess

As you can imagine, my heart skipped a beat. Nonetheless, it was all good in the end, because I was already enrolled for the compulsory courses I wanted to take

WTF PEOPLE!!
Some people really need to read their error messages.

Just now I got this teammate asking me how he should handle the error git returned. The error message stated: "Please commit your changes or stash them before you merge." He asked me what he should do to fix the error... I was astonished by his stupidity that he did not read the fucking error message.

Almost every fucking time a teammate comes to me with the question how to fix an error, there is a message that says how to fix the error. Why don't they read them?!?! I told you so many times to read your fucking error messages!!!

I'm really glad the project is over in a couple of weeks and I get a new team..

not sure if this totally classifies as a rant, but here goes:

so my Pi is giving a lot of problems. can't install software, keep getting weird error messages. so I try DD a new image onto the card. does not work at all. tried on three different machines :D
next I try run rm -rf /
it's obviously totally fucked. nothing works. pull the plug and plug it in again to see what happens.... it boots up again :D all the commands are back. no files are gone.

and that's when I was like fuck this and I returned the sd card :D

Sometimes I think "I should write a meaningful error message for this exception" and then i remember how useless 99% of the error messages of every compiler / interpreter I've ever had to use and decide "msg ='something went wrong'" is good enough.

Sending webrequest to book car service, but the website isn't telling me if the request went through - just back to the same page with all info filled in. No error messages. Right now they either have 10 requests from me, or none. Stupid fucking site.

What happens when a Linux sysadmin has to work with a Windows machine? Annoyance. Frustration. Irritation. Rage. Maybe all.

Is every piece of administrative software in the Windows environment as unfriendly as this wmic thingmajig I was trying to fiddle with today?

Everything, from its pedanticity on switch order, through very unhelpful error messages, all the way to a very... lacking... help description just turns me off. Ugh. I will "Unexpected switch at this level" you, too, you little piece of ****!

Come on guys, use those JSON schemas properly. The number of times I see people going "err, few strings here, any other properties ok, no properties required, job done." Dahhh, that's pointless. Lock that bloody thing down as much as you possibly can.

I mean, the damn things can be used to fail fast whenever you misspell properties, miss required properties, format dates wrong - heck, even when you want to validate the set format of an array - and then libraries will throw back an error to your client (or logs if you're just on backend) and tell you *exactly what's wrong.* It's immensely powerful, and all you have to do is craft a decent schema to get it for free.

If I see one more person trying to validate their JSON manually in 500 lines of buggy code and throwing ambiguous error messages when it could have been trivially handled by a schema, I'm going to scream.

My Gear S3's charger all of a sudden decided not to stop full charge when the watch was at 100%, so I came home to a watch that was flaming hot and going crazy with error messages that it's overheated, battery going down WHILE charging.

Tried it a few more times, never stops at 100% anymore

Samsung you fucking retards, thanks for trying to burn my house down (again)

the fking piece of technology which is unreal engine... you spend a lot of time on rigging and preparing a beautiful skeleton in blender, you are finally done, and you want to export it as fbx. But nooooo here are like 100 hoops you have to jump through and another more 100 blender settings to set so that the mighty unreal "might" accept your humble offering of an fbx and break it 10 times in the process....
this is rediculous.
The error messages are useless. "mimimi you have multiple roots" "mimimi same named objects". Ya sure, and when I use the older fbx 6.1 library for the export suddently these are fine? hmmmmmmm
<.<'

I was setting up a small home server running CentOS to my closet and was fighting with a USB Wifi adapter that wouldn't stay "awake". Googled the error messages and nothing...

Decided to about it on the CentOS forums and mentioned (MENTIONED, WASNT THE POINT) CWP (CentOS WebPanel) in my question, an admin came, COMMENTED A LINK TO A FORUM POST THAT TOLD "CWP IS NO WAY LINKED TO CENTOS" AND CLOSED THE QUESTION!
FUUUCKKKKK, i wanted to hit something sooo hard. The admin basically turned my point from A to X.

Do you enjoy pain? Love being mistreated while paying $100 a year for it? Welcome to Apple Developer Enrollment!
You'd think for a company that claims to provide "seamless" experiences, their enrollment process would be super straightforward, but no, get ready to waste incredible time with generic error messages.
"Enrollment through the developer app is not possible for this account".
Great! Just great. My peasant app wasn't worthy of being on the almight App Store anyway. Forgive me for trying, my lord.

WTF.

First, they make you prove your existence with endless verifications. Need a D-U-N-S number? Good luck because it's a nightmare. Support? Barely helpful. And if anything goes wrong? Expect weeks of waiting with zero urgency from Apple.

And that $100? You pay it every single year, just to keep your apps measly alive. Meanwhile, Google charges a one-time $25. Fair? Not in Apple land.

And if they randomly decide your app has an issue? Boom, it'll be gone. No warning, no clear answers, just frustration.

So yeah, if you're a masochist who adores pain, jumping through hoops and paying for the privilege, Apple’s got you covered!

PO1: Hey, PO2 just told me that he experiences a lot of crashes in our iOS app!

Me: Whoa! The app hasn’t had any crashes since ages. The testers haven’t reported crashes either. (Me in panic mode). I will ask PO2 about some details about the crashes.

Me to PO2: So, can you please describe me when the crash happens?

PO2: (long story about error messages and UI quirks and how he force quits the app to make them disappear)

Me: OK thanks for that info. Those are definitely valid problems that we have not encountered yet. But none of them are crashes. So are there any other problems that cause crashes?

PO2: Yes and no. (Long story and more problems)

Me: ok we need to investigate that. But are there crashes?

PO2: (Something that doesn’t answer the question)

Me: I need to ask explicitly again: Are there actual crashes where the app closes itself automatically?

PO2: No, that has never happened.

I just found this in my "Religious views" info on FB, thought I would share it even tho it's just a paste from somewhere. Don't slaughter me if this is a reoccuring thing on here😂

THE 0x17'RD PSALM

The Computer is my taskmaster; I need not think.
He maketh me to write flawless reports
He leadeth me with Computer-Aided Instruction
He restoreth my jumbled files
He guideth me through the program with menus.

Yea, though I walk through the valley of
the endless GOTO,
I will fear no error messages;
For thy User's Manual is with me.

Thy disk drive and thy Pac-Man-they comfort me.
Thou displayest a spreadsheet program before me
in the presence of my supervisor.

Thou enableth the printout;
the floor runneth over (with paper).
Surely good jobs and good pay shall follow me
All the days of my life;

And I shall access your CPUs, forever.

Pro tip: make your tool’s error messages very long, so feeding them into ChatGPT is not financially viable. Then, sell support for your tool.

FUCK.
NEXTJS.

...

THIS PIECE OF FUCKING SHIT WORKED 4 DAYS AGO.

I CHANGED ***NOTHING***.

4 DAYS LATER I START THE PROJECT AGAIN AND HALF THE STUFF BREAK. NOTHING FUCKING WORKS!!!!!!!

SOMETIMES IT WORKS SOMETIMES IT BREAKS

MESSAGES GET SENT SUCCESSFULLY 2-3 TIMES IN A ROW AND THEN Random 401 error

Random page glitch flickering when routing to new pages rendering the content blank

Random list map iteration crashes on ui dev side

This is such a fucking SHIT

Now i started my angular and spring boot exact same project that i stopped worjing on since october 2023 AND EVERYTHING WORKS FINE WITHOUT ANY RANDOM ERRORS

RANDOM ERRORS ONLY HAPPEN FOR NEXTJS FUCKSHIT FUCKING FRAMEWORK

FUCKIEST DOGSHIT GORILLACUM MAD FUCKIJNNGG RETARD FRAMEWORK FOR AUTISTICS I WASTED SO MUCH TIME LEARNING THIS PIECE OF FUCKING GARBAGE!!!!!!!!!

I need to hire a fucking personal cryptologist just to help me understand Visual Studio error messages.

An app that translates those dreaded error messages into succinct and human readable English, like: you missed a semi on line 23.

I still don’t understand git completely ,sometimes the error messages are so hard to understand I just make a new repository and push all my new updates there using GitHub desktop.

SO MAD. Hands are shaking after dealing with this awful API for too long. I just sent this to a contact at JP Morgan Chase.

-------------------
Hello [X],
1. I'm having absolutely no luck logging in to this account to check the Order Abstraction service settings. I was able to log in once earlier this morning, but ever since I've received this frustratingly vague "We are currently unable to complete your request" error message (attached). I even switched IP's via a VPN, and was able to get as far as entering the below Identification Code until I got the same message. Has this account been blocked? Password incorrect? What's the issue?

2. I've been researching the Order Abstraction API for hours as well, attempting to defuddle this gem of an API call response:

error=1&message=Authentication+failure....processing+stopped

NOWHERE in the documentation (last updated 14 months ago) is there any reference to this^^ error or any sort of standardized error-handling description whatsoever - unless you count the detailed error codes outlined for the Hosted Payment responses, which this Order Abstraction service completely ignores. Finally, the HTTP response status code from the Abstraction API is "200 OK", signaling that everything is fine and dandy, which is incorrect. The error message indicates there should be a 400-level status code response, such as 401 Unauthorized, 403 Forbidden or at least 400 Bad Request.

Frankly, I am extremely frustrated and tired of working with poorly documented, poorly designed and poorly maintained developer services which fail to follow basic methodology standardized decades ago. Error messages should be clear and descriptive, including HTTP status codes and a parseable response - preferably JSON or XML.
-----

This whole piece of garbage is junk. If you're big enough to own a bank, you're big enough to provide useful error messages to the developers kind enough to attempt to work with you.

The more problems I encounter with Windows the more I have the impression these infested chimps never implemented a real system repair/restoration feature but just faked it with randomized error messages.

Now Windows 10 can't even rollback updates anymore but lands in an infinite boot loop that even a reset to an earlier restoration point won't fix.
And the Windows repair option lists two Windows installations even though there's just one.

Somehow the roles of Linux and Windows have switched nowadays, by now I had to reinstall Win10 5 times on three PCs in the last 12 months.
Windows 8 was shit too but at least it didn't fucking break within a week.

Remove a users virus, save them for a day. Teach a user to Google error messages, save them from a lifetime of viruses.

Fuck azure. Not even 2 hours in and this is the biggest bullshit I've seen. So fucking overcomplicated just to sign in and use the azure portal. Keep getting bombarded with random error messages when i try to create any fucking resource. Some tenant error no idea what that shit is. Annoying as fucjk

What is with IT and their obsession with error messages?

"If there is no error message, I cannot help"

Your not going to get an error message because the problem is VPN is messing up my DNS due to tunneling. There is no error other than me not having Internet if VPN disconnects unless I reboot.

Was recently asked if our team wanted to change from Java to Kotlin so I looked over the feature lists but don't see much that's impressive.

One argument was less boilerplate code but I think they're are libraries like Lomboq that can write that stuff for you.

The other was smart type casting and type inference and to that I'm like this sounds like giving monkeys a hammer.

Our JS codebase looks like shit... And our Java app just crashed in prod.

Getting a ton of text messages this morning and thankfully I'm on vacation still...

The error is not caused by NPE... but how some or logic spammed the db..

A new language isn't going to fix this.... And a team that writes this sort of shit logic clearly shows they are incapable of learning a new one probably...

They are already script kiddies... Don't need them to become babies...

Hiding things I couldn't fix and error messages using CSS.

Who the fuck invented the glorified pile of shit people call laravel? Is this actually used in PROD for anything else than load testing a monitoring server by creating loads of error messages?
OOP exists for a reason, not to create bazillions of classes with static methods.
Dump that shit ffs!

Am I the only one here that needs more time to create user friendly and Idiot-save error Messages than writing the whole validation of stuff?

No error messages? Hmmmmmm.............something is very wrong.

So I got my sister a new PC and being the thrifty (and masochistic) fuck I am, I thought I'd build it myself. I built the PC yesterday (side note: Stick to backplate coolers, Push-Pin is the bane of my existence, patience and fingers) and wanted to install Windows today.
I shit you not, I ran this godforsaken spawn of Satan of 'Windows Media Creator Tool' no less than 5 times with different USB sticks, different Ports, turned off AV and FW and as Administrator but stuff ain't working. After ~30min of downloading Windows each time, it always told me in usual Windows manner "Something went wrong", because who needs decent error messages anyway...

Fuck you Firefox and your shitty debugger.

Why do you try to be so different, to the point where you make the error messages obscure?

Google the error message I get in the Chrome debugger - hundreds of results.

Google the error message I get in the Firefox debugger - I can count the results with my fingers.

Just use the same error messages god damn it.

P.S: Also, why is there no fucking option to open an image in a new tab, like in Chrome?

I am done with .NET and it's bullshit error messages.

"Validation error happened! Please see Entity.Validation.Properties to see what the error is, then consult an oracle, who'll summon a demon who'll answer only three questions . . ."

FUCK OFF and just give me the error. I swear to god exceptions in NET always lead to some stupid fucking scavenger hunt rather than just letting me know what the fuck went wrong. This isn't the first time I've encountered this either, where it tells me there's an error and there's a mountain with a shaman at the top who'll provide me with the details if I can just hire a sherpa who'll help me climb it.

I read the other day here about people not reading the error messages shown by the IDE and thought "there can't be people this dumb..."

Well, today I was helping a friend out with his java project and he was trying to figure out an error for at least 10 min so I told him, read the error message, he goes like nah, that won't help, I kept repeating it till he did it and guess what? The explanation was there and helped him figure out the problem.
His excuse? He didn't have the patience to read the message, it was 2 lines long...

How can you be so stupid to the point where your first thought isn't checking out the damn message the IDE gives you? It's there for a fucking reason.

A QA walks into a bar and ordered two error messages.

For the morning is long and full of error messages...

How can anyone justify the cofefing craploaded bullshitish error messages of bloddy java?
Who, in the name of the flying spaghetti monster came up with that brain damaged bitwaste?
Sorry if i offended brain damaged people with that comparison

Really... "Investigate the reason" and try again. Bruh.

Someone please explain to me how error messages such as
"Something went wrong" or "Critical error" are valid and provide little to no follow up explanation in the GUI, Logs, or client logs.

I get that not all error cases can be displayed on a GUI, but at least have decent error handling. Especially if your $8+ billion company.

The more I surrond stuff in try{...} statements, and handle with geeky error messages that should actually never happen (e.g. "TransactionId 73545 not find for UserId 10. Look for Interaction 212345 at the logs."), the more I think our Customer Support area will someday need a Customer Support Support area.

Another one of those success messages, that looks like an error message. feat. MySQL Workbench

After two weeks of struggling with Docker, I can confidently say, this is the worst shit I've ever worked with.

$ php bin/console make:migration
ERROR: php_network_getaddresses: getaddrinfo failed: Name or service not known

Well let's try again...

$ php bin/console make:migration
ERROR: Connection refused

Different error messages for the same commands?! FUCK YOU!!!

Is part of being intermediate/fluent in a tool, language or framework that you've just unwillingly memorized all the error messages you've come across?

'Hey I got error X' -> Just change Z and C and it will work
'Do you know what this stacktrace is trying to tell me?' -> Yeah you forgot a space
'What does this mean?' -> Just add the host to the hostfile

Not that it immediately makes you an expert ofcourse

So, started working in a nodejs/react personal project with an old friend. I code in linux mint, my pal always at windows 7 never worked in something different from php. From the very beginning I advised him to move to linux

Me: hey man, the backend is running now, pull the changes and `npm start`

Friend: ok so I need to install dependencies right?
Me: yup, easy peasy lemon squeezy

So after a brief(one week period) until my friend could install visual studio to get some deps installed

Friend: hey I ran `npm start`, it got stuck. backend does not start at all, no output messages, no error, no nothing

Me: FFS, that's why I told you from the start, "use any linux distro for this project" :(

Then for a couple of hours(4) trying to install a distro in his 7 years old laptop...

Me: Ok, let's call it a day, 7 tries to install this thing in your old machine is enough. did you not realize your HDD was really busted? in your 7 years with your laptop? this is BS that's why I could not install linux :|

Friend: I didn't, windows never showed me any problem, maybe windows is better than linux in that matter.

Me: GTFO

IT in the social sector. For some, it is absolutely new that reading error messages and trying to follow them actually helps.

Some are absolutely amazed that the error message says exactly what you should do.

I can't count how often I said "read the message" and got an "oh, okay then..." back.

I submit all my code changes to the integration stream. Co worker integrates my code removes all my changes that breaks his hacky crap. Then complains his stuff doesn't work. I ask him why he he did not conform to the requirments says cause this is what worked before. I look at code see he assigns a value in the message to zero. I ask ever so politely why he is changing the incomming messages. He says this is what works. I Then send an email to him telling him this in an error. He reply saying this it what works. At stand up he complains and says no messages are getting through it doesn't work. The team tells him to revert to the original code. (My code) and update his code after two days of emails to bosses and complaining he reports it works with my code after he is done. He is the senior senior chief grand Pooba and makes more money than me.

I love Rust's error messages, but I think they were trying to be a little too smart with the error reporting here and ended up relying too much on properties of the medium.
How the fuck do I tell which is which?

My hypothesis is that because #3 can only be a lower bound based on the phrasing of the sentence, and because #2 is an upper bound, the correct order is 2;4;1;3. But why do I have to do intermediate level English grammar exercises to read my error message?

does a different error message still mean progress when you go from 3 error messages to 173?

Customer complains about an issue after a software update. The head of department himself tested the update and got an error message.

Me looking at the logs. Ok, that's an issue, but based on hardware failure, customer should fix his hardware, no relation to the new software.
But surprisingly close to the software update, which piques my curiosity.

Me looking at older logs ... same issue. EVERY FUCKING DAY. For months. The corresponding error message only appears if a user is logged on, so quite a few people have seen it. Obviously nobody cared. Maybe we just ditch error messages, it'll save lots of work.

I like when devs jokes in their error messages... right? This is a joke...

Atlassian needs improvement!
Screenshot from the Jira "Accessibility" settings page where I hoped to find a dark mode switch.

When I wanted to send them feedback about the settings page, the feedback form failed, cluttering vintage style error messages with poor UX writing all over the page.

> Help us improve!
>
> We’d love to hear more about your experience with the new accessibility settings in Jira. Any thoughts on what you liked and where we could improve are more than welcome.
> Oops! Something went wrong...
>
> There was a problem submitting your feedback, likely due to the configuration of this form. You might want to contact the site owner to let them know about this issue.

P.S. Thinking of accessibility: there is not way to enter an ALT text to image uploads on devrant? seriously?

The superpower to understand all error messages! 🤓

Other build tools:

Here is a plugin, use it . Be done.

Scala Build Tool aka SBT:

Build your own plugin.

Everything is scala...
You can create by the way funny endless loops when using the wrong syntax - yet it might compile successfully. And then when you load the plugin, it works. Till it is evaluated - lazy evaluation for the fun.

Error messages are at best cryptic.

*If* you manage to get a working plugin and *if* it runs...

Surprise. Surprise.

You might need to parse the log output of SBT.

Another funny surprise: Log output isn't configurable. You can configure the log level. That's it.

So after a lot of pain stakingly putting together a fucking shitty plugin, you can now grind the rest of your brain with ...
sed.

Cause yeah. You can now use regex to parse an sbt build log and extract the necessary information.

:)

...

So....

Are we there?

Mwahahahhaa.

Only if you haven't forgotten to either disable colored output for SBT... Or take an extra mile with e.g. less -R.

Otherwise you have ASCII control characters in your file. :-)

After getting that shit to work, you now have finally a parseable build log.

Just took days instead of hours.

But that's SBT. :-)

Fucking hell my insights are late ones...
So I am working with fluid dynamics simulation. I went home fired up the laptop and started the calculations. This is how the events went:

9 PM: starting the calculation
10 PM: checking on the graphs to see whether everything will be alright if I leave it running. Then went to sleep.
2 AM: Waking up in shock, that I forgot to turn on autosave after every time step. Then reassured myself that this is only a test and I won't need the previous results anyway.
5 AM: waking up, everything seems to be fine. I pause the calculation hibernate the laptop and went to work.
6:40 AM on my way to the front door a stray thought struck into my mind... What if it lost contact with the licence server, while entering hibernated state. Bah never mind... It will establish a new connection when I switch it back on.
6.45 AM Switching on the laptop. Two error messages greet me.

1. Lost contact with license server.
2. Abnormal exit.

Looking on the tray the paused simulation is gone. Since I didn't enabled autosave, I have to start it all over again. Well. Lesson learned I guess. Too bad it cost 8 hours of CPU time.

I wanted some ideas on how to word an error message better, so I googled "error message best practices".
80% of the results were about form validation and not actual code breaking errors >:(

On the up-side, I now know that I must not say "No, Bad User!"