Re:The Elephant in the Room: Web design work is drying up
by learc83 on Wednesday February 24, 2016 @05:04PM
(#11170603)
Traditionally web developer is a more broad term that covers front and back end work.
I agree that there is nothing wrong with evolving the term "front end developer" into "UI/UX engineer". My problem is that the OP is talking about replacing "web developer" with "UI/UX" engineer. Web developer traditionaly includes backend engineers who aren't only working on UI.
Re:The Elephant in the Room: Web design work is drying up
by cjcenizal on Wednesday February 24, 2016 @06:55PM
(#11171248)
I don't think "web developer" has been replaced by "UI/UX engineer". I would still draw the same distinction between the two that you're drawing. But I think demand for "front end developer" has lessened and demand for "UI/UX engineer" has increased.
Re:The Elephant in the Room: Web design work is drying up
by jameshart on Wednesday February 24, 2016 @06:30PM
(#11171106)
And back in the last century, 'webmaster' was the term that encompassed front end, back end, and web server administration work. Terms move rapidly in the web world, and as complexity grows, people become more specialized and less aware of details in other parts of the stack.
Re:The Elephant in the Room: Web design work is drying up
by learc83 on Wednesday February 24, 2016 @07:15PM
(#11171370)
All of what you said is true, yet none of it has anything to do with what I wrote. If we replaced the term webmasters with Content Engineers, and started calling designers/developers/server admins Content Engineers, you'd have a point.
Web developer is a broad term. UI/UX Engineer is a specific term. Yes many people specialize in frontend or backend, but both of them are still web developers. Calling both of them UI/UX Engineers is dumb.
1. a frontend, which is a Single Page App, shipped as a blob of JS;
2. a backend, which is a big fat set of services in random languages.
The people who create the frontend are traditionally thought of as web developers, but "UI/UX engineer" is perhaps closer: they're engineering a program, yes, but it's ultimately a program entirely to serve the purpose of being a nice UI/UX in front of an API.
I think the most on-target name for this role would probably be "client-app developer." The client happens to be web-based, but that doesn't much matter. It's still a client that consumes your service.