Good thoughts here. I think the subject is something a lot of designers could stand to benefit from—knowledge is power after all (I also like that you took a realistic stance: "Hey we all have to pay our bills...").
– What's described in the article is 95% of the UX jobs
– UX Design generally aligns with product—design thinking is just design-led product strategy (which is 'design' proper, but repackaged to sidestep the common misconception of design being the 'visuals')
– I don't think a job description having HTML/CSS/JS is a death sentence. I don't believe all designers should code (I find it makes them scope down the imaginable because they're just thinking about the feasible) , but HTML and CSS are really easily understandable scripting languages (they require no programming logic and you won't often come across some kind of algorithmic demand to write logic). Knowing them is knowing how layouts work—which can only help you with composition.
– I've hired many designers and I can tell you: Designers are not the same. Some are more engineering-centric (one of my highest performers is a systems engineer—she measures EVERYTHING). Some are product-centric (visionary, research based, feeling). Some are business-centric (business model and market positioning are key ingredients to great design work). So different types of roles just offers our profession a diversity of choices. The trick for a designer looking for work is to know the options and choose a role that fits them.
The desire for HTML/CSS/JS knowledge is so that UX designers know how the web works right, so much of the web is forms and containers, if you know how they work and how to structure them you can propose more realistic solutions.
I don’t disagree w the logic (I even said it above too). But honestly I’ve never truly found truth in it. Designers that can prototype in HTML/CSS often have trouble with setting the right scope too. On my team the designer w no HTML skill delivers measured designs expertly w her squad. I’m beginning to wonder if it’s because we over estimate our ability to ‘peek behind the veil’ with HTML/CS when we should instead be focusing on HOW we communicate across design/dev professions. She does it well, so her stuff gets made with precision.
Food for though.
apparently this is another new grad with huge ego symptoms who's having a hard time to find a job straight out of disgraceful general assembly. just check out his website. the splash screen is his face with the title 'your leader'. under the products it's just his talks... and he has a fkcing job board on his personal page -_-
seriously, general assembly must be shut down for 'training' and releasing these useless people who couldn't able to get a proper BA.
edit. what's wrong if people are looking for designer who can code? do you suggest companies to hire crooks like you who can't even comprehend the development environment. I admit that the only good 'ux' designers I've met are the one's who can code or have very long experience on graphic design, definitely not clowns from weekend courses like that guy. bad job descriptions are not spesific to design -oh oh I'm sorry. Design and ux is a completely different stuff according to this guy. they should be only talking instead of working. hm...
Maybe... maybe not. But I don't see what ad-hominem (personal) attacks are doing for you here. Debate him on the issues of the article IMO—not looking to discredit him because you don't think he has the "right" education.
The truth is that engineers can do anything
I cringe at this statement... Usually, its time, money, and priorities that is stopping them. You can have a tech team burn 2 weeks for a feature that might push the needle a tad or out of scope. I rather hire a designer that can work with and communicate clearly with the engineering team.
Don't get me wrong, the engineering team frustrates me to no end at times. However, I try my best to find a middle ground. If you bring them early in the process, the more likely ideas will get build.