- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
You must log in or register to comment.
I, too, place
2> /dev/nullafter every lineif (error) { continue; }On Error Resume NextVisual Basic is a beautiful language
I legitimately use this line in one of my scripts because range.find returns an error of the value is not found. The use case is taking a 2d matrix saved as an array, with data collected from multiple excel tabs and rearranging it for a CSV upload into Salesforce. The initial array contains values that the rest of the data does not have, so when I search for a non existent value, I can skip the error.
Of course vba COULD just implement try/catch statements and that’d be so much cleaner, but alas.
If it wanted to get my attention it should have been an error
Eh it’s Javascript. Anything goes
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!
If I can’t see it, is it really there?
If it works, it works
This is why:
“It ain’t stupid if it works.”
is fundamentally incorrect.
Sometimes it’s better to hope while closing eyes
Warnings are for ignorings :3
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.
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.
-ErrorActionPreference SilentlyContinue
–yolo
