Earlier quoted context omitted.
developers who only know how to write fat JS frontends Yeah. This is often a big challenge for small companies / small teams. Nearly every web app is now two apps , and it's increasingly infeasible for any developer to have a mastery of both backend and frontend stacks. Not necessarily a terrible problem when you have dozens of developers, but a lot of dev teams are 1-3 people. Instead of web dev circa 2010 where you…
I don’t understand why members of a dev team back in the day would’ve been more capable of being full-stack than today... The front/back divide also existed back then, with barely any possibility of a front person ever touching the back-end (a possibility that exists nowadays, without going into its merits or demerits). For a reasonably ambitious and industrious individual nowadays it’s not unreasonable to become rea…
There was not "frontend" and "backend" developers. There were designers and developers. Designers created designs. They were usually delivered as PDFs, because the bulk of them came from print design backgrounds.
Their designs were then implemented by developers. Senior level developers tended to more of the application level heavy lifting (server-side scripting & db), with junior level developers working on converting designs to html, then to templates. By the time a junior developer moved on to app code, they were well versed and had mastered HTML and all the weird edge cases. They knew HTML.
The first real wave of "frontend" and "backend" developers came on the scene when you had designers learn Flash. They started driving more complex applications and there was a more bifurcation.
Granted even in small teams of the era, you had developers prefer "front" or "back". We tended to value "A jack of all trades is a master of none, but oftentimes better than a master of one"