[dutchbrit]

I hate titles, sure, it does look more fancy. Besides, you can have frontend only applications written in javascript. Would that make me just a 'UI Developer'? I can go on and on, but just stick with a title that explains your skills the best. I can't stick a label on myself. I dabble in a lot of fields.

I don't disagree with all of your points however. People should just make up their own title that fit them best.

[zappan]

I'm afraid you're missing it a bit - just making only javascript applications is the reason to make a different distinction - some people are better at doing MVC, and they do it in the browser now; while some people are great in making great looking UIs, but not really digging into application architecture. And, of course, there are people doing both, being full-stack devs, but still they're usually more efficient in some areas than the others - I am such an example, still I know UI devs that are way more efficient and know neat tricks on the UI, as well as some great UI libraries to do their work faster (and usually better, relying on the know-how built into the lib) because they specialize in that.

Thanks for your comment regarding labeling, though... I agree that sometimes it's inappropriate, still sometimes it's useful to figure out the kind of work being done under such a label

[k__]

I'm an UI-developer, but I still have to think about software architecture, because we have a multi-tier System.

There is a data-gathering (tier-1) and -mutation (tier-2) backend and a HTTP-front-end to gather this data (tier-3).

And then there is the GUI (tier-4), which is an application itself, with the HTTP-frontend as backend.

The back-end developers work in tier-1/2 The front-end evelopers work in tier-3/4