&gt; I&#x27;ve seen plenty of projects with separate front end and back end developers fuck up because the front end developers try to solve &quot;back end problems&quot; on the front end and vice versa.<p>I totally agree, but even if you have a front-end and back-end communicating well, sometimes the front-end developers throw too much over the wall to the back-end, like when the front-end &quot;thinks it is more intuitive if the request looked like this&quot; instead of something else that would be just as easy to create and would be much less work on the back-end. And I&#x27;m sure the opposite is true as well with back-end putting too much work on the front-end.<p>And, in the argument against a single full-stack developer being the solution to this problem, I&#x27;ve seen extremely talented full-stack developers create some terrible user interfaces, and some who created great user interfaces that would struggle to create adequately performant server-side services to back them.