I have seen this happen many times - the only way to get other teams to prioritize your work is to convince your leaderships its important so they can talk to the leadership of those team that it is important. Sometimes, even after leadership pressure, teams refuse to move priorities or don't deliver on time - always account for those as well.
No matter what you do, the slow pace & politics of large companies will hinder your growth. There would be some features/projects that would be absolutely unfeasible - not because they are technically harder but because you won't be able to reach alignment.
Smarter thing to do in these situations is to move on to something else that can deliver impact. If you keep delivering impactful features on your own (even if it means some duplication of effort), you will notice a lot of other team's manager would be interested in integrating with you as they now think of your feature/product as a potential cash cow & the cycle turn the other way - you product grow way faster than you predicted because now the company is working to enhance it & in doing so, they will bring customers from different touch points the company has resulting in a stronger moat.
Ofc, all this requires patience, vision, strategy, politics & luck. Its different ball game from startup where you throw N things to the wall and expect K things to stick. Here you can only throw maybe N/2 things to the wall and maybe K-x things will stick but if your strategy is correct, those K-x things will be far valuable in a big company.
100% agreed. This is probably useful to enforce standards in a team that might be lacking it otherwise. For big tech teams, it might be useful to do such CRs randomly to make sure devs in the company are aligned on best practices.
Should they have not been suspended from trading for a certain period of time in addition to the fine? Take for eg, sports as an analogy - Individual players, no matter who popular they are, are almost always suspended/banned if found cheating.
Capital gains over last few years have been insane. The fine might be higher but a 400MM profit 5 years ago would have easily doubled just investing in SP500.
Its not just the initial setup that's painful with Arch, the whole rolling update model means things break often and I no longer have the patience to patch them. But I do agree that linux provides a better env for development compared to macOS. On Ubuntu atm and works like charm with flexibility to extend it as I like.
No matter what you do, the slow pace & politics of large companies will hinder your growth. There would be some features/projects that would be absolutely unfeasible - not because they are technically harder but because you won't be able to reach alignment.
Smarter thing to do in these situations is to move on to something else that can deliver impact. If you keep delivering impactful features on your own (even if it means some duplication of effort), you will notice a lot of other team's manager would be interested in integrating with you as they now think of your feature/product as a potential cash cow & the cycle turn the other way - you product grow way faster than you predicted because now the company is working to enhance it & in doing so, they will bring customers from different touch points the company has resulting in a stronger moat.
Ofc, all this requires patience, vision, strategy, politics & luck. Its different ball game from startup where you throw N things to the wall and expect K things to stick. Here you can only throw maybe N/2 things to the wall and maybe K-x things will stick but if your strategy is correct, those K-x things will be far valuable in a big company.