From week 5 into my employment he reports me to hr because he was unsatisfied with the quality of my work. Over the next few weeks he would proceed to make my life miserable and systematically use hr to give me a poor performance review eventually firing me for my attitude. It really sucks that I got fired because I really needed liked the job but I guess I can now say I’m a diehard vim user.
This is the key. I don't think he was fired for not using VS Studio. I think he was fired because his quality sucked or he was slow or he had a poor attitude or they had to make extra accommodations to him because he used a non team supported IDE. Or all of the above.
In later comments, he suggested that he had disagreements with his boss about how to do things and suggested that his boss was threatened by him. To me, it sounded like he did not get along with his boss and vim was not the core issue.
He posted it in /r/vim so all he is going to get is echo chamber of sympathy.
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
This. 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.
4 comments
[ 0.28 ms ] story [ 18.1 ms ] threadThis is the key. I don't think he was fired for not using VS Studio. I think he was fired because his quality sucked or he was slow or he had a poor attitude or they had to make extra accommodations to him because he used a non team supported IDE. Or all of the above.
In later comments, he suggested that he had disagreements with his boss about how to do things and suggested that his boss was threatened by him. To me, it sounded like he did not get along with his boss and vim was not the core issue.
He posted it in /r/vim so all he is going to get is echo chamber of sympathy.
Everybody knows that you should have been using Emacs.
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