_Sorry for posting this again, but I accidentally deleted the original when I changed web servers recently, and I thought it was worth reprinting. Let that be a lesson to us all in the [Tao of Backup](http:/
The great Remy Sharp ([@rem](https:/
> I don't know why I thought it was uncool to be a "web developer". Perhaps because it's utterly vague.
> What "web developer" does mean to me though, is this:
> Someone who writes code for browsers. Likely from the school of view source, is comfortable with drop-in libraries, understands standards and best practice techniques. But mostly, a tinkerer.
I like his definition (especially the part about tinkering), but I think that it's incomplete, being merely functional.
I suggest that the term "web developer", by its definition, carriers a philosophical drive: to develop the web. That is to say, a web developer should visualize how they would like the web to be (as a whole), and build their own projects in a way that reflects that vision.
This is something I've tried to do myself, both in my professional and personal projects (albeit with varying degrees of success). To me, being a web developer means that I should use [responsive design principles](https:/
As a web developer, I want to participate in a decentralized web, and would rather use a self-hosted, fully-open [social media platform](http:/
All in all, I think this definition adds an air of legitimacy to the "web developer" title. As I noted in a [comment](https:/
_TL;DR - A #WebDeveloper should "develop the web" by building their projects in accordance with their own vision of how the web should be. For me, that means using open source software to build standards-compliant, accessible, and secure sites and apps.