My job was not labeled as front end, back end, DevOps, or SysOps. We did not really use those terms that are much more common place today. Just an engineer who was wholly responsible for various web properties from end user experience to server up time.
In which case OC is still wrong. It's not that "a decade ago when a front-end developer meant you handled [X, Y, Z...]" but "a decade ago there was practically no such thing as front-end development, only web development...".
https://hn.algolia.com/?query=front%20end%20development&sort...
Three pages of low vote threads with the occasional mention of front-end development.
There wasn't much of a term of front-end development 7 years ago. It's a new thing.
You had back-end devs who would do some funky front-end stuff with often atrocious UIs and a bunch of designers who would hack together some jQuery plugins badly.
The highest voted story from 7 years ago is talking about converting PSD to HTML/CSS, which many of us back then would have sneered at being called development.
which actually gives me some perspective for the speed at which FE tools seem be iterating. I'll have to keep that in mind moving forward.
Making sure Apache/PHP/MySQL didn't fall on their face under load and yelling at the front end guy to optimize his bloody SQL queries. At least that is what I did.
Wait a minute. If front-end developers handled Apache/PHP/MySQL too then what did back-end developers handle?
I used to think front-end means client-side (HTML/CSS/Javascript) and back-end means server-side (Apache-or-nginx/PHP-or-Python-or-Ruby/MySQL-or-PostgresQL).