you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 1 year ago (4 children)

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.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 1 year ago* (last edited 1 year ago) (1 child)

    Why would we? lol, we wouldn't. But when management says "Help Delores with her app problem", what are you gonna do?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year ago

    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.

  • source
  • parent