It's really easy to be the IT guy that looks at a few commits then harshly judges all the developers. It's a little less easy to be the guy that is actually writing code. I used to be the IT guy doing that...not anymore..now that I'm also the guy writing much of it.
Same excuses, third decade -- of watching the same bugs happen over and over. Color me unimpressed with them at this point.
Nothing personal, everyone does their best and the industry isn't really getting any smarter.
Not sure it ever will. I'm not saying I have any answers, but the industry has its head in the sand pretending it has control of the complexity it creates.
See the CVE numbers for 2015? Not pretty.
Considering the info in the Win10 thread, it doesn't help much when even OS level code is malicious at worst and questionably immoral at best, underneath it all.
At least these guys making this thing aren't doing that.
And like I've said before... They pay me really well to clean up the messes. Still want that "Internet Janitor" business card...
We had a vendor shove a $16K software upgrade down our throats with the threat of non-support in Q4. It was installed and running a whopping 6 hours before it brought that portion of the business to a complete stop, and is now a $16K paperweight in the server room, and the cables were plugged back into the old one that works.
The vendor says they'll "try" to schedule us into their "training schedule" sometime in February but no promises. LOL.
I bet they practice Agile development. Hahaha.
Except of course, they forgot sometime in the last five years to bother to ask us how we use our $2M printer that the software runs... and didn't make sure the new UI did what the old one did... ROFLMAO.
Not sure where this industry is headed, but it ain't toward doing it better...
The nice part is, job security is great as long as you know how to plan how to roll back to what worked.