Over the years at TechSmith the ASP and VB6 (mostly) gave way to C# but that wasn’t the only change. Somewhere along the line I became a software engineer.
I can’t speak for the industry as a whole but at TSC there was an impression that web devs weren’t “real developers” compared to the software engineers working on the company’s desktop products. So everyone became software engineers and everyone was equal, even if the job didn’t change at all.
Fast forward to several years ago and the term “full-stack engineer” starts being thrown around. A full-stack engineer being someone who writes back-end code and front end code and maybe does some image manipulation and can do some server management… And I fail to see how this isn’t what we used to call a web developer.
As an industry, did we create a new title just to get the word “engineer” into it? “No, I’m not one of those slacker web developers. I’m a full-stack engineer.” I get that the term became famous when Facebook was (supposedly) only hiring full-stack devs but why give it that name when “web developer” already meant that.
For a long time, even after my title at TechSmith changed, I defined myself as a web developer. One of my mentors called me out on it and I couldn’t explain why I clung to that label. Maybe it’s because, the way I see it, “web developer” is just less of a mouthful than “full-stack engineer” and more accurate than “software engineer.”
If there’s supposed to be a difference between web developer and full-stack engineer, I don’t see it.
I should say that I don’t actually have a problem with the full-stack engineer title. Web development has evolved. There are fewer gaps between web development and mobile development than there were a decade ago, for example. I just see web developer and full-stack engineer as the same thing and think it’s jarring to see the titles used as if they’re not.