5 ms·
Feels like the author is holding off a lot of information. I once had a colleague who wouldn’t use VS Code when the whole team was using it. Which I didn’t mind
by _thisdot 4y ago
Feels like the author is holding off a lot of information. I once had a colleague who wouldn’t use VS Code when the whole team was using it. Which I didn’t mind because I had a phase with Atom which lasted until GitHub announced they’re sunsetting Atom
But the problem with this guy was that while everyone did a “Format on Save” with VS Code, he’d often submit PRs that failed CI checks for code style. And this happened way too often. Every PR, a reviewer had to comment this
We could’ve solved the problem with precommit hooks. But the fact that this dude asked for reviews on PRs that failed CI checks and couldn’t be merged was the real red flag
- senttoschool 4y agoThis. As far as I know, VS Studio would have even more team specific configurations. The fact that his boss complained about quality, and he complained that his boss was jealous of him suggests that he was fired because he was not worth all the trouble.