Where Did All the Web Developers Go?
Stop using terms which obscure the actual thing you're trying to do. Do you develop for the web? Congratulations! You're a web developer.
By Jared White
There’s a dangerous problem in our industry right now, which is that we’ve job-title’d and buzzword’ed and abstracted our way out of recognizing the actual thing we’re all doing if we participate in and care about the global open standard that is the World-Wide Web—which is, y’know, developing for the web. We used to call people who do that—crazy I know—a term you don’t hear so much any more: web developer.
I find this situation deplorable. The web is one of the greatest inventions in the history of the human race. It’s one of the most incredible examples of an open specification iterated upon and evolved by a consortium of governments, companies, and individuals spanning the globe. There’s literally nothing else like it, not even close.
I personally like identifying as a Rubyist, perhaps a Rails developer or something like that—but that’s only in the sense of centering myself in a particular stream of programming, community, and ecosystem tools. At heart, above all else, I’m a web developer. And I will continue to use and celebrate that term as long as the web—as it’s actually defined by the open specification itself—exists.
Will you join me? You can start by refraining from using the term front-end developer, or back-end developer, or full-stack developer, or whatever. Use the term “web developer”. Do you develop for the web? Congratulations! You’re a web developer.
Revel in it.