3 ms·
I badly want an intimate look under the sheets at how the vscode team does their development cycle. These updates are consistent and generally very high quality
by Waterluvian 8y ago
I badly want an intimate look under the sheets at how the vscode team does their development cycle. These updates are consistent and generally very high quality, and focused on a handful of features. I want to replicate it for my team. But I don't want buzzwords like "agile", I want to cut through all that and see the actual actions, behaviour, and tools that result in this kind of success.
- tracker1 8y agoIt would be interesting to see a case study of this, as well as how the interaction with the public community, and collaborators has worked. I do know that some pieces do burrow from the larger community, and it's interesting even what you can glean from GitHub alone.
- shearnie 8y agoThey seem to coincide closely with the release cycles of Visual Studio proper. I wonder if both teams (or the same team) are within similar disciplines.
- Tyriar 8y agoHi, I'm part of the VS Code team. We have a page on our wiki that describes in a fair amount of detail how we structure iterations: https://github.com/Microsoft/vscode/wiki/Development-Process https://github.com/Microsoft/vscode/wiki/Development-Process
- Waterluvian 8y agoThis is phenomenal. Thanks for sharing the link.
- jeromebaek 8y agoI work at Microsoft. Generally, here, we have a relaxed philosophy towards approaching things. No pressure cooker environment. Don't feel like going to work? Stay at home. Because it's not shoved down your throat, you develop a particular affection towards your work, and when it gets to crunch time you put your head down and work because you actually want to. I can't speak for every team, but that's the general state of affairs.
- deleted 8y ago[deleted]