In addition to this, once you’ve added an ESLint plugin, you’ve not only prevented the problem from entering that particular area of your codebase, you’ve also prevented it from showing up anywhere else as well. That’s a real win! (And that’s a benefit you do not have with testing).
And whatever you do, be good to others online. They’re more than just the pixels on your screen. On the other side of that pixel is a real human being, with all manner of hopes and flaws. Remember that the next time you feel the urge to tear into them after reading a tweet you don’t agree with.
I realized that what I was addicted to was inflating my own ego, tiny bits at a time, by feeding the idea that my opinions — on anything — were informed, intelligent, reasoned, and useful, and that any conversation that I read could benefit from me poking my head in.
…to make sure it doesn’t come back. Instead of starting out with test driven development to do that, first ask yourself: “Could this bug have been prevented using a type system (like Flow)?” If not, then ask “Could this bug have been prevented using a custom ESLint plugin?” The nice thing about these two tools is that you can run them on your code statically.