4 ms·
> No code reviews, security review, integration testing, quality assurance testing, compatibility testing, or validation. If this was a small startup, I can ab
by vorpalhex 9y ago
> No code reviews, security review, integration testing, quality assurance testing, compatibility testing, or validation.
If this was a small startup, I can absolutely see those being hurdles. This is Microsoft on a product they've had for 20+ years that is a major part of their platform - those things should be mostly automated and well oiled machines.
A mature enterprise level company has no excuses for "QA is hard!" or "We can't validate patches!" for a product they sell. I don't expect them to get this out in ten minutes, but they should be able to manage a patch in 24 - 72 hours for a fairly critical and relatively easily solved security bug.
- Quarrelsome 9y agoI'm guessing if they fix this bug the simple way they break the entire product and the proper way is many months of work (entire eco-system restructure).
- BoorishBears 9y agoIronically I would comment exactly what you did with, but the roles reversed: “If this was a small startup I couldn’t see those being hurdles but at a behemoth like MS with an almost 2 decade old product I can.”
- latencyloser 9y agoAs a former Microsoft employee, my experience was that the longer a product was around, the harder it was to figure out who understood any part of it well enough to change something. I would guess I averaged about 10 lines a month on my project that had been around for decades. Making even slight tweaks required dozens of meetings, design discussions, functional and performance testing, etc. etc. It took an eternity.
- patcheudor 9y agoMicrosoft is still actively patching Skype. Here's an example of them patching what sounds like a similar DLL flaw just last year: https://www.cvedetails.com/cve/CVE-2017-6517/ https://www.cvedetails.com/cve/CVE-2017-6517/
- user5994461 9y agoAnd don't forget that the product work as expected in most cases and many changes are not justified. The bike shed won't get painted to a new color just because a the new middle manager asked for it.
- pizza234 9y ago> 24 - 72 hours for a fairly critical and relatively easily solved security bug Let's see. How many microsoft employees would it take to change a lightbulb? ;-) https://blogs.msdn.microsoft.com/ericlippert/2003/10/28/how-many-microsoft-employees-does-it-take-to-change-a-lightbulb https://blogs.msdn.microsoft.com/ericlippert/2003/10/28/how-... Highlight: > That initial five minutes of dev time translates into many person-weeks of work and enormous costs This is just to add an interesting article on top of the sibling comment from the MS employee; nothing's easy in the engineering of a large product.
- cptskippy 9y agoI feel like you've got those reversed. In small startup the bug fix would be deployed to production before it's committed to source control. In a large enterprise the process isn't too hard, it's just complicated. I was neither justifying or admonishing MS for this issue, I was just responding to a gross trivialization of the process that I found offensive.