> I see 100s-1000+ people work on software product development and very little happen with the product for YEARS while there are tons of obvious (to me) improvements possible

I worked in an org with about 60 engineers all working on the same product and I have to actively _not_ fix small issues to keep my sanity. Whenever I see a small issue I would have:

0) If it changes anything visible to the user discuss it with UX or PM (very annoying)

1) Fix it (easy part, usually)

2) Create PR and explain issue

3) Get someone from the other overworked team to look at it (not as bad if it is from my own team)

4) Get comments for often trivial things (depends a lot on the changes)

5) Get asked to refactor some related functionality because the fix is a bit messy without it (workaround) or to address the root cause of the issue (this is usually a big deal)

6) Possibly several rounds of reviews

7) Someone break my fix next time anyone makes a change to that part of the code

All to get something done that wasn't asked of me, that my manager will probably not see or know about unless I bring it up, that if I do bring it up my manager will probably tell me to not waste time on it since "it is the other team's problem".

So I would either ignore the issue or create a ticket that will probably be ignored. Only if it is a really trivial uncontroversial change would I bother to actually proactively do it.

Thanks. This explains Android. Because the only other explanation would be no dev at Google actually uses it day to day as their phone because it has so many dumb little infuriating things.

Example: Why does my kitchen bluetooth, that I connect to the most, and that I am located nearest to, always go to the bottom of my bluetooth list, meaning I can't select from the quick screen and have to unlock and pull up another screen (when my hands are kitchen dirty)? I consume media on bluetooth the most showering and in the kitchen. The devices used should be 1 and 2, but they never are. EVERYTHING on Android is this 'devs must not actually use this' unfriendly. I still can't use the timer function using voice because if I don't wait for my phone to repeat back all the timer info and I touch something it just blanks out my timer, so I've learned I can't trust it after ruining too much food. These are my two most common use cases for my phone and where it ads value to my life, and both are needlessly annoying on Android causing me to hate the platform because in 2025 these little details should work. Someone at Google must cook things that need timers. Someone at Google must listen to music/audiobooks and have enough devices they spill over to the secondary screen. If feels like Android has zero actual world love/care from the devs or these daily annoyances would bubble up instantly.