Dividing front end from back end is an antipattern
No, it&#x27;s not the division that&#x27;s the problem, it&#x27;s having one driving the other.<p>The thing is front end dev is actually very different from back end dev. Having done a lot of both, I can say that they require very different skillsets and different knowledge, so it is quite normal that they&#x27;re not done by the same people.<p>Now, if your team is frontend first, you&#x27;ll likely screw up your backend design in the sense that you won&#x27;t be able to define a nice API for it. Similarly, if your team is backend first, you&#x27;ll have a nice API, but probably won&#x27;t think about all the frontend needs, and will have to patch things nastily down the road.<p>Truth is, coordinating people with different skills is hard.<p>Now this kind of articles take aim at teams that don&#x27;t manage to make it work. So yeah, not being great at managing teams is an antipattern...