This is a good take. To add to it a bit, there's another perspective that makes no-code solutions useful: team decoupling. You know Conway's Law about how the

This is a good take. To add to it a bit, there's another perspective that makes no-code solutions useful: team decoupling. You know Conway's Law about how the software is structured like the organization that produces it? No-code is that, but it's giving "coding power" to parts of the team that didn't have them before. E.g. a design team can accomplish a reasonable number of funnel tweaks using an A/B testing tool, and it means they get their job done faster (= more effectively), and the engineering team can focus on other problems. It's not a panacea and there's definitely risks, but I've seen it be helpful in this way in many contexts.