Yea but then instead of being an architect and an engineer, you're basically just a customer.

Or a pilot of an aircraft rather than a "Wing Engineer" responsible for controlling the flaps or a "Flight Reliability Engineer" responsible for keeping the beeping noises and flashy lights to a minimum?

I've been vibe coding a large project the last couple of days and while it is pure magic, I have little understanding of the actual code (yet!) and the output is probably worse than if a team of Software Engineers spent a few months on it, but I still get to have sane discussions with Mr. Claude Sonnet about software design patterns and code coverage. And like I said: days, not months. My "role" in this project has of course shifted from "developer" to "overseer" or "architect" even, but if I hadn't have a Software Engineering background my LLM would have produced a rather poor result.