this post was submitted on 17 Dec 2023
135 points (97.9% liked)
Technology
59421 readers
3364 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Looks like they need to learn a thing or two about integration tests, redundancy, and fail-overs.
A software update didn't take it down. Negligence did. You should wonder why it doesn't work before you ship to production.
Yep.
Where's the non-prod test environment? For major systems we always have a multi-tier setup, of Test (pretty open, wild-west, but completely isolated and only test data on it), then Non-Prod Test, which looks a lot like production, has production-like test data, with User Acceptance Testing capability, still isolated from both prod and test. (We also have other layers of test too, say for hardware integration to backend, etc).
Also, this example is why I constantly argue against auto updates for anything, even my phone apps.
Without validation testing, you don't know shit won't work and then disrupt your work flow. My phone is a tool that I rely on to work a certain way.
Integration testing is great for release validation.
But there's also development work that should have been done on the release process itself, like support for progressive rollouts and easy rollbacks.
Progressive rollout? Nah, these people are acting like it's 1992 and just cowboy that shit up!