Ah I getcha now. I think my point is still valid though - and in fact full stack engineers are more likely to write a spaghetti code mess from the back to the front because they control the entire feature and may see the code in its entirety as one "feature" and thus one code base.
You are valid. I wrote a whole post about this but the reply didn't seem to work so I lost the full reply.
I did write most of my ideas to "underwater"'s comment.
Basically, my position is more on the fact that if you need things done quickly, then a full stack guy is the one you need. You can fix/abstract the code later. In fact, I encourage that. But to get the ball rolling, you're gonna need some quick and useful (sometimes ugly spaghetti) code.
Its a trade off that must be made, especially you're rapidly building your product.
