 |
Igor Delovski Board My Own Personal Slashdot!
|
| Dev Links |
| Author |
Message |
Ike Kapetan
Joined: 17 Jun 2006 Posts: 3379 Location: Europe
|
|
| Back to top |
|
 |
Ike Kapetan
Joined: 17 Jun 2006 Posts: 3379 Location: Europe
|
Posted: Sun Oct 19, 2025 10:43 pm Post subject: |
|
|
techtrenches - The Great Software Quality Collapse: How We Normalized Catastrophe
The Great Software Quality Collapse: How We Normalized Catastrophe
DENIS STETSKOV
SEP 19, 2025
"The Apple Calculator leaked 32GB of RAM.
Not used. Not allocated. Leaked. A basic calculator app is hemorrhaging
more memory than most computers had a decade ago.
Twenty years ago, this would have triggered emergency patches and post-
mortems. Today, it's just another bug report in the queue.
We've normalized software catastrophes to the point where a Calculator
leaking 32GB of RAM barely makes the news. This isn't about AI. The quality
crisis started years before ChatGPT existed. AI just weaponized existing
incompetence.
The Numbers Nobody Wants to Discuss
I've been tracking software quality metrics for three years. The degradation
isn't gradual--it's exponential.
Memory consumption has lost all meaning:
VS Code: 96GB memory leaks through SSH connections
Microsoft Teams: 100% CPU usage on 32GB machines
Chrome: 16GB consumption for 50 tabs is now "normal"
Discord: 32GB RAM usage within 60 seconds of screen sharing
Spotify: 79GB memory consumption on macOS
These aren't feature requirements. They're memory leaks that nobody bothered to fix.
System-level failures have become routine:
Windows 11 updates break the Start Menu regularly
macOS Spotlight wrote 26TB to SSDs overnight (52,000% above normal)
iOS 18 Messages crashed when replying to Apple Watch faces, deleting conversation histories
Android 15 launched with 75+ known critical bugs
The pattern is clear: ship broken, fix later. Sometimes.
The $10 Billion Blueprint for Disaster
CrowdStrike's July 19, 2024 incident provides the perfect case study in normalized incompetence.
A single configuration file missing one array bounds check crashed 8.5
million Windows computers globally. Emergency services failed. Airlines
grounded flights. Hospitals canceled surgeries.
Total economic damage: $10 billion minimum.
The root cause? They expected 21 fields but received 20.
One. Missing. Field.
This wasn't sophisticated. This was Computer Science 101 error handling
that nobody implemented. And it passed through their entire deployment
pipeline." |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|