No/Low-Code: Letting people who don’t know what they’re doing half-ass things poorly without understanding the first thing about it and leaving them completely incapable of fixing it when something goes wrong and then pissing off actual developers when they have to go into the Playskool interface to fix it.
I’ve worked in business process automation for a bit. In most cases I’ve seen no/low-code is introduced when IT can no longer service technical debt and won’t deliver any new features within reasonable timeframes (usually a result of decades of underfunding). No „real” developer will be ever fixing no/low-code solutions either because why would they? Are they going to fix something in an alien tech stack? Are they going to implement this functionality properly? No, because they never had resources to do that.
“So we have this procedure in Excel which the entire department relies on”
I have inherited and also created and passed on many of those Excel files in my professional life. They get a bad rep but they’re also as bad as everyone says.
Why would we? lol, we wouldn’t. But when management says “Help Delores with her app problem”, what are you gonna do?
I’m probably biased because I only work for big corpos and it would never be this simple there. IT is usually safe from this kind of dumb stuff, but then again that insulation might have been part of the reason why business people were considering no/low-code.
Well yeah but if the example is Yunohost and web interfaces, this makes sense
Will not support complex firewall setups or even AI scraper protection, wireguard tunnels, tailscale/headscale/whatever alternative but it is an easy docker frontend I guess
I have difficulties finding open-source references in the article!? Where is it?
