Seems like the author has a case of all or nothing. The real power in agentic programming, to me, is not in extremes, but in that you are still actively present. You don't give it world-size things to do, but byte-sized, and you constantly steer it. It's to be detailed enough to produce quality, and to be aware of everything it produces, but not so detailed that it makes sense to just write the code yourself. It's a delicate balance, but once you've found it, incredibly powerful. Especially mixed with deterministic self-checking tools (like some MCP's).

If you "set and forget", then you are vibe coding, and I do not trust for a second that the output is quality, or that you'd even know how that output fits into the larger system. You effectively delegate away the reason you are being paid onto the AI, so why pay you? What are you adding to the mix here? Your prompting skills?

Agentic programming to me is just a more efficient use of the tools I already used anyway, but it's not doing the thinking for me, it's just doing the _doing_ for me.