15
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 31 Aug 2025
15 points (82.6% liked)
Opensource
6636 readers
330 users here now
A community for discussion about open source software! Ask questions, share knowledge, share news, or post interesting stuff related to it!
⠀
founded 2 years ago
MODERATORS
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.