I don’t get it. This isn’t funny. I wouldn’t approve it in merge request. Most wouldn’t.
Trying to hide problems and incompetence is the joke. A lot of people don’t want problems solved, they just don’t want to see them, and will take the easy route. If you just want that, this is the easy route.
Incompetent? Absolutely, that’s the joke.
I, too, place
2> /dev/nullafter every lineYes, but
2>&1 > /dev/nullis the real hero.
edit: works better when used together with
StackOverflow.comment.enabled = false;Actually fixing warnings is for noobs
if they mattered they’d be errors I’m sure
That’s when you do CTRL+C, CTRL+V
Meanwhile in another universe one of my biggest win was to introduce this line in our PR validation pipeline.
eslint . --max-warnings 0Works so well, and soothes the warning annoyance brain, and keeps warnings from eventually becoming errors.
In a codebase with a lot of warnings is even better for me to add a disable comments for all the existing warning and then not allow any new one in.
And then each time a part of the code needs to be touched the existing warning there should be solved too.
Several times I’ve set the max warnings to whatever the current warning count is, and then decreased that over time.
If it wanted to get my attention it should have been an error
Eh it’s Javascript. Anything goes
this is fucking gold
Yeah, array.length is mutable in javascript. I’m surprised it caught on.
If i can just suppress the warnings which need to be fixed till morning in my buggy code, anything goes!
Warnings? We’ll come back and address those later. Maybe once we’re feature complete. Or maybe shortly after that.
Don’t worry. We’ll totally fix all of them soon. Promise. Hand to God. They definitely will not be here five years from now.
Warnings are for ignorings :3
if (error) { continue; }On Error Resume NextVisual Basic is a beautiful language
On error goto 0Was always syntacticly confusing for me.
try { operation(); } catch { // nice weather, eh? }with contextlib.suppress(BaseException): do_thing()☑️ PR Approved
Thanks. I hate it.
Starting with Java 21 (I think), they’ve introduced ignored variables, so you can now actually do this:
try { operation(); } catch (Exception _) { // nice weather, eh? }Edit: forgot that this is about JS lel
So basically the same as a discard in C#?
Yeah, Python has it as well. I think the only real use of it is code readability since you declare that this variable will never be used.
Same thing right?
If your joking yes, if your not Java and Java Script are seperate things.
His joking?
Actually made this mistake in front of 20 people the other day. Guy at my job mentioned coding in java and I asked if he was doing web dev 🤦
Plenty of java back end web development, so maybe not as embarrassing as you felt?
-ErrorActionPreference SilentlyContinue
–yolo
If I can’t see it, is it really there?
If it works, it works
Sometimes it’s better to hope while closing eyes
This is why:
“It ain’t stupid if it works.”
is fundamentally incorrect.
I would add: until it doesn’t.
