A lot of these “auto-pilot” apps have thousands of people employed, I don’t get it. Like, what is there to work on once you have things working pretty well? If anything they just start ruining the product over time…
Tbh most employees at a company this size become risk mitigation more than anything else. Once you’ve reached a certain level of success, you’re looking at what doesn’t move the needle as much as what makes it move positively. There could be a feature that is a major QoL improvement, but because in a test segment it performed 1% worse than base then it won’t be implemented.
Spotify, I believe, still works in the tribe and guild model that they created.
Chapter = people with the same skill set, squad = a group of people from different chapters focused on a single project, tribe = a group of squads focused on a large business goal, guild = a collective of folks who have a shared interest like Data Privacy.
Suffice to say, Agile is an imperfect tool and as you try to scale it, you need an increasing number of people to support it and make it run. Coders and Designers are likely just a fraction of their head count.
I’ve worked places that don’t have that support structure in place and they’ve stagnated for years struggling to get the most basic of decisions made. Decisions is what it is about too. Rarely do you get actual leadership from the c-level and especially from a CEO. So you end up with a lot of cooks trying to work out why the broth doesn’t taste quite right and lacking confidence to just add a bit of salt.
Probably data-analysis/AI type stuff to track users and advertise “better,” making the backend more efficient to reduce costs, and adding support for new hardware. A lot of big, very profitable companies also have skunkworks-like projects for exploring new ideas and prototypes, most of which never make it into production.
It’s both amazing and annoying that Google is perfectly able to create useful apps for iOS (despite the huge limitations the OS imposes) but Apple can’t figure out how to make any Android app that isn’t utter crap with fewer restrictions imposed on them.
The app exists in its current state on purpose. The idea is not to give you a seamless and masterful listening experience. If it was, they wouldn’t compress tracks to 192kbps or less. The idea is to keep you trapped in their ecosystem and give you just enough value to not cancel your subscription.
My guess is for every 1 developer there’s 10 or more non technical administrative jobs. Most tech companies are grossly fat worth useless non productive employees that do very menial bureaucratic work. Think Office Space, but less neck ties.
How do they have this many employees and an absolutely trash android app?
A lot of these “auto-pilot” apps have thousands of people employed, I don’t get it. Like, what is there to work on once you have things working pretty well? If anything they just start ruining the product over time…
Tbh most employees at a company this size become risk mitigation more than anything else. Once you’ve reached a certain level of success, you’re looking at what doesn’t move the needle as much as what makes it move positively. There could be a feature that is a major QoL improvement, but because in a test segment it performed 1% worse than base then it won’t be implemented.
Spotify, I believe, still works in the tribe and guild model that they created.
Chapter = people with the same skill set, squad = a group of people from different chapters focused on a single project, tribe = a group of squads focused on a large business goal, guild = a collective of folks who have a shared interest like Data Privacy.
Suffice to say, Agile is an imperfect tool and as you try to scale it, you need an increasing number of people to support it and make it run. Coders and Designers are likely just a fraction of their head count.
I’ve worked places that don’t have that support structure in place and they’ve stagnated for years struggling to get the most basic of decisions made. Decisions is what it is about too. Rarely do you get actual leadership from the c-level and especially from a CEO. So you end up with a lot of cooks trying to work out why the broth doesn’t taste quite right and lacking confidence to just add a bit of salt.
Probably data-analysis/AI type stuff to track users and advertise “better,” making the backend more efficient to reduce costs, and adding support for new hardware. A lot of big, very profitable companies also have skunkworks-like projects for exploring new ideas and prototypes, most of which never make it into production.
In my experience it’s always new apps that ruin the existing experience.
deleted by creator
Well, they have to make new, broken terrible features and then come fix them when people complain by basically putting it back to how it was.
Haha still, does that really require 9,000 people to do? Surely you can half-ass some new features with like a few hundred people?
To be fair, even Apple Music and Tidal are trash on Android. And Apple is a $3 trillion company with over 150k employees.
It’s both amazing and annoying that Google is perfectly able to create useful apps for iOS (despite the huge limitations the OS imposes) but Apple can’t figure out how to make any Android app that isn’t utter crap with fewer restrictions imposed on them.
@d3Xt3r
@hesusingthespiritbomb
They want you to buy Apple.
Don’t negotiate with or give in to terrorists!
@ohlaph
I blamed my Subaru for a lot of my issues then i switched apps and amazingly every single issue went away.
The app exists in its current state on purpose. The idea is not to give you a seamless and masterful listening experience. If it was, they wouldn’t compress tracks to 192kbps or less. The idea is to keep you trapped in their ecosystem and give you just enough value to not cancel your subscription.
My guess is for every 1 developer there’s 10 or more non technical administrative jobs. Most tech companies are grossly fat worth useless non productive employees that do very menial bureaucratic work. Think Office Space, but less neck ties.