3 ms·
The separation of frontend and back end has devalued both, and also can complicate both. There was a time where there weren't 15 job titles to build a web app,
by j45 3y ago
The separation of frontend and back end has devalued both, and also can complicate both.
There was a time where there weren't 15 job titles to build a web app, and building a webapp was relatively the same. This sharding, pershaps to make tech adjacent jobs more approachable was a good idea, but I don't see it having evolved.
Front end can be very, very complex, sometimes too complex. The same can be said about backend.
If anyone reads about actual full stack development, where a developer had to learn the bare metal, linux, devops, to be able to serve a single page.. it did become easier, but the understanding of how things can best work together or not is a gap I see more and more.
Complexity slows down development pace, which is the antithesis of growing fast. Adding more people triggers the mythical man month clause.
Burning innovation points early on unnecessary complexity for the future is often the single biggest nail in the coffin when complexity and curveballs arrive and flexibility seems to have dissapeared to do what's needed.
Technologies like Alpine.js, Htmx, especially livewire, all are bringing the best of the tooling together with an unapologetic simplicity.
Should it be more complex to build the same 2004 webapp in 2024? I hope not in each and every case.