Release with bugs
Filed under: Software | No Comments »If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!
Bugs are inevitable.
You can have a QA team and rely on them, to find all the bugs – but there are going to be bugs in there, QA or not.
I think what’s way more valuable is having a lean enough team to respond to bugs quickly and having code reviews to prevent seriously malicious code to get in (i.e. stuff that’s really going to mess up your database).
I am, however, curious about the recent WordPress.com issue that led to an hour or so downtime of a lot of famous blogs, including you-know-who famous tech blogger (left out so they don’t get more press). I’m just wondering what sort of code caused the messing up of the config files and how that got through their automated testing.
Related posts:
Leave a Reply