Given that many companies do a terrible job of maintaining and refreshing their code base... and that even their production code bases are in perpetual beta... and even before AI they were doing things like discarding their legacy codebase and attempting to rewrite things from scratch (remember Sonos?)... an argument can be made that if you're going to churn out a shitty replacement, but can do it faster, that will still save you money.
https://arstechnica.com/gadget...
"In May, Sonos updated its mobile appâ"to the dismay of many users. With missing features and bugs, customers complained about a loss of functionality and hardware not working the way it should. As Sonos deals with the expensive repercussions, a report from Bloomberg today highlights how Sonos allowed the release of an update so buggy and incomplete as to overturn its goodwill with long-standing customers.
Illustrating how poorly this app update has gone, last month, Sonos CEO Patrick Spence said the company would spend $20 million to $30 million in the short term to get the app where it needs to be (which is, basically, functioning as well as the predecessor) and rebuild customer and partner trust. Sonos also expects to miss its annual revenue target by $200 million. This is partially due to its delay of two hardware releases to focus on the app. Bloomberg noted that âoeSonos shares are down 25% this year.â Annual bonuses and merit-based raises have also reportedly been canceled."
I have no idea how much money Sonos spent before committing to spending an additional 30M, but taking a 200M revenue hit because they couldn't get enough feature parity before shutting off the old servers and disabling the old app seems like a pretty big stick.
"One reason for the appâ(TM)s failure is the outdated code and infrastructure that the prior app was running on. Anonymous employees Bloomberg spoke with claimed that the Sonos appâ(TM)s technical debt had been building up for 20 years before the update.
By the time Sonos decided to update the app in mid-2022, it was dealing with software based on virtually obsolete infrastructure and code languages. As such, the app update âoewas less about introducing new functionality than sorting out the existing mess,â Bloomberg reported.
After decades of the appâ(TM)s inner workings growing stale, the impending release of Sonosâ(TM) long anticipated Ace wireless headphones, which came out in June, made the need for a new app both urgent and necessary. This is because the headphones were made to be on-the-go, differing from Sonosâ(TM) other products, mainly speakers and soundbars relying on home Wi-Fi. This seems to align with comments that Spence made to investors in August. He said that the app update was âoea redesign of the entire systemâ"not only the app but also the player side of our system, as well as our cloud infrastructureâ"and this was a complex undertaking.â"
This sounds like they didn't want to support parallel systems and were hoping that they could migrate everything over before the cutover... and when they failed to make that deadline, they decided (and by they, I mean management, because who else in their right minds would disable functionality to happy customers) to just deep-six the legacy environment without warning instead of transitioning people to a "legacy retention program" with a definite cut-off date in the future.
I guess the moral of the story is, if you have shitty management, having them make fucked up decisions that result in near-immediate feedback is better than having them percolate for a year and then result in no-bonuses / layoffs.