I recently got into an argument with some friends (that are not programmers). They argued that nocode is a good thing to do projects on because they are very fast, and I could not think of an argument against that. So yeah, I feel kind of odd about the fact that noCode could someday replace a ton of programmers.
Here's an unpopular take; if no-code is threatening your programming skills, you should probably try expanding your horizons. Maybe those people can spin up a SaaS in a matter of 15 minutes, but how many of them can make POSIX API calls without relying on complicated, expensive, nonfree tools? By the time you've hacked together a no-code solution, you've probably wasted more time than just learning and implementing the "proper" way to do it.<p>Again, maybe that's a reductive way of looking at it. But the number of low-wage Javascript employees are due for a reckoning, and I could see no-code coming to eat their lunch. Will it replace embedded driver development or systems programming? Not for a <i>long</i> time.
Even no-code requires that you be able to break a problem down to solve it, and that involves knowledge, skills and experience. Programmers will adapt, not disappear.