Engineers who can code should still use low-code/no-code platforms because they shift focus from pure technical work to translating business needs. Faster development, richer ecosystems, and open-source components matter less than the shared space these tools create between technologists and business users.
Why should an engineer use low-code/no-code? And I get this question all the time where it can be startup technical founders, it can be CTOs, it can be just engineers working on things that'll say, look, I know how to solve this problem in JavaScript or Python or Rust or whatever tools they like to use. Not only that, there's actually a good deal of ecosystem around it that allows for some better support. There are many things that are actually better about using those tools. They get to go faster, they have better support mechanisms, and a lot of this stuff is open source. Why would you ever want to go to low-code/no-code? And the answer has a lot to do with the way you bridge into the business. If you believe it is your job to create software as an engineer, then yeah, you should use the tools that are going to work the best for you because that's where the center of gravity is. The premise of low-code/no-code is that the center is not on the technologist, it's between the technologist and the business user. That using it as a means of communication is a key to value.
