A collegue of mine mentioned a problem he was having when he told people he was a web developer. The problem is that he is a software engineer that happens to work with web technology, he doesn’t build “websites”, he builds web applications and I think this difference is lost on a lot of people. As it turns out, I have had exactly the same problem, I just couldn’t seem to put my finger on it.
It seems that every time I need to prove my abilities to some new company, some of the questions are just ludicrously simple, like how would you sort a list of items or how would you design a system of shapes in an object oriented fashion. I can only assume that these questions need to be asked because the people looking for a web development job, wander into interviews for software engineers.
I have always thought of myself as a web developer, it communicated to people what I did and the technologies that I worked with (how convienient!). Now, it seems that term has picked up an awful lot of extra baggage or, maybe it lost some weight. OR I just made the mistake of saying hey, I work with the Internets, I develop software on them, I must be a web developer!
It has become somewhat of a shock to me recently to meet some of the people I share the same title with. Of course, I don’t mean to bad mouth people who design/develop websites for people and call themselves web developers. Those people have just as much a right to use the term as I do (probably more so), it just happens that the projects that they want to work on, and the projects I want to work on are wildly different types of work. I would imaging employers and employees both have trouble finding which type of web developer they are looking for,
- Type B: designer/developers (Build, modify and apply themes for CMSs)
- Type C: spiders (I doubt there is much issue confusing this one with the other two, except maybe in Spiderman’s case)
However, I think I am going to go back to calling myself a software engineer.