Sonos laying off 100 people amid expensive app problems

Post content hidden for low score. Show…

msawzall

Ars Praefectus
5,532
Subscriptor++
Funny how layoffs never seem to affect the management that made the monumental fuckups to begin with.

100% guaran-fucking-teed that many who were laid off knew the new app was shit, said so, and were ignored.
General rule for all companies: When something succeeds, management wins. When something fails, the working class loses.
 
Upvote
266 (267 / -1)

Sajuuk

Ars Tribunus Angusticlavius
9,427
This most recent layoff wave comes as Sonos is expected to spend tens of millions of dollars to address the fallout from its updated app. Released in May, the update removed various functions, including the ability to use sleep timers and access local music libraries and accessibility features.
Multiple somebodies at the top of the company signed off on pushing these changes. They won't be fired, of course, but they signed off on it.
 
Upvote
129 (130 / -1)

50me12

Ars Tribunus Angusticlavius
7,064
Funny how layoffs never seem to affect the management that made the monumental fuckups to begin with.

100% guaran-fucking-teed that many who were laid off knew the new app was shit, said so, and were ignored.
I bet almost every engineer knew this "new app architecture" was garbage too.
 
Upvote
107 (109 / -2)
Post content hidden for low score. Show…

ip_what

Ars Tribunus Angusticlavius
6,135
Ah the classic rewrite trap that any seasoned engineer will tell you to stay away from.

You should never rewrite the existing app. You replace parts of it at a time with testing to ensure you're not mucking things up

There’s got to be balance here, lest you end up with Delta Airlines technology stack.
 
Upvote
131 (133 / -2)

floyd42

Ars Scholae Palatinae
943
Subscriptor++
Does that include every manager and executive that signed off on it?

I'm sure the blame and penalty hasn't been completely passed onto the working class employees.
This reminds me of where I work as a "manager" but I'm really a web dev.

We had a license on our cms which was coming due for something like a million dollars because of bot activity thanks to my old, short sighted manager. I worked like a dog for 4 months to get everything migrated over and working with a new system and when it was all done on time my reports joked that they hoped some of the saved money would be coming to us. I told them no, this just meant that no one got fired because that would have definitely happened to get the budget more level.

So yeah, it's usually the people least responsible that have to suffer the consequences. I doubt it's ever been different than that and it sucks which is why I worked so hard.
 
Upvote
109 (111 / -2)

deltaproximus

Ars Scholae Palatinae
720
Subscriptor++
As someone with Sonos throughout their entire house (9 speakers and a sub). I wasn't even aware there was a problem and aside from setting up my system or adding speakers...I've never opened up the Sonos app.

I got a new phone 9 months ago and I realized I never even installed the sonos app. What are people using this for?
Sounds like they're not using the new app for much, because it's incapable, but FTA people used the old app for
the ability to use sleep timers and access local music libraries and accessibility features
 
Upvote
28 (28 / 0)

jdale

Ars Legatus Legionis
16,774
Subscriptor
As someone with Sonos throughout their entire house (9 speakers and a sub). I wasn't even aware there was a problem and aside from setting up my system or adding speakers...I've never opened up the Sonos app.

I got a new phone 9 months ago and I realized I never even installed the sonos app. What are people using this for?
Playing music? Controlling music when I'm not at my computer? What do you use for that?
 
Upvote
50 (53 / -3)
As someone with Sonos throughout their entire house (9 speakers and a sub). I wasn't even aware there was a problem and aside from setting up my system or adding speakers...I've never opened up the Sonos app.

I got a new phone 9 months ago and I realized I never even installed the sonos app. What are people using this for?
Playing music from my phone. Playing music from my music server.
 
Upvote
44 (45 / -1)

2TurnersNotEnough

Wise, Aged Ars Veteran
183
Subscriptor++
Yeap, that's why you rewrite different slices with test harness.

With some of these apps, I doubt they have more tests than some QA testers
Haven’t you heard? QA is a cost center. So you fire them all, and make the devs responsible for testing their own code with test harnesses that will have 100% coverage. Easy-peazy.

What could go wrong?
 
Upvote
118 (118 / 0)

iindigo

Wise, Aged Ars Veteran
136
Subscriptor++
I would be very interested to hear from someone on the inside exactly what happened here. Was the new app contracted out to the lowest bidder? Was it a matter of Sonos not wanting to pay the wages demanded by more capable developers? Is it a case of the cart pulling the horse, with designers and product managers having disproportionally more say in the product than the engineers? Perhaps marketing wanted the ability to inject their own changes without interacting with engineering which made for an unsustainable architecture? Some combo of all the above?

Lots of things that could've gone wrong here.


Ah the classic rewrite trap that any seasoned engineer will tell you to stay away from.

You should never rewrite the existing app. You replace parts of it at a time with testing to ensure you're not mucking things up

While this isn't a bad rule of thumb, rewrites can be pulled off with exceptionally capable teams and leadership that understand the value of everything the original was capable of and know to factor all of that into designs, requirements, and estimates for the replacement. Where things go awry is when the replacement isn't intended to be comprehensive or is based on a shallow grasp of the original. Extensive testing with real-world users helps a lot here too.

