3 ms·
The easy answer to this is "warnings should be warnings" but the hard question is "how do we get people to stop treating them as errors?"
by saagarjha 6y ago
The easy answer to this is "warnings should be warnings" but the hard question is "how do we get people to stop treating them as errors?"
- eyelidlessness 6y agoThe easy answer is to stop treating errors as warnings! I’m working on a project where for the first time in my career I’ve made my environment/workflow/tooling less shouty about problems. I’m writing for my blog, so I installed a spell check extension. But its dictionary stinks. So I just turn off its warnings before a final post pass. Most of the time when I see yellow in my editor it’s stuff I would expect to be red. Even from my primary language (TypeScript) which officially doesn’t even have warnings. More things should be errors and treated as such! And more things that legitimately qualify as warnings should error in final checks to ensure they were addressed somehow, even with just an explicit dismissal.