re: Why Everyone Is Fighting About CSS/UX and JS VIEW POST

FULL DISCUSSION
 

I'm not web developer/engineer/designer etc... However, your post did pique my interest. Regarding the job title nomenclature and what that entails, I believe if everyone simply accepted that they are all "skilled tradespeople" and have the same goals in mind, then maybe you can move past that. It seems really silly to get caught up in a title like that.

Regarding stacks, that is not isolated to the web (As I'm sure everyone who reads this post are aware of.).

 

I completely agree. The specific title of “engineer” has been one of the most contested things about my post, and really I only defend it because of the implied “eww, design” attitude that some developers get.

You know what it remind me of? Did you watch that episode of the Office where Dwight was fighting about the difference in prestige between “Assistant Manager” and “Assistant to the Manager”?

 

lol I hadn't seen that episode. I'll make a note to check that out.

Usability and design in a lot of ways (in my opinion) adhere to the same principals as engineering. Each choice must go through the same rigor as any complex backend system.

Reminds of the "full-stack" thing from years past (That still a thing?).

 

Engineering in my country is a field that is disciplined by laws. You can't even call yourself an engineer if you don't pass a specific exam and graduate in engineering. They're also not inherently more worth than a designer, which everyone considers a bad word but a designer is simply someone who is trained in culture and not only a very specific tech.

 

I understand that in Canada and European countries you need a engineering certification to have the title. In that regard, I understand it. If a software engineer is writing software that monitors your heart rate, you want assurances that it will work and if something should go wrong, you can hold the organization or person accountable who created it. That's how it works here (US) for other engineering disciplines.

However, in the US this isn't the case. The term "software engineer" is thrown around a lot and it's in a way commingled with "developer" or "programmer". In some cases we say the word as to not offend the individual. Again reiterating that other engineering disciplines are required to be certified. Just not the software variety.

In light of all that, by me expressing that design follows the same kind of "rigor" as engineering does not mean that i'm taking a side in that regard (Seriously, I don't care. Call yourself whatever you want.). I was merely speaking to the kind of philosophies good UX/UI professionals do (In my experiences.). They are held accountable for the products that they produce at least on a organizational and product level.

Hope that explains my initial posts.

code of conduct - report abuse