I've had a lot of frustrations with "APIs are eating the world" over the last two years. 1. "No code" interacts badly with "infrastructure as code." Instead of

I've had a lot of frustrations with "APIs are eating the world" over the last two years. 1. "No code" interacts badly with "infrastructure as code." Instead of a client library, you get a web admin console. If you want your configurations to be reproducible, durable, and auditable, you now have to build a client yourself or use a third-party client. Case in point: Snowflake directing users to a buggy third-party Terraform provider built by some random organization that's always several versions behind. 2. "No code" is much harder to test. You have to deploy changes to see them. You don't have the tools to mock them out. There is no local testing. At best, you can have a test environment. But to do end-to-end testing within it, you need to rebuild basically a mirror image of prod, since you can't mock any API boundaries nearly as easily anymore. As a result, a lot of "testing" ends up being done by pushing to prod and trying to roll back when needed. 3. "No code" often means surprise upgrades and feature changes that are out of your control. Some vendors (e.g., Databricks) mercifully display a toast in the GUI prompting you to update. Many just post some release notes somewhere and call it a day.