It depends on what no-code/low-code is used for. When used properly, no-code and low-code platforms are great. They let a much broader population of non-develo

It depends on what no-code/low-code is used for. When used properly, no-code and low-code platforms are great. They let a much broader population of non-developers build things and automate workflows. Even for people with an engineering background, they're often just simpler and faster to use than writing code from scratch. One of the best uses I've seen for these platforms is when prototyping a new startup or product idea–you can invest a few hours of work to build something that can demonstrate a proof of concept. However, the vast majority of the time I see low-code platforms being used at scale in an enterprise setting, they're being used in ways that create more problems than they solve. The core problem is that these platforms aren't built in a way that encourages maintainability and collaboration at scale. Why? When using a no-code/low-code platform, you're still building software, even if you're not writing a single line of code. And if you're trying to collaborate on that software with other people, you'll want things like version control, code reviews, unit testing, dev/prod environments, etc. Most NC/LC platforms don't provide any of this. I'm working on a startup, https://www.airplane.dev/ https://www.airplane.dev/ where we're building a platform that lets people create internal tools more easily, and it's technically a low-code approach, but it's very different than most of these "siloed" app builders out there. You can express everything as code and version control it, write unit tests against it, etc.