Another patching debacle — how we got here

Topic

New Reply

WOODY’S WINDOWS WATCH By Woody Leonhard Frantic moves to fix this month’s Windows-update bugs highlight the dark underbelly of Microsoft’s patching st
[See the full post at: Another patching debacle — how we got here]

2 users thanked author for this post.

geekdom, abbodi86

Reply | Quote

Replies

There are two ways to program and maintain code.  The first, which admittedly takes extra skill, time, and money, is the approach an organization like NASA uses.  It assumes the code is for mission critical components and MUST operate correctly and reliably right from the start.  It also assumes that code changes will be very difficult or impossible to execute, so complete testing for both correct operation and to come as close as possible to eliminating all bugs is a critical phase of development.  As we’ve seen, even with this painstaking approach, mistakes still get made.

And then we have the new normal, ushered in by using a very under-skilled, supposedly low cost (not if the complete ROI calculation is done) workforce of outsourced coders.  This method is basically one that focuses on delivering code of dubious quality as quickly as possible with minimal testing.  It is assumed that any errors will be caught once the code is being actively used, and there is little concern about the consequences of applications crashing.

The second process is also fouled by the mistaken concept that the coders don’t actually have to know what they are trying to code.  They simply have to “code to spec”.  And having the coder themselves do the testing and QC creates added issues.

It is no wonder that Windows is broken beyond repair.  Worse yet, the chance of the Microsoft of today reliably coding a new and improved version of Windows is likely zero.  The company does not have the workflow model, and any “talent” that could have executed this is long gone.

I dare say that most of the amazing software we’ve seen over the years have come from individuals or small teams of highly skilled and focused programmers.

1 user thanked author for this post.

EstherD

Reply | Quote

I disabled remote services on my personal PC years ago.  Didn’t take a rocket scientist to figure out that this would be a great way to exploit peoples computers.   Call me arrogant, but, if I cannot fix my own PC then it’s not fixable.    lolol

I do understand that your average end user has to sometimes get external help though.    🙂

Reply | Quote

I think a more appropriate description would involve Asian Carp not salmon …

https://www.youtube.com/watch?v=flrkCjiDURA

Byte me!

1 user thanked author for this post.

woody

Reply | Quote

I fully agree that better testing at Microsoft would go a long way toward fixing the problem.  Speaking as a former IT Quality professional, and having worked in the past with Microsoft’s QA teams, I find the degradation of their efforts completely embarrassing to the quality profession.

Of course, another thing that would help is if they’d quit adding “features” to Windows that have nothing to do with an operating system and stop trying to mimic Apple.  Give us a kernel, a few basic interface-type items (the CMD window, Notepad, a browser if they must — too bad it’ll be Edge) for the benefit of those who are not computer experts, or offer two versions of Windows — one as I’m requesting and one for those who need everything integrated.  I shudder to think at how much memory is being used up by things I have no use for and can’t get rid of (or can’t find enough information about to feel safe getting rid of).  Would have swithced to Linux long ago if I didn’t have a couple work-critical (as in “they ARE the business”) programs that need Windows.

1 user thanked author for this post.

AlexEiffel

Reply | Quote