Skip Navigation
8 comments
  • 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.

    • 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

8 comments