That's expensive though, and so is almost never what happens. It's way cheaper and easier to have the designers spin up a good looking mockup and build off of that.
 
Upvote
52 (54 / -2)
fuck spence.
LOL, gee some really sensitive people downvoted you...too sensitive to be on the internet I would say. But yeah he should be the first to go at this point. He has been in charge during all the many issues with Sonos and people laid off. Besides it flat out not working the new UI is terrible too and I didn't really have complaints about the last UI when so many others did.
 
Upvote
-7 (23 / -30)
Post content hidden for low score. Show…
I would be very interested to hear from someone on the inside exactly what happened here. Was the new app contracted out to the lowest bidder? Was it a matter of Sonos not wanting to pay the wages demanded by more capable developers? Is it a case of the cart pulling the horse, with designers and product managers having disproportionally more say in the product than the engineers? Perhaps marketing wanted the ability to inject their own changes without interacting with engineering which made for an unsustainable architecture? Some combo of all the above?

Lots of things that could've gone wrong here.




While this isn't a bad rule of thumb, rewrites can be pulled off with exceptionally capable teams and leadership that understand the value of everything the original was capable of and know to factor all of that into designs, requirements, and estimates for the replacement. Where things go awry is when the replacement isn't intended to be comprehensive or is based on a shallow grasp of the original. Extensive testing with real-world users helps a lot here too.

That's expensive though, and so is almost never what happens. It's way cheaper and easier to have the designers spin up a good looking mockup and build off of that.
Sonos laid off all their US developers long ago and replaced them with cheap 3rd party contractors from 3rd world countires.
 
Upvote
71 (74 / -3)

metavirus

Ars Praetorian
439
Subscriptor++
LOL, gee some really sensitive people downvoted you...too sensitive to be on the internet I would say. But yeah he should be the first to go at this point. He has been in charge during all the many issues with Sonos and people laid off. Besides it flat out not working the new UI is terrible too and I didn't really have complaints about the last UI when so many others did.
Yeah, I was surprised at that as well. Not sure if it was the potty mouth, brevity, or Sonos Fandom, which has always struck me as a bit much. {shrug emoji}
 
Upvote
5 (14 / -9)

iindigo

Wise, Aged Ars Veteran
136
Subscriptor++
Sonos laid off all their US developers long ago and replaced them with cheap 3rd party contractors from 3rd world countires.

Well that explains a lot. You might be able to get by doing that when software isn't at the heart of your business and/or your software is very simple, but with as many things as the Sonos app does (easily multiple standalone apps' worth of functionality) and how it's the center of their ecosystem, things are bound to go wrong.
 
Upvote
52 (53 / -1)

dipzip

Smack-Fu Master, in training
79
Subscriptor
Haven’t you heard? QA is a cost center. So you fire them all, and make the devs responsible for testing their own code with test harnesses that will have 100% coverage. Easy-peazy.

What could go wrong?
Like many others on this forum, it sounds like you and I both have experience in software development. It's been nearly two decades since I've seen any software company staff a formal QA department. Not having a QA department is quite normal in my experience. And while I agree there are risks to having devs test their own code, particularly during the initial phases of the no-QA transition, I have also seen many years of successful operations using the no-QA model.
 
Upvote
17 (21 / -4)
Yeah, I was surprised at that as well. Not sure if it was the potty mouth, brevity, or Sonos Fandom, which has always struck me as a bit much. {shrug emoji}

I'm guessing it simply didn't land. Not everybody knows about the whole fuck spez thing. That context is necessary for it to work.
 
Upvote
40 (41 / -1)

50me12

Ars Tribunus Angusticlavius
7,064
Haven’t you heard? QA is a cost center. So you fire them all, and make the devs responsible for testing their own code with test harnesses that will have 100% coverage. Easy-peazy.

What could go wrong?
I don't even know if this was a QA failure.

The app is missing past features... QA not likely to test something that was a "doesn't have that" decision.
 
Upvote
46 (46 / 0)
I expect my hardware to continue working even if the company deems the product to be too old. I decide when I am ready to upgrade. Bricking devices and taking away features with forced updates will not be tolerated.

We will own nothing and be happy for it. I will purchase nothing in return.

Provide value for money, inspire me to purchase something new because it is better, not because you ruined what I already bought.
 
Upvote
49 (49 / 0)

QuantumEntanglement

Smack-Fu Master, in training
2
Subscriptor++
The message Sonos are sending is take care of investors before customers. I was a believer in their ecosystem and recommended it to at least 10+ people because it was damn reliable with acceptable sound quality. Not any more… spent 2hrs using a mix of old android phones and PCs to help a friend fix a broken system due to the new app. Now they want to reduce staff?

Executive decisions to help investor’s perception instead of customer perception will not fix the long-term problems.
 
Upvote
60 (61 / -1)
Ah the classic rewrite trap that any seasoned engineer will tell you to stay away from.

You should never rewrite the existing app. You replace parts of it at a time with testing to ensure you're not mucking things up
Generally true, but there are occasions where an app replacement could be necessary. Still, you better test the shit out of it to ensure functionality, and at least try to update the back end separately from the front end. (Sounds like Sonos did neither.)
 
Upvote
30 (30 / 0)