A succinct way I’ve framed the split is that a front-of-the-front-end developer determines the look and feel of a button, while a back-of-the-front-end developer determines what happens when that button is clicked.
Doing it right requires a different pace of working and a much broader thought process than “ok, let’s get this thing out the door.” Which is super tough because most workplaces place a huge emphasis on getting things out the door, and fast. Little agile tickets that are expected to be completed in micro sprints to me seem to be antithetical to doing it right.
Once you’ve had a taste of effortless updates, it’s awfully hard to back to manual everything.
So they didn’t.
And neither did thousands of their peers. It just simply wasn’t worth it. The inertia was too strong.
The old web, the cool web, the weird web, the hand-organized web… died.
And the damn reverse chronology bias — once called into creation, it hungers eternally — sought its next victim. Myspace. Facebook. Twitter. Instagram. Pinterest, of all things. Today these social publishing tools are beginning to buck reverse chronological sort; they’re introducing algorithm sort, to surface content not by time posted but by popularity, or expected interactions, based on individual and group history. There is even less control than ever before.
There are no more quirky homepages.
There are no more amateur research librarians.
All thanks to a quirky bit of software produced to alleviate the pain of a tiny subset of a very small audience.