What's fascinating to me as that it's happening at the same time as the "X as code" movement. Devops: Infrastructure as code. or dbt's viewpoint on analytics a

What's fascinating to me as that it's happening at the same time as the "X as code" movement. Devops: Infrastructure as code. or dbt's viewpoint on analytics as code (see https://blog.getdbt.com/building-a-mature-analytics-workflow/ https://blog.getdbt.com/building-a-mature-analytics-workflow...) So I'm seeing it as an exercise in finding sweet spots. There are things that have been mostly manual or point-and-click and people are seeing wins from defining and managing them as code. Usually in terms of reproducibility and testability. Then there are things that people have traditionally done in code (e.g. admin UIs) where maybe most of it can be abstracted away into a point and click tool. No-code works great until it breaks, and then your ability to debug is going to be very constrained. We're fighting that problem with some no-code ETLs using Stitch at work today, for example.