Hi all.
Just something that I've been thinking of in recent days.
I'm not a developer and really know nothing about software development. From having been an Insider testing preview builds, what I have understood in simplistic terms is that adding a new feature, or fixing one bug can cause other things that had been previously working to 'break'.
A lot of these bugs will be noticeable.
From time to time security updates are released to fix things that the vast majority of us never knew had been an issue. These security updates are therefore for more 'behind the scenes' things. My question is, if these are not noticeable from the outset how can we be sure that a fix for a security issue has not been subsequently 'broken' by a newer update?
(I'm talking in general, not just Microsoft. But when Google and Apple release updates too how do we know that a fix for a security issue has not been subsequently broken by a newer update?)
Just something that I've been thinking of in recent days.
I'm not a developer and really know nothing about software development. From having been an Insider testing preview builds, what I have understood in simplistic terms is that adding a new feature, or fixing one bug can cause other things that had been previously working to 'break'.
A lot of these bugs will be noticeable.
From time to time security updates are released to fix things that the vast majority of us never knew had been an issue. These security updates are therefore for more 'behind the scenes' things. My question is, if these are not noticeable from the outset how can we be sure that a fix for a security issue has not been subsequently 'broken' by a newer update?
(I'm talking in general, not just Microsoft. But when Google and Apple release updates too how do we know that a fix for a security issue has not been subsequently broken by a newer update?)
Facebook
Twitter
Instagram