Yes but if you don't care enough to think about, analyze, and decide how to improve your architecture, it doesn't matter. And I'm seeing that a lot with full vibe code code bases
Caring about the architecture only matters if you intend to build on top of it, where it become hard to mutate for needs. Big refactors are quick and (relatively) cheap if you don't care about the code.
Don't get me wrong, I am not in any way a fan of vibe coding but the "you're going to vibe code yourself into a corner you can't get out of" argument doesn't hold water.
Yea, probably with a more expensive model.
Problem is:
Eng 1 vibe codes team into a corner and forces Eng 2 and Eng 3 to either review a hideous amount of slop code or pretend they reviewed it.
Now who will vibe code the team out of the corner? Eng 1 is too lazy or at least doesn't know how to get out of the jam and Eng 2 and Eng 3 are not janitors to clean up after Eng 1 all the time.
You might say fire Eng 1, but by all tracked metrics he is a 10x engineer out producing everyone else!