Clearly this will be an unpopular opinion here, but I believe low/no-code has its place. And honestly I've seen it proven out a few times where I work. I agree that it will never replace full development in all instances, but there are times when having a developer or even an intelligent power user quickly (point #1) build out simple (point #2) solutions with very little interference from security (point #3). At least this is what I have seen first-hand in the projects that have succeeded at my place of work. The "inflexibility" of low/no-code is, in my opinion, guardrails preventing the power user from destroying more than a few decks of the Deathstar. If you want the whole thing blown up, that's when you need a full stack developer! :-)

PM here. Are some of us useless? No doubt, you'll find that in every labor cat. I agree with the person who said a good PM clears blocks and runs interference. But even when that's what we attempt to do, there's never certainty that the client won't flex the "it's our money" muscle and shut us down. It happens frequently. Clients don't like to be told uncomfortable truths about complexity and delay, they just WANT IT NOW! And as far as buffering devs from the business process and clients, ther is NO one size fits all to this. Some devs (most, I'd wager) are great at requirements gathering and client interaction. But some devs are cave-dwelling trogs that frighten and confuse the client to the point that they need a buffer. I 100% guarantee you know at least one. My point is that the PM position, like yours, requires subtlety, statesmanship, broad knowledge of the domain, and a deep knowledge of the strengths and *weaknesses* of the dev team. Yes, I know that's a word that some devs don't acknowledge. Many of us do try to not be useless.