Wow. As someone working on developing a no/low-code solution, that was an insightful comment to read, thank you. I can see your words are based on personal expe

Wow. As someone working on developing a no/low-code solution, that was an insightful comment to read, thank you. I can see your words are based on personal experience. I like that you acknowledge the potential issues and weaknesses of the approach, but lean hard on the value it can offer. I agree with that too, from my own experience seeing how the system I'm building, imperfect in various ways, is valued by a growing userbase in the real world. I especially relate to the strange niches where such solutions can be found to be powerfully practical, solving all kinds of needs for the end user (who are often businesses using such tools internally). People have remarked on how Excel spreadsheets have been ab/used to great lengths, providing tangible benefits as well as possible nightmares. > ..In the real world 99% of actually used, useful programs, are boring re-hashes or CRUD, APIs, Web Services, UIs, and so on. That's the stuff people pay for which keeps the lights on. Personally I feel it's 80/20, or less still - but I do believe no/low-code solutions are pushing the threshold described in the article, where they're better/simpler/easier to use and solve user needs, without going into the world of code. I think it's still an exploratory field, finding what patterns work best, the right primitives for people to work on a higher level of abstraction than code.