“The HTML guy”
I’ve recently started on a new assignment (which is mainly the reason that I haven’t been able to muster any extra strength to blog, besides from my family being sick…), and I’m hired as a subcontractor. This means that I’ve been introduced to a lot of people the last couple of days, and it has almost exclusively been with a term that I hate:
The HTML guy.
Maybe it’s just me, maybe I’m overly sensitive. I mean, I’m fairly convinced that none of the people who have used the term meant to be condescending. But still, that label feels like something less worthy to me. Yes, I do code HTML, but it’s just a small portion of my tasks/skills; to be technical, a majority of my time probably goes into CSS (and consequently, covering up for IE flaws each and every day), and if it’s a fun project, a lot of well-motivated JavaScripting to enhance interaction and usability.
And this is just to mention the major building blocks of my work. Then there’s accessibility considerations, knowing the ins and outs of web browser shortcomings and inconsistencies, a bit of information architecture, some design and especially Photoshop knowledge, knowing the back end technology well enough to be aware of the possible obstacles as well as opportunities it gives you etc.
Perhaps it’s because dealing with “just” HTML feels less worthy (although taking a look at the poor HTML code in most of the web sites in the world, it seems extremely difficult)… Still, I just don’t like it. So, what does this poor sensitive developer want to be called then?
Well, since “fantastic handsome sexy beast web dev-rockstar” is probably out of the question, I’ll give you some more humble suggestions:
- Interface Developer
- The Interface guy
- Web Developer
- Design and interaction-coder
Is it just me hating that term? Or even caring at all about how one is presented to others? Or do you feel the same, but have some better names for this trade?


