As a consultant in the business automation and data space, the promised "paradigm-shift" is sort-of accurate but a little too optimistic in what the author beli

As a consultant in the business automation and data space, the promised "paradigm-shift" is sort-of accurate but a little too optimistic in what the author believes the implications are. No-code/low-code has been a game changer in many ways for businesses. It lets people dip their toes into improving their efficiency and productivity with low-hanging automations and simple apps. These things can have huge payoffs. And if you stick within that realm, it actually is a paradigm-shift to be able to build solutions as a non-tech person. But there's always a point where you: 1. need more complex no-code/low-code solutions to get big pay-offs 2. have a mess of so many no-code/low-code solutions that they end up causing tons of maintenance/issues and you have trouble getting all your separate solutions to play nicely together You end up spending a lot of money to get someone who is very advanced with those no-code/low-code tools (which usually ends up with code solutions inside of those tools), or end up building completely custom solutions anyway. Also, there are a lot of nuances in what could be considered no/low-code. This article isn't too clear on which types of applications are considered no/low-code, and throws out everything from cellular-IoT infrastructure to MES. Is something like Tableau low-code? Or are we talking more about the Zapier kind of tools? Both of those examples have giant roadblocks once you get to a certain point, where you need some type of dev/architect knowledge to really get the most use out of the tools.