A ham sandwich with a million buttons that each do different things, sure, but it’s not impossible to learn the ones you need, and they rarely break. How many times have we seen apps fail one of those criteria?
It also has the distinction of printing a massive amount of money and being a huge competitive advantage over other ML institutions — like, say, Facebook. So it seems obvious why developer experience wasn’t prioritized, just “ok.”
But using it, I feel deeply in my gut that there has to be a better way. But I've not seen anything across any of the major clouds that is much better.
2) For awhile Google wanted to move more new development onto GCP (an effort called "Google on Google"), but it had limited traction and has been abandoned AFAIK, because internal tooling, infrastructure, and devex was just so much better than what GCP had to offer.
2) feels like this just proves my point
Rather than force the teams who developed the original tooling inside Google to develop a similar public facing commercial product, they had GCP developers write parallel tools, or they bought third party tools and tried to integrate them. Both solutions proved not as easy as management had hoped.