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

And experienced ones, too.

Well with C++, I could even understand that because a missing semicolon in a template gives you error messages that easily dwarf "War and Peace" LOL!

I mean there are a lot of scary warnings when you update npm packages or load a website in the console but apparently they're not that grave. So how do you detect the real bad one when you lack the knowlede which ones are bad and which one not so much?

@heyheni when it is keeping your program from running? (C code)

@Fast-Nop yeah they seriously need something better than templates

@heyheni you read warnings when error messages don’t make sense(kinda going fishing) also you read ALL errors not just grave ones lol

Most people don't read anything, ever.

Your beginners read?! You're lucky.

Its 50/50, half of them dont red them and the other half dont understand them.

"why does it say error on line 69 while I forgot a semicolon on line 68?"

Send the errors to the DBAs... they'll figure it out...

Try:
Except err:
Fuck it.. continue.

Wtf why can't devs write error messages that actually make sense to other people...
It's not hard people, defensive programming, check inputs and throw descriptive errors early on

@anolis talking about C code, if you don't know you have to check for errors then you're fucked

I'm not gonna lie I tend to do that :-)

I guess it really depends on what error you're given to work from.

A few days ago Spark told me that executors were dying because of a heartbeat timeout meaning the worker nodes couldn't communicate with the master anymore.

OK. Thats fine. Research why that might happen and increase network timeout but the same happens, just takes longer.

Heartbeat errors apparently hide out of memory errors. Then I find out ubuntu is killing the java process because its out of memory. Not just the single executor that's out of memory.

OK. Thats fine. Increase from 3 to 10 worker nodes and triple the memory of each. Nope. Still runs out of memory. Just takes 12 hours and not 30 mins to fail. The more resources I throw at it the worse it gets

Turns out the input data that we get from someone else had a lot of duplicates.

From a networking error to data duplication error is not clear at all.

Well I have met some experienced ones too... (we were supposed to cooperate developing some angular app)
him> hey, nothing works, the page does nothing.
me> does it throw any js error? If so. What does it say?
him>dunno, some weird shit appeared in the developer console

(he was using an undeclared variable... And was unable to understand the error message)