Readit News[1] All teams should have a Jordan, a kobe, a shaquille or a combi. One needs A players and supporting cast. It is not the culture or the org who decides upon the evolution of the heroism. It is the hero who builds a team around him/her. [2] the scrum or agile saga that promotes that all team members should be able to do what all team members do is just excel-minded-nonesense. Cant win championships with only goalkeepers, or only midfielders. Cant prep one to be good in both either during a lifetime.
Probably google wants weat crops that always look alike and are predictable?
Big tech is in a really tough spot when it comes to innovation. Google has developed a reputation for killing off products too easily. Many have commented here and elsewhere that you can’t trust them to invest in using their new products because they might just kill it off and leave you in the lurch. Of course, you get a self fulfilling prophecy as then too few people use the product for fear that it’ll get killed off.
But I’m guessing Google is also more hesitant to launching a new products that since it neither wants to worsen its reputation for killing them, nor does it want to support a product indefinitely, even if it’s not profitable.
So then what? The answer probably should be that Google should buy up startups that have figured out product-market fit and just need to scale. They can’t do that though because the FTC is already breathing down their neck with anti-trust suits.
Google actually is investing in a lot of very transformative technologies—AI obviously, but also quantum computers, biotech, and autonomous vehicles. Those are things that just aren’t well very well suited to 20% projects.
Personally, I voluntarily built and run open source apps for 16 different cities for their transit system. This gave me two weeks to update 16 apps, for no benefit of anyone. My app is a PWA, and the Android version just uses cordova + a few plugins to add a few native options. Unfortunately, updating cordova to support the new target android api broke some of the plugins, which haven't been updated yet, so it ended up being a full weekend of work and testing.
Truthfully, I'd prefer to get rid of the app and just have users go to the website and install the PWA, but the average user still doesn't know how to do this. And the Play Store is still the first place users go to find apps. If google would just allow submitting a PWA directly to the app store, that'd be nice... I am not looking forward to doing this yearly.
Professionally, we are also scrambling. We have a legacy app that some supported customers are still using until the end of the year. The app is a fairly complex application, and basic testing has already shown that just changing the target api version has broken quite a few things. We have gotten the extension, but we know this will take 1-2 weeks of developer time + 1-2 weeks of QA's time, for an update that does nothing but appease Google. All for an app we are going to officially remove from the store at the end of the year, once all customers transition to the new app is complete.
Is see clean code but references about hexagonal architecture could be way more impactful, IMHO
After the first 2 days on the project this should be clear, shouldn’t it? And all the other proposed questions are answered in the first 10 minutes on the first contact with the PO. 10 months later on the project the only thing that matters is what is needed and when.