2) "System structure mirrors organization". I.E., it's an indicator of a fragmented and disorganized structure that's not likely to produce cohesive product results.
As much as I like to dunk on how messy things can be at Google I don't think this is a really good example. Apart from small startups I would be scared if you served all of them from the same base host.
The many domains is a problem because it suggests a many-teams approach to product development, and the more cooks in the kitchen, the more likely a repeat of Gemini 1’s rollout, which was a mess [0].
Basically I’m looking to see that Google cares about the meta-level user experience of finding, understanding, and using its products, and scattering key usage details around the internet is not a good sign. It suggests deeper process problems if a simple issue like this either didn’t get noticed or can’t get fixed.
* the parent link is to storage.googleapis.com
* There's documentation on ai.google.dev
* The announcement blogpost is https://blog.google/technology/developers/gemma-3/
* you try it on https://aistudio.google.com/
It's helpful to have a top-level post like this, but can some PM please consolidate this into, IDK, ai.google.com/gemini?