Just read the first couple of posts in the series and it's excellent so far. The author really nailed something that I have struggled to express for years. To paraphrase heavily, purported "low-code" solutions really just mean "our code". If the consumer is 100% fine with out of the box (or "supported" solutions), then the vendor's software really is worth it.
But businesses rarely just want what's "out-of-the-box", because no business decision maker gets promoted by using off-the-shelf tools, exactly like they are designed. They have to add their "thumbprint" to the software, which usually means inventing some ridiculous feature that their company "must" have, and which typically breaks the high-level abstraction provided by the software.
So now some poor schmuck entry-level dev is tasked with breaking an abstraction that was never designed to be broken, in a ways that no one has ever encountered (and is unlikely to be able to help with). Ask me how I know...
I have the same thoughts, I recently was tasked with looking at a Shopify website that was built with a no code tool. It’s unfixable. How do we fix this as an industry? I don’t think we do.
But businesses rarely just want what's "out-of-the-box", because no business decision maker gets promoted by using off-the-shelf tools, exactly like they are designed. They have to add their "thumbprint" to the software, which usually means inventing some ridiculous feature that their company "must" have, and which typically breaks the high-level abstraction provided by the software.
So now some poor schmuck entry-level dev is tasked with breaking an abstraction that was never designed to be broken, in a ways that no one has ever encountered (and is unlikely to be able to help with). Ask me how I know...