The problem with software is infinitely larger when rewriting, refactoring and maintaining ”not code”. I’m in such a situation as we speak, and I’ve worked wit

The problem with software is infinitely larger when rewriting, refactoring and maintaining ”not code”. I’m in such a situation as we speak, and I’ve worked with low/no code workflow tools for more than a decade. I’ve been part in building two: one BPM(N) workflow based and one graph-based data-modeling, form-building, event-sourced nightmare (like Alan or structr [1], both probably 10 years old by now, btw) - it goes for a great sales pitch but never touches on the finer points of maintaining and iterating on systems over time; a.k.a ownership! Coding is usually not the issue, especially in business settings. Rather it’s about accumulating domain knowledge and expertise and figuring out boundaries. It’s perhaps even more about owning the end results over time. There’s a sort of quasi-competency built up around tools like this - you still need to understand how to build and govern systems, which is the hard part. You end up with non-system thinkers that can build opaque stuff in a DSL. This ends badly. Yeah, I’ve been around. Also blockchain will change everything. ;) [0] https://alan-platform.com/ https://alan-platform.com/ [1] https://structr.com/ https://structr.com/