Low/no-code solutions (LNCS) almost always become maintenance headaches, except for a few highly trivial uses. They are kind of like renting a motel for 20 year

Low/no-code solutions (LNCS) almost always become maintenance headaches, except for a few highly trivial uses. They are kind of like renting a motel for 20 years: they are easy to get into, but will empty your wallet in the long wrong compared to buying a house. For one, newbies don't know how to write/build software for future maintainers in mind. It's a skill that often takes years to do well, often by having to rework others' poor code. And LNCS often lack abstraction and factoring abilities, creating redundancy that become sources of mistakes down the road. Maybe someday an innovative idea will change this, but I haven't seen it yet. LNCS have been attempted for 30+ years, and the newer ones seem to be using variations on already-tried themes. Thus, I'm skeptical of a different outcome. Unless you are an R&D firm, don't be a guinea pig to shiny LNCS claims.