3 ms·
> When everything takes 20% longer to ship than you planned because every other week some random team(s) is forced to do unplanned, immediate rewrites by a vend
by gtirloni 3y ago
> When everything takes 20% longer to ship than you planned because every other week some random team(s) is forced to do unplanned, immediate rewrites by a vendor
This vendor is certainly not GCP in this case.
Every other week? Immediate rewrites? Is this even based on reality?
- busterarm 3y agoGCP is the best of Google's offerings and they still manage to do this. If you're using Google APIs like Places, AdWords, Geocoder, etc, they frequently make breaking changes with no announcement. I've had many, many days in my career of having to drop everything to patch mission-critical glue code to keep up with Google APIs. Also keep in mind that the documentation for their SDKs is frequently outdated and incorrect, especially around authentication and to the point that I often just deferred to reading the source code over reading their docs. And that's even if their SDK was in a working state, because often their own SDKs would lag behind their own API changes and you'd have to try out ruby, python or php to find one that worked properly (although golang always works, because that's what Googlers actually give a shit about). Maybe its gotten better in the last few years, but that was solidly my experience from 2010-2018 and those were a lot closer to "Peak Google" than now. Now I write less code against their APIs, but I also have about 10M/yr in GCP infrastructure that I manage and it's also a treadmill even though we stick to the basics (VMs, GCS, Cloud SQL, GKE).