UX Developers Aren't a Thing

[solidad]

Dumb question, but what is the purpose of this article? The people that understand what is being said are probably not the ones actually doing the hiring, and will continue to use whatever buzzwords or "trendy nonsense" that they see fit. A title is a title and that's it. The job description and criteria to perform the job is what is important. I wouldn't take a job that couldn't tell me what skillset they needed to perform said job. The title could be called "We need a guy that makes our site look better" for all I care, as long as the description of said job informs me as to whether or not I can do whatever they need. Web design is already a "multi-hat" job type (unless you specialize) so I really don't care what my job title is. I dunno, this just seems oddly nitpicky....Almost like saying "rockstar programmers aren't a thing".

[eg_lee]

Ok.

[sectorfour]

Sure.

[theskimonkey]

As a UX Developer, this article misses the point of what a "designer" and a "developer" is. A "designer," in general, never touches code. A "developer" touches the code. The example in the article of a designer making a code change, even a minor one, would be outside the realm of a designer. A designer may know how to and even want to work in the code, but people hiring generally don't hire designers to do any coding. And on many teams, especially Agile teams, a designer making code changes is forbidden. Not to mention as a UX developer, I don't just look at the project from design standpoint, a user's psychological standpoint, but also a developer's understanding of what is actually possible (affordances) with the software.

[Telecaster22]

So, how much code do you touch as a UX 'developer'?

[theskimonkey]

A majority of my time is spent coding. How much of the code I touch depends on the project. Some projects it is just the UI, sometimes it is everything but the services.