| Respectfully - You are working for one of the largest companies on the planet. You push code that gets used by millions of people. How on earth are you not thoroughly testing your changes??? How can something like this slip into a real build? Like, this is egregious. I work somewhere that makes software for a lot of users (although not as many as Microsoft!). We also need to ship quickly. But we work on a 45-day cycle, with 15 of those days being dedicated to ensuring we didn't add any awful bugs (and fixing them ASAP before it goes to users - or reverting the change until it is ready). I would expect Microsoft to have AT LEAST that amount of care. We can't trust that you are shipping software that even works anymore! What other changes are going in that are broken in more subtle ways? It used to be that VS Code was rock solid, and any issues were likely third-party extensions - but now it's a crapshoot, and I can't be sure if crashes etc. are the fault of extensions or Microsoft themselves! The VS Code team needs to use this mistake as motivation to lead the charge on making a quality editor. Not an editor that gets half-baked, untested changes pushed weekly. An editor that is dogfooded and where a mistake like this going to prod is unacceptable. Because if you don't, people won't trust your editor anymore. Just like people have stopped trusting your OS, and now users are fleeing it in such numbers that the Windows team has recognized they have a problem and are changing course. That WILL happen to VS Code and GitHub soon unless you actually start owning mistakes internally and fixing them before users find them. |