Among other things I've done in this life are building computer boxes, troubleshooting hardware and software problems and teaching a slew of apps, from early days (Anyone remember stuff like Harvard Graphics?)
One of the things I learned early and adopted fervently as Windows developed and grew: Wait a week, maybe 2, before applying a Windows software upgrade or fix. By then, if there's going to be trouble, it will have happened and hopefully be pulled or resolved.
@Pat_Walrond
In IT, early adoption is always high risk. Unless it's critical for continued operations, patches can wait just a little to be confirmed.
@ArcturusSaDiablo This one creates a BSOD.. There was one a few years back that totally fux0red systems. Only way out was reformatting or rebooting into a backup. That was chilling. I didn't get caught by it, but it did drive a little "software fixing" my way.
@Pat_Walrond @ArcturusSaDiablo I use to be part of the IT research community and attended LISA (Usenix) conferences for 10+ years. I still remember this paper:
@hallmarc I haven't finished reading the whole paper yet, but 1) I love the parody on "to be or not to be", and 2) I'm grateful I only had to apply patches to individual systems. The number of things to take into consideration for a network is disconcerting, to say the least. @ArcturusSaDiablo