Depends on the use case. As someone without a lot of budget to hire devs, I currently use no code in my company extensively, our Airtable has 50 tables, some o

Depends on the use case. As someone without a lot of budget to hire devs, I currently use no code in my company extensively, our Airtable has 50 tables, some of them with > 10k records. There is certain excitement to do all in no-code now, but the ceiling is truly there as the article says, the rule of thumb is that if something is operational and not core for business we do in low code, if it is business critical (we lose money if goes down) then it gets coded. What happens if our business goes down, and is <low code tool> fault? We can't just say "welp" to our customers complaints, recently we saw that not even Atlassian is immune to long outages. Also what happens when the market needs for you to do "X" and the tool can't? Now you are stuck in a low-code environment with 3 months migration while the competitors pass ahead. We also got a lot of bugs with this tools on things that were supposed to work, and it slowed us down significantly. From what I see that the best use case of low code is kickstarting software projects. If done with the right tool (one that allows for easy exporting), it allows to get the data in order for future scaling with code. Since changing application logic in a living project (and even the entire language / framework) happens all the time, but the data generally does not, this seems like a best case scenario for a new feature or product that still needs to validate their market fit.