Published: Apr 18, 2015 by C.S. Rhymes
To some people, the differences in these two roles are obvious. A developer is the one that makes the code and the designer is the one that decides how it will look. But in my experience it is not as simple as it may appear.
Traditionally web designers would do a lot of their work in programs such as Illustrator or Photoshop, creating images of how they think the page should be laid out, working on elements such as navigation, font styles and colours. This is then handed over to the developer to make the page.
Previously, I would not have classed myself as a designer. I think this was mainly due to my lack of confidence in my design skills, thinking that no one would like my work. I would let someone else tell me how it should look.
When people ask what I do I tend to reply with the term web developer, as opposed to web designer. I’m not really sure why this is? Maybe I think it is easier to explain what I do. Maybe it’s because I think it sounds more technical. I think it’s because I have always classed myself as a programmer, the one that just concentrates on making things work and not worrying about how it looks. That can be done after it’s all working, right?
The more I learn about web development, the more I have begun to realise that how someone thinks a page works is just as important as how it actually works. If you have used a website a lot before then you know your way around it and you know it’s navigation method and it’s quirks. The first time you use a website, you have to learn how it works and how to navigate from one page to another.
This has made me think a lot more about the User Experience aspects of web development. You have to keep asking how can I make this easier to use, how can I make it more obvious and how can I make this quicker for the user.
So what is the difference between the roles?
Basically, I don’t think there should be two roles anymore. I think that web design is an essential skill for a developer and vice versa. User Experience and User Interface Design is now such a massive part of web development it all merges together.
Basically, I don’t think there should be two roles anymore.
This is an opportunity for people that used to class themselves as designers to be able to learn to code and gives the developers a chance to learn more about design and prototyping. This is a good thing.
The real winners are the general public, getting better designed and easier to use websites.
So the next time someone asks me what I do, I might call myself a ‘Full-Stack Developer’ as according to Creative Bloq:
“A full-stack developer typically means someone who is expected to be able to perform the roles of web designer, web developer and elements of UI and UX design too.”
The issue with Full-Stack developer is that it’s not particularly catchy. How about Web Experience Engineer & Designer or WEED for short?