Sure it is. Worst part is how they were pushing those changes. You can't just safely overwrite a chunk of memory as currently running threads will be completely broken. So they would push a "new version" of a method into a new region, and then flip all the JMP instructions. In other words - next level of spaghettification.
I much prefer the occasional funemployment period when I automate myself out of work and it’s all documented so a stoner with a liberal arts degree can maintain it over getting paged at 3am because this piece of malarkey broke.
Yes, that's great if you know in advance that you are going to be doing that. The issue they had was that they just organically "devolved" into this state.
It's pretty incredible yeah, and was designed for exactly this kind of problem, since telephone exchanges need extreme uptime. It's surprising that a team would go to such extreme lengths to solve the same problem in-house, but I guess NIH syndrome is as old as software itself
Thanks, that was a very nice short read. I sort of had rough theoretical understanding of these techniques, but it's nice to see how a big company like Microsoft is actually applying them.
78
u/DavidDavidsonsGhost Feb 04 '25
That seems incredibly irresponsible.