4 ms·
If we have a test or a linter that prevents a problem, that runs in a couple of milliseconds, and you didn't run it because you are too cool to run it, then we
by 29athrowaway 2y ago
If we have a test or a linter that prevents a problem, that runs in a couple of milliseconds, and you didn't run it because you are too cool to run it, then we are no longer talking about subjective preferences about tools. We are talking about responsibility.
If your code caused data loss on production because you are LARPing about being a hotshot instead of adopting the processes that keep the code running I don't care how fast your editor is.
- sodapopcan 2y agoLol, you're exactly who I'm complaining about. I do agree with you: I also dislike people who don't learn their tools and don't do the things you're talking about. But just because you're using an IDE doesn't mean you're going to use all of its features. Conversely, if you're going to use a text editor, you absolutely have to ensure you have that stuff.
- 12345hn6789 2y agoDoes your team have required code reviews? This might help reduce production incidents - sent from my terminal
- 29athrowaway 2y agoChecks running on continuous integration is the mitigation for not having used a linter during development in this case. The linter feedback would take longer to get back to the developer though, increasing the "cost of change".
- xigoi 2y agoWhat does the choice of editor have to do with whether you run tests?