5 ms·
I would tell a slightly different version of this story, focusing in on "rollout-based quality assurance". I would say that effortless, automatic updates are t
by brundolf 6y ago
I would tell a slightly different version of this story, focusing in on "rollout-based quality assurance".
I would say that effortless, automatic updates are to blame.
When you can always just push an update, the impact of a given bug goes way down. It's no longer mission-critical to exterminate flaws before shipping; a totally broken feature becomes a mere annoyance. So project prioritization shifts from polishing an artifact to outweighing the (presumed inevitable) constant stream of little annoyances with fixes and features. I think the shift towards automated testing is just a symptom; an attempt to bridge the gap in this brave new world.
For a clear-cut example of this phenomenon, look to the video game industry. Until around 2007, games received no updates. Ever. Once a game shipped, it was shipped. There wasn't even a mechanism for installing an update from physical media.
Right around that time, "glitches" went from very rare unicorns that people would spend lots of time actually seeking out, to nearly everyday occurrences. As long as it doesn't corrupt someone's save file, they mostly laugh it off and upload a clip to YouTube to show their friends. This is just how things are now.
(Edit: I should have scoped this to "console games")
- derefr 6y ago> Until around 2007, games received no updates. Ever. Once a game shipped, it was shipped. There wasn't even a mechanism for installing an update from physical media. Sure, but they still (sometimes) released (a few) extra revisions of a game. They were just targeted at people who bought physical copies after the revision date, rather than at existing customers. Or said updates came on the 1.0 version of the game as shipped in markets that got the game later than others. (Just imagine — per-market release versioning. Every market effectively got its own fork of the codebase!) Or said updates came in the form of a re-release port. There are patches made to the emulated downloadable app-store re-releases of some games, that never made it into any physical edition of the game. Also, before home consoles, arcade game machines did receive bug-fix updates regularly. Arcade machines were essentially provided “as a service” from their manufacturers, with support contracts et al. Sort of like vending machines are today. If you reported a bug, they’d fix it and send you a new EEPROM chip to swap out in your cabinet. If there was a critical bug that affected all units, they’d send techs out to everybody’s machines to swap out the ROM for the newest revision. (For this reason, it’s actually kind of hard to do art-conservation / archiving of arcade games. The cabinets almost never have fully “original-release” components inside.)
- brundolf 6y agoI'm sure this happened occasionally, but it wasn't advertised. Nobody was buying a new copy to get an update. Reviewers weren't revising their reviews in accordance (something which does actually happen now). It was still absolutely mission-critical to get things as polished as possible the first time around.
- OminousWeapons 6y agoI agree that games used to have far fewer bugs when shipped, but it's not true that games never received updates back in the day. I distinctly remember queuing on file sharing sites as a kid in the early 2000s to download half-life updates and updates for other games.
- brundolf 6y agoI suppose my statements above should be mostly limited to games on consoles, not PC. That's what I had in mind.
- IggleSniggle 6y agoI remember when DLC used to be called “a patch” and it was both bug fixes and also huge amounts of new content. I wish I could remember what games this pertained to.
- ryandrake 6y agoI think you've both got a piece of it. I've programmed PC software, embedded software, and mobile software, and my gut feeling (without data) is that the shipped software quality is inversely proportional to the update frequency and ease of updates. Had nothing to do with how smart or skilled the developers and testers were. Had nothing to do with management's priorities. Update frequency and ease changed immensely once we could feasibly deliver patches over the Internet. Before easy updates, you'd actually quality check every corner of the application, you'd actually fix those P2s and P3s. You'd do exploratory testing off the test plan rails to find things. There was even a concept of "done" in software, as in, you eventually stop constantly jamming features in and tweaking the UI in maddening ways. Now, it's just "LOL just ship it, users will just deal with it until the next release!" Now, it's "Do experiments on N% in prod and use end users for A/B testing. If something's broken we'll update!" In several industries, it's actually totally expected that v1.0 of the application simply won't work at all. It's more important for these companies to ship non-working software than to miss the deadline and ship something that works! Because who cares? Users will bear the cost and update.
- foobiekr 6y agoI have witnessed this first hand comparing two systems. One system has no patching, and updates incur some non-trivial amount of effort on the part of the installer. Releases are a few times a year, at most. The other system has patching, updates are lighter weight, and as a result, the system has THOUSANDS of patches released over the last decade, north of 2 per work day. Guess which system is higher quality? The former. Much, much higher quality.
- malaya_zemlya 6y agoabsolutely this. Back in the early 2000s quality assurance was insane. A release is was working on (aaa title from a major studio) was blocked because players' eyes were rendered incorrectly and you had to really zoom in to even see the glitch. And of course you had to find and fix all bugs before october, or else you won't be able to hit Christmas sales. Once internet updates became the norm, it all became pretty much like the rest of software industry. (At least game companies still have QA departments, a lot of mainstream web companies have dispensed with those as well.)
- sumtechguy 6y agoOr as I tell my wife. I am playing my favorite game 'updating playstation'. I turn the thing on so rarely by the time I usually do turn it on there is 1-2GB of updates waiting. Glad I have a semi decent internet connection these days...
- ars 6y ago> Until around 2007, games received no updates. Warcraft II, from 1995 received multiple patches. So did many other games from that era. Do you perhaps mean console games when you say "games"?