I have to agree.<p>You can get a back-end developer to do front-end. He might lack the experience to deal with some gotchas or browser compatibility but it&#x27;s nothing that can&#x27;t be solved with a simple Google search.<p>A front-end developer doing back-end, on the other hand, might not work as well.<p>In my experience they often fail to come up with anything remotely modular on their own, write maintainable code, understand the design concepts of more &quot;advanced&quot; frameworks like Angular or doing anything different than copy-pasting some jQuery snippet they found on yahoo answers.<p>It&#x27;s not that JavaScript forces you to write spaghetti code, it&#x27;s just that until very recently it was mostly written by clueless morons that didn&#x27;t know any better.<p>How can you write your front-end in something like Reagent if most of your staff get micro-strokes when being asked to type {{ }} instead of &lt;%= %&gt; in your new template system or go la la la can&#x27;t hear you when you mention the merits of CSS preprocessors?<p>Fortunately this is all changing as the result of front-end these days getting more &quot;mentally stimulating&quot; thus capturing the interest of back-end developers (the ones that more often than not happen to have degrees).<p>disclaimer: anecdotal evidence etc