News for hackers. Stuff that matters.
Re:The Elephant in the Room: Web design work is drying up by cjcenizal on Wednesday February 24, 2016 @02:09PM (#11169296)
I think there's a fundamental shift in the type of web-skills which are now in demand, due to a number of factors. Here's some things which come to mind:

- A "web designer" or "web developer" used to be a generalist who wrote HTML, CSS, and some jQuery. Now there's a demand for specialization: a UI/UX designer who can prototype, iterate quickly, and use real data if possible, and a UI/UX engineer who can develop large-scale apps with an eye towards security, performance, reusability, and maintainability.

- The need for the generalist web designer/developer seems supplanted by tools like Squarespace and Bootstrap, which make it easy to get acceptable results with fewer skills. It's the "commoditization of design".

- The need for specialized designers/engineers is spurred by a realization that good design can command a premium/competitive advantage (and that good design means iterating quickly and having a deep understanding of what makes fundamentally good UI and UX), and that the front-end benefits from sound engineering practices as much as the back-end, especially if you're building SPAs or large-scale apps with complex UXes.

- A lot of the design problems have been solved already. Questions such as when modals are appropriate, how to design forms effectively, what makes a good call-to-action, and how to structure IA effectively have been answered. Companies no longer need teams of people to work out answers to these questions, just one or two good leaders to evangelize the answers that are already established, and a team of UI engineers that can execute them well.

Re:The Elephant in the Room: Web design work is drying up by sixtypoundhound on Wednesday February 24, 2016 @03:07PM (#11169787)
You nailed it. A large fraction of the work effort which was traditionally branded as web-design has been repackaged into additional roles and/or automated and streamlined via tools.

In reality, 60% of my time is spent on web design, but this effort is repackaged into two broader job descriptions: UX developer (requires heavy Javascript code) and web marketer (requires knowledge of analytics, SEO technique, conversion optimization, and a dozen other skills). Plus my frameworks pick up a lot of the lower level details of setting up and managing a web-page.

Not seeing a shortage of work in those two spaces....

Re:The Elephant in the Room: Web design work is drying up by odonnellryan on Wednesday February 24, 2016 @05:10PM (#11170642)
Yeah. What is even web design these days? I consider myself pretty good at making a website look nice, but I don't design it in Photoshop.
Re:The Elephant in the Room: Web design work is drying up by hayksaakian on Wednesday February 24, 2016 @10:02PM (#11172076)
From my observations it's a matter of picking a nice wordpress theme and customizing it for your brand.
Re:The Elephant in the Room: Web design work is drying up by cgarvey on Thursday February 25, 2016 @01:48AM (#11172783)
How many of the websites you love to use are built on wordpress themes?
Re:The Elephant in the Room: Web design work is drying up by hayksaakian on Thursday February 25, 2016 @06:29PM (#11178703)
some large sites using wordpress

1. TechCrunch 2. The New Yorker 3. BBC America 4. The Official Star Wars Blog 5. Variety 6. Sony Music 7. MTV News 8. Beyonce 9. ebay Inc 10. PlayStation.Blog 11. Best Buy 12. Xerox 13. Bata 14. Quartz 15. ESPN Product Blog 16. Nokia Conversations 17. Ford Social 18. Fortune 19. Time Inc. 20. Facebook Newsroom 21. The New York Times Company 22. Marks & Spencer for Business 23. Google Ventures 24. Harvard Business Review Blogs 25. Larry King Liveblog 26. The Official Rackspace Blog 27. Philips DirectLife Coach Blog 28. ExpressJet Airlines 29. Inside BlackBerry 30. Rotary Means Business – Rotary Club 31. The Rolling Stones 32. The Walking Dead – AMC 33. The Mozilla Blog 34. The Wall Street Journal Law Blog 35. Dallas Mavericks 36. Wil Wheaton 37. Snoop Dogg 38. SAP News Center 39. Wolverine Worldwide 40. Reuters Blogs

Re:The Elephant in the Room: Web design work is drying up by cjmcqueen on Thursday February 25, 2016 @02:25AM (#11172898)
I can't say I "love" TechCrunch, but it is built on WordPress... Although, I see your point about generic themes.
Re:The Elephant in the Room: Web design work is drying up by ommunist on Thursday February 25, 2016 @05:20AM (#11173496)
Smashing Magazine, Techcrunch,... about 25% of them.
Re:The Elephant in the Room: Web design work is drying up by paulojreis on Thursday February 25, 2016 @03:24AM (#11173098)
As with all design, it's not about making it look nice.
Re:The Elephant in the Room: Web design work is drying up by odonnellryan on Thursday February 25, 2016 @08:36AM (#11174273)
That's true, but I think that's what a lot of people think it is.

I'm also a software dev. I wouldn't say, when designing code, that "I make the code look nice" though, I'd hope that's at least part of it.

However... when someone is looking for a "designer," while it does include UI/UX (again, whatever that is ;) ) I've found they strictly only want someone who is good at making pretty things in Photoshop.

Re:The Elephant in the Room: Web design work is drying up by nchelluri on Thursday February 25, 2016 @04:21AM (#11173291)
I think your post could do with some bullet points about what design is.
Re:The Elephant in the Room: Web design work is drying up by paulojreis on Thursday February 25, 2016 @05:13AM (#11173465)
You're right.

The process of making form follow function, maybe?

Re:The Elephant in the Room: Web design work is drying up by odonnellryan on Thursday February 25, 2016 @08:37AM (#11174280)
Definition of design: a plan or drawing produced to show the look and function or workings of a building, garment, or other object before it is built or made.

So, I guess "web designer" is very similar to "make it in Photoshop" and I should stop complaining ;)

Re:The Elephant in the Room: Web design work is drying up by paulojreis on Thursday February 25, 2016 @09:19AM (#11174524)
I'd say that definition defines the outcome of design, not design itself. I focused on the "process" deliberately, because most design work happens outside whatever tool you use to externalize your plan/vision.

It's reductive to conceive design as the design outcome, IMHO. If you have a guy doing all the UX work (alignment with business needs, research, gather data, analysis, IA, brand identity integration, etc.) and other guy which takes all this work and produces UI mock-ups in Photoshop, who did most design work?

Re:The Elephant in the Room: Web design work is drying up by rwhitman on Thursday February 25, 2016 @03:29AM (#11173117)
The point about generalists no longer having a place in the market is something that's becoming more and more apparent every day.

The web was crafted by generalists. People who could think about both technology and design at the same time were hugely valuable builders, and leveraged to rapidly build up the content and tools of web from nothing.

Looking back, it was the wild west. We generalists were the rough and tumble pioneers that swung an axe and moved boulders, dug for gold, founded towns from dirt.

But now, it's built. There's no more frontier left to explore. The roads are cleared, railroads built, the land claims are well established, the towns have paved streets and public services.

10 years ago we web generalists were calling ourselves designers or developers but now we're engineers, product consultants. There's no longer a mad scramble to get a vision onto the screen with a designer, develop a new product from nothing. It's all about engineering to remove the flaws of the rough work done by pioneers, carefully looking at what's been established and tuning it so that it lasts.

I think some of us chronic generalists need to find a new frontier. This is just no longer our place..

Re:The Elephant in the Room: Web design work is drying up by pbowyer on Thursday February 25, 2016 @03:56AM (#11173204)
Simon Wardley puts it very well in his Pioneers / Settlers / Town Planners model:

http://blog.gardeviance.org/2015/03/on-pioneers-settlers-tow...

If you spot that new frontier do share - it's what attracted me to the web.

Re:The Elephant in the Room: Web design work is drying up by thenomad on Thursday February 25, 2016 @06:42AM (#11173787)
VR is my current top pic for a likely new frontier.

It'll either bomb or it'll be huge, the equivalent of the introduction of the smartphone or greater.

Re:The Elephant in the Room: Web design work is drying up by swah on Thursday February 25, 2016 @10:13AM (#11174905)
I wonder if it will isolate people even more? Everyone is always buried on their cellphones these days...

Maybe people just accept to meet inside the Matrix... http://hypescience.com/wp-content/uploads/2016/02/12719113_1...

Re:The Elephant in the Room: Web design work is drying up by rwhitman on Thursday February 25, 2016 @03:22PM (#11177502)
How does one break into VR without a background in 3D gaming / CG?
Re:The Elephant in the Room: Web design work is drying up by cableshaft on Thursday February 25, 2016 @06:18PM (#11178640)
Learn how to make a 3D game when you can spare the time with some books and/or tutorials (Unity game engine I believe has plugins for certain VR systems). Make a simple game that works in VR (use Google Cardboard if you need something affordable).

Put it on your portfolio, and contact these companies and show how enthusiastic you are to enter the new VR frontier in your cover letter.

Unity doesn't require knowing how to program low level 3D graphics. You just need to understand how to import models (that you can find on their asset store), and some basics about 3D coordinate space and basic update/draw loops used in every game to move and rotate those objects over time.

You can go as deep as you want with it, but you could probably follow a tutorial on Unity and knock out something that proves you understand the basics in the span of a weekend.

Keep improving and adding new stuff onto your portfolio, maybe blog about what you've learned, and keep networking until someone wants to give you a shot.

That's basically how I broke into the game industry. It took time and passion, but I did it.

Re:The Elephant in the Room: Web design work is drying up by dba7dba on Friday February 26, 2016 @01:25AM (#11180092)
'game industry'. Whenever I hear that term, I shudder at the idea of working loong days and nights and weekends the industry seems to require.
Re:The Elephant in the Room: Web design work is drying up by cableshaft on Friday February 26, 2016 @09:30AM (#11181515)
I didn't include that bit, but yeah, I only lasted a few years in the industry myself before being burnt out. Now I'm back to making games as a hobby.
Re:The Elephant in the Room: Web design work is drying up by rwhitman on Friday February 26, 2016 @01:26AM (#11180093)
Fascinating. Never crossed my mind that this was an area I could break into. Thank you
Re:The Elephant in the Room: Web design work is drying up by rwhitman on Thursday February 25, 2016 @03:20PM (#11177492)
Thank you so much for that read.

The part about Pioneers of the past being burned at the stake I'll hold on to. That's a truth that hangs on today, albeit with less fire and more firing

Re:The Elephant in the Room: Web design work is drying up by patkai on Thursday February 25, 2016 @07:52AM (#11174041)
IoT
Re:The Elephant in the Room: Web design work is drying up by madaxe_again on Thursday February 25, 2016 @04:33AM (#11173331)
Well, I know where I want to go after the web, and am beginning to scheme - space - the final frontier.
Re:The Elephant in the Room: Web design work is drying up by ryanSrich on Wednesday February 24, 2016 @05:25PM (#11170732)
> "A lot of the design problems have been solved already. Questions such as when modals are appropriate, how to design forms effectively, what makes a good call-to-action, and how to structure IA effectively have been answered. Companies no longer need teams of people to work out answers to these questions, just one or two good leaders to evangelize the answers that are already established, and a team of UI engineers that can execute them well."

Perhaps I'm taking this the wrong way, but the tasks you listed there don't even begin to scratch the surface of existing design problems a UI designer will face on a daily basis.

EDIT: ex. Consider the design work that went into this product http://www.research.ibm.com/cognitive-computing/watson/watso...

Re:The Elephant in the Room: Web design work is drying up by mtrpcic on Wednesday February 24, 2016 @05:53PM (#11170905)
I think you two are saying the same things. The examples he provided are the problems that have already been solved, so you don't need teams of people to figure them out. Instead, you just need two pros who are excellent in specific areas, and "industry best practices" fills in the gaps. 10 years ago, there were no best practices, so this wasn't quite as possible.
Re:The Elephant in the Room: Web design work is drying up by burgessaccount on Wednesday February 24, 2016 @08:01PM (#11171632)
It seems to also depend very much on who the website is for. The reality is that many organizations (small businesses basic organizations restaurants schools nonprofits etc.) need sites that do basic, routine things, in which case, the hard problems are solved, and good templates are available. In that case, having an in-house person who understands the company's needs is better than having a sophisticated specialist. It seems like, as the # of websites has increased, one would have expected the demand for web designers to increase proportionately, but it hasn't, because the orgs with the most complex site needs were the first to build.
Re:The Elephant in the Room: Web design work is drying up by ryanSrich on Wednesday February 24, 2016 @09:09PM (#11171907)
Website is also a minomer now more than ever. If it's online and you access it via the web is it a website? A product? A web product? A web app? SaaS app? Is it mobile? Is a webkit app a website? Is a website wrapped in a mobile browser ported to a phone a website?

One could certainly argue in either direction for all of those questions. The skills are all very similar, the technologies are mostly the same (foundationally).

I don't think work is drying up nor demand going down. I think designers are more important now more than ever, they just might not be traditional web designers.

Re:The Elephant in the Room: Web design work is drying up by theoh on Wednesday February 24, 2016 @06:18PM (#11171040)
Looking at WatsonPaths, I'd say that it it's an "expert system" (very old idea) with one UX gimmick added, the path visualization of Watson's best guess at each stage. It's a totally appropriate application of that type of infographic, but IMO the insight that it could aid visualization to use it is a high level concept. I'd be curious to know whether the idea led to the WatsonPaths project, or if it was discovered in the course of an exploratory initiative (presumably with another name). What it definitely isn't is UX design "as usual". (That kind of diagram is not a new invention: http://www.economist.com/blogs/graphicdetail/2015/05/daily-c... )
Re:The Elephant in the Room: Web design work is drying up by snegu on Wednesday February 24, 2016 @07:46PM (#11171561)
Those actually are the design problems a UX designer working on a company's marketing site will face on a daily basis. That's why all the interesting UX work has moved away from "web design," as discussed in the article, into designing the types of tools you link to.
Re:The Elephant in the Room: Web design work is drying up by ryanSrich on Thursday February 25, 2016 @04:09PM (#11177811)
But the tool I linked to was just a prototype. The actual product will be accessed via the web.
Re:The Elephant in the Room: Web design work is drying up by jamiesonbecker on Thursday February 25, 2016 @12:17AM (#11172531)
The web designers who designed the WatsonPaths diagrams that were probably already intimately familiar with the same type of diagram in Google Analytics:

http://www.webs9.com/wp-content/uploads/2012/10/Social_visit...

Re:The Elephant in the Room: Web design work is drying up by learc83 on Wednesday February 24, 2016 @02:59PM (#11169721)
>a UI/UX engineer who can develop large-scale apps with an eye towards security, performance, reusability, and maintainability.

I've never head this referred to as a UI/UX engineer. You seem to have just described a web developer. If you're developing "large-scale apps" then you're definitely doing more than UI/UX, so why call it UI/UX engineering?

Re:The Elephant in the Room: Web design work is drying up by joshuacc on Wednesday February 24, 2016 @03:19PM (#11169905)
At my company we call this role "UI Development." A UI developer is expected to be good at all aspects of development that are required to implement the user interface, including HTML, CSS, JavaScript, and server-side templating languages.

The JavaScript skills in question include the ability to write clean code, write unit tests and use client-side frameworks like Angular or React.

Having an eye for design and usability is a plus, but not the focus.

Re:The Elephant in the Room: Web design work is drying up by EC1 on Wednesday February 24, 2016 @06:27PM (#11171094)
Actually you just described a front-end developer, which I guess you call "UI Development". Which is really a scam by companies to overwork one individual with two jobs. UI and actual development should remain separate as there is a seriously massive workload for each. These "full stack" roles only make sense extremely early on in the company or on a greenfield project, anything where iteration and field testing take priority by virtue of simplicity as a result of time.
Re:The Elephant in the Room: Web design work is drying up by dclowd9901 on Wednesday February 24, 2016 @05:31PM (#11170775)
Don't forget front end build pipelines and some server code to implement or retool APIs. Front end engineers need to know just about everything all the way back to the db
Re:The Elephant in the Room: Web design work is drying up by derefr on Wednesday February 24, 2016 @04:21PM (#11170331)
Think of it like this. Something like Gmail.com is really two things:

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.

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.

Re:The Elephant in the Room: Web design work is drying up by stevepaulo on Wednesday February 24, 2016 @04:28PM (#11170364)
Google calls us this. Last year the position of "Web Developer" was renamed to "UX Engineer".
Re:The Elephant in the Room: Web design work is drying up by highstep on Wednesday February 24, 2016 @06:05PM (#11170971)
Does anyone else feel uncomfortable with calling themselves an engineer without going to school to become a true engineer?
Re:The Elephant in the Room: Web design work is drying up by kylehotchkiss on Wednesday February 24, 2016 @08:52PM (#11171835)
Absolutely. I went to school with (and am close friends) with many engineers. They worked very hard on their studies while I sorta goofed off and didn't finish school. I respect their dedication to process, standards, not reinventing the wheel when not needed, and commitment to projects that last an entire career. Their tasks include making things work better for people in general and not just a segmented community. It's also good to remember "Engineers" make decisions that other people's lives depend on.

I am proud to call myself a programmer or a web developer. Our work is hard, it's dynamic, and it has the potential to impact many lives. But we should be sensitive to the engineering community as lives depend on their work and calculations not falling apart.

Re:The Elephant in the Room: Web design work is drying up by hilbertseries on Thursday February 25, 2016 @12:07AM (#11172499)
It varies. Some developers right the software for embedded devices that power airplanes or medical machinery. Some engineers design speakers.
Re:The Elephant in the Room: Web design work is drying up by nchelluri on Thursday February 25, 2016 @04:25AM (#11173304)
I agree with both of you, and feel pretty strongly (without any real concrete evidence, but with lots of anecdotal personal experience to back it up) that the vast majority of pro coders are software developers but by no means software engineers. I personally put "Software Developer" on my resume/linkedin for all of my dev jobs, regardless of what my employer/client calls the position.

On the whole engineering vs developing thing I think that dev is still in its infancy. Professional certs that are really meaningful and indicate some level of knowledge on various dev subjects would be a good baseline in the future, IMO. In Canada, to be a P.Eng. (https://en.wikipedia.org/wiki/Regulation_and_licensure_in_en...) one must, by law, be licensed.

From that link:

> The regulation and licensing of engineers are accomplished through a self-governing body that is given the power to license and discipline professional engineers, as well as regulate the practice of the professional engineers...

> A self-governing body's prime purpose is to protect the public.

Re:The Elephant in the Room: Web design work is drying up by lazaroclapp on Wednesday February 24, 2016 @11:19PM (#11172362)
The problem is that the line is not as clear as you'd think. Is someone who makes electronic circuits, but is mostly self-taught, an engineer? How about for software? There is usually very little difference between the best self-taught programmers and the best engineering-school taught ones, up an including knowledge of calculus, algorithmic complexity analysis, ML/stats, etc. Finally, there are people like me who did a bachelors in CS inside a school of sciences, rather than a school of engineering, is 'Software Engineer' justified in the later case, but not the former? Why?

Also, this discussion is a bit like asking why you can be a Data "Scientist" without a Ph.D. and without peer-reviewed publications. In reality, most people understand the difference between a scientist working in neurobiology or particle physics, and a data scientist working on ads (a competent data scientist working on a private non-profit in epidemiology might actually be harder to classify, though). So, same goes as to the difference between a civil engineer and a software engineer.

Edit: If anything, I know a few UX designers that reject the engineer label, but only because it makes the process sound more mechanical compared to designer (in my understanding, both are about discovering and satisfying constrains, but constrains are more strongly defined and more externally enforced in engineering than design, even for software).

Re:The Elephant in the Room: Web design work is drying up by notalaser on Thursday February 25, 2016 @04:44AM (#11173362)
In certain parts of the world, including much of Europe, the question is less ambiguous than it seems. There are countries where this, for instance, has a very clear answer:

> Is someone who makes electronic circuits, but is mostly self-taught, an engineer?

If he's accredited by that country's authority on the matter (e.g. the Engineering Council in the UK), then yes. If not, no.

Around here, you're only allowed to call yourself an engineer if you have a degree from a technical university.

Sure, the company can give you any title they want (I mean, if they're allowed to give obnoxious titles like Senior JavaScript Ninja or whatever, surely they can call someone an engineer, too), but from a legal standpoint, that's null, with all the consequences that follow (e.g. legal documents that require an engineer's signature have to be signed by someone that the state agrees is an engineer, regardless of what the company thinks).

Edit: FWIW, while I'm legally allowed to claim that glorious title (my diploma says "Instrumentation Engineering"), I tend to avoid it, too. My job has always been to program computers, and if I'll be able to do that until I retire, I will. Consequently, I see no reason to call myself anything other than a programmer. My employers disagree for paperwork reasons, so the paperwork they do says otherwise, but "programmer" is what I want everyone to call me. There is very little of true value to be found in a name; people who chase the title of engineer, rather than the engineering education, are missing the point.

Re:The Elephant in the Room: Web design work is drying up by nchelluri on Thursday February 25, 2016 @04:38AM (#11173350)
I like the way you've stated this. While in general I am not fond of arguing semantics and don't often think it's worthwhile, in this case I would say it's warranted.

When I think of "engineer", I think of P.Eng., and the licensing/accreditation that goes along with it has useful connotations to it. So I'd say while some of us devs might be doing engineering type of work, and may even be eligible for something like an P.Eng. license in their place of residence, they simply are not engineers, because they are not licensed.

On the other side of that coin, I don't believe there is ever such a hard-and-fast rule that is applied to the word "scientist". As such, I don't believe that Ph.D. or getting published is required - what's required is instead to be someone who practices science.

Re:The Elephant in the Room: Web design work is drying up by learc83 on Wednesday February 24, 2016 @07:23PM (#11171437)
That ship has sailed. Engineer has been genericized. Some countries still have laws regulating who can use the term, but in most places there is a difference between engineer, and something like Professional Engineer (which requires licensing).
Re:The Elephant in the Room: Web design work is drying up by ojbyrne on Wednesday February 24, 2016 @09:56PM (#11172054)
My father is a "true" engineer. He has said to me that the amount of education I have and work I have done would make it easy to be certified as a P.E.
Re:The Elephant in the Room: Web design work is drying up by empath75 on Wednesday February 24, 2016 @08:10PM (#11171671)
I've been a voip engineer, a network engineer, a software engineer and a devops engineer. I've never taken a CS class in my life.
Re:The Elephant in the Room: Web design work is drying up by NotSammyHagar on Friday February 26, 2016 @06:19PM (#11185031)
I don't want to be mean, but I guess this is - jobs that have certifications are not often engineering in the software world. Such as the oldtime way to get big bucks "certified netware engineer", oracle pooh-bah certified admin.

One day there will no doubt be real engineering accrediations, like peng for software, but we aren't there today.

Re:The Elephant in the Room: Web design work is drying up by Scramblejams on Thursday February 25, 2016 @12:47AM (#11172619)
Yes. I went to school to become an aerospace engineer, worked in that field for a while and recently switched to doing game development. Yet even though the title I was given when I was hired at my present job includes the word "engineer," I'm thoroughly uncomfortable using it.
Re:The Elephant in the Room: Web design work is drying up by ionised on Thursday February 25, 2016 @04:36AM (#11173344)
It's generally frowned upon in the UK, where an engineer must be accredited and chartered with the Engineering Council. Software development is considered a very immature discipline that is not yet subject to the same regulation and strict principles that civil engineering for example is.

I can't say I've ever seen dev jobs advertised as 'software engineer' positions here before. It's always 'software developer'.

Re:The Elephant in the Room: Web design work is drying up by radley on Wednesday February 24, 2016 @07:08PM (#11171317)
You don't need a degree to be called a coder.

Engineer simply means it's more code than Photoshop.

I prefer UI Developer.

Re:The Elephant in the Room: Web design work is drying up by bcoates on Thursday February 25, 2016 @01:01AM (#11172647)
Nah. If you're going to be pedantic about traditional definitions you get no credit for half measures, and engineering being an academic discipline as opposed to a generic term for an occupation/skillset is a relative novelty.
Re:The Elephant in the Room: Web design work is drying up by _ao789 on Wednesday February 24, 2016 @06:16PM (#11171026)
I completely agree. Its like someone carrying a board up a flight of stairs and calling themselves an engineer. Did you get an typical engineering degree for it? Exactly!
Re:The Elephant in the Room: Web design work is drying up by ddebernardy on Wednesday February 24, 2016 @06:25PM (#11171088)
Meh, in France some companies call cleaning ladies "surface engineers" so we're vaccinated. Sign of the times. :-)
Re:The Elephant in the Room: Web design work is drying up by batmansmk on Wednesday February 24, 2016 @08:20PM (#11171711)
It is untrue, they are called "surface technicians". In France engineer is a regulated title like MD or PHD here in USA.
Re:The Elephant in the Room: Web design work is drying up by wott on Wednesday February 24, 2016 @08:20PM (#11171713)
You meant "surface technician", did you not?
Re:The Elephant in the Room: Web design work is drying up by _ao789 on Wednesday February 24, 2016 @06:27PM (#11171096)
I rest my case
Re:The Elephant in the Room: Web design work is drying up by highstep on Wednesday February 24, 2016 @06:42PM (#11171170)
I wasn't trying to dimension the challenge and skills needed to be a developer. I'm more so questioning the use a label which traditionally has a certification process attached to it.
Re:The Elephant in the Room: Web design work is drying up by 91bananas on Wednesday February 24, 2016 @11:06PM (#11172324)
No. Engineering is weighing costs, benefits, and risks while solving a specific problem given those parameters.
Re:The Elephant in the Room: Web design work is drying up by Tepix on Thursday February 25, 2016 @04:27AM (#11173311)
In Germany, the term "Ingenieur" is still protected so you don't even have that option.
Re:The Elephant in the Room: Web design work is drying up by stickfigure on Thursday February 25, 2016 @02:19AM (#11172879)
My CS degree is from the College of Engineering at my university (Cal Poly SLO). So, no.
Re:The Elephant in the Room: Web design work is drying up by gnarbarian on Wednesday February 24, 2016 @09:07PM (#11171897)
I agree. That's a front-end programmer. A modern UI/UX designer's realm extends to HTML and CSS. The more JS they know the better but is not necessary.
Re:The Elephant in the Room: Web design work is drying up by baddox on Wednesday February 24, 2016 @04:48PM (#11170507)
Well a web app is a user interface. Obviously there are backend components to most web apps, but any of the client-side work can still reasonably be referred to as UI work. You just need to specify between UI designer and UI engineer.
Re:The Elephant in the Room: Web design work is drying up by learc83 on Wednesday February 24, 2016 @05:07PM (#11170626)
Yeah and using UI Engineer as an alias for frontend developer is fine. But the term "web developer" is a more broad term that covers front and back end work, so I think it's a bit weird to start referring to all web developers as UI engineers.
Re:The Elephant in the Room: Web design work is drying up by tootie on Wednesday February 24, 2016 @03:03PM (#11169750)
Yeah, the middle is hollowing out. You can get a decent design for next to nothing with a WP template or SquareSpace and the cost of gettting something significantly better is to pay millions to a top-tier design agency. The middle ground is shrinking but the top and bottom seem to be growing stronger than ever.
Re:The Elephant in the Room: Web design work is drying up by j_lev on Wednesday February 24, 2016 @03:27PM (#11169973)
Agree. Lots of money still being thrown at Drupal agencies.
Re:The Elephant in the Room: Web design work is drying up by mschuster91 on Wednesday February 24, 2016 @04:04PM (#11170210)
Drupal at least provides you with a fast prototyping experience. Data fields for everything, and connectors to all kinds of external services, validated in some cases by years of production grade usage. Caching, databases, clustering, high-availability... All solved and mature.

The only thing you don't get for free with Drupal is a backend which you can speak to if you're deciding to go the SPA route later on.

Which, in my personal opinion, is a pretty stupid trend anyway. SPAs tend to grow to Java Enterprise levels of complexity very very fast, and things break All. The. Time. Not to mention you're putting huge amounts of work to the frontend, where you virtually cannot account for cross-browser behavior, people with multiple-year-old browsers... and people with devices older than two years!

Leave a Drupal project idle and unmaintained for a year, and you'll be able to pick up where you left it. Good luck doing the same with an AngularJS SPA - you might get away if you used npm shrinkwrap when you left, but the first npm update WILL kill your code with a billion possible places to fix.

Drupal is mature, and maturity is something that the entire Javascript development and tooling community is missing unless you stick to plain jQuery.

Stability and reliability IS a thing, especially in enterprise.

Go the hipster way when your target audience is hipsters, go the proven, old-school way when your target audience is enterprise.

edit: ad maturity of Drupal and support... D6 got released in 2008-Q1 and support ended in 2016-Q1. That's EIGHT YEARS of continuous support and security fixes, and I expect similar if not better support timeframes for D7.

Good luck finding a Backbone.js or Ember.js (and maybe even AngularJS) developer in four years from now; not to mention that during the entire D6/7 lifetime backwards-compatibility-breaking changes were a rarity in Drupal when all of the mentioned JS frameworks have had more than their fair share of clusterfucks stemming from bad design. Or just the tooling environment, breaking changes everywhere and (gut feeling) every month there's a new tool to learn or best practices revamped.

Wonder why PHP, server-side rendering and SQL is so prevalent? You can rely on buying a solution and having support and developers even in multiple years from now. Enterprise doesn't want ever-changing piles of crap layered in more piles of crap, enterprise wants stability and maintainability. And enterprise is where the money is, not some SV startup only surviving on VC or with 90% of its customers startups only surviving on VC.

Re:The Elephant in the Room: Web design work is drying up by lmm on Wednesday February 24, 2016 @06:15PM (#11171025)
I have a turbogears app from 2008 that I still occasionally maintain. It's not officially supported, but it works, and I find Python to be nicer than PHP by enough to be worthwhile. I wouldn't use Javascript because it's awful, but if a small, immature framework suits your needs I wouldn't avoid it just because it's small/immature. Either your app won't be terribly important, or it will be; in either case you're sorted.

If you want to ever have a safe upgrade path that doesn't involve months of testing then you absolutely need a type system, IMO. The only framework I've felt completely safe doing major upgrades on is Wicket - which, not coincidentally, is the only framework I've ever known to make extensive use of final classes and final methods (Java), to enforce that it's only possible to use it in supported ways.

Re:The Elephant in the Room: Web design work is drying up by UK-AL on Wednesday February 24, 2016 @04:47PM (#11170504)
Angular SPA applications ALWAYS seem really buggy for me. Freezes, and spinners that never go away and you have to refresh etc

Maybe I just have bad luck.

Re:The Elephant in the Room: Web design work is drying up by wmil on Wednesday February 24, 2016 @10:15PM (#11172127)
Javascript SPA applications get less respect from business owners than they deserve.

People see JS and throw their JQuery & some CSS developers at it. Or they use their backend PHP devs who've never written code that runs for longer than one request.

Either way you end up with code written by people who don't understand some of the fundamentals of UI programming.

Angular gets the worst of it because it's the most popular framework. It's exacerbated by the fact that Angular doesn't offer suggestions for a lot of common problems.

Re:The Elephant in the Room: Web design work is drying up by gaius on Thursday February 25, 2016 @03:15AM (#11173064)
Angular is probably the bees knees if you are a Google employee but it makes little sense for anyone outside to bet the farm on it.
Re:The Elephant in the Room: Web design work is drying up by ihsw on Thursday February 25, 2016 @12:30AM (#11172569)
I live and breathe Angular SPA applications -- the vast majority of developers that work with it cannot comprehend a well-designed and usable Angular application.

Proper error handling, sane state management, and keeping the codepaths short and easily grok'd is very difficult with Angular -- especially for larger applications. This results in blackholes where users find themselves in strange spots that are inescapable other than a full page refresh.

These are either developers dipping their toe into the front end after living in the back end of things their whole career, jQuery dudes hastily breaking into SPA development to stay afloat in an environment the submitted article exactly mentions, or simply lazy developers that couldn't be bothered due to tight deadlines/budget/whatever.

Re:The Elephant in the Room: Web design work is drying up by wwweston on Thursday February 25, 2016 @01:11AM (#11172678)
Angular is popular enough that someone who could distill a reasonable set of concepts and practices for working with it could probably reap some significant rewards in the education/training marketplace.

But if proper error handling, sane state management, and keeping codepaths short are actually "very difficult with Angular," maybe it's not the comprehension powers of the developers using it that are falling short.

A framework should be actively making those things easy.

Re:The Elephant in the Room: Web design work is drying up by ihsw on Thursday February 25, 2016 @02:25AM (#11172901)
That is correct, Angular leaves a lot to be desired. The tooling is just not there and the developer is usually left to do due diligence on their own.

React/JSX and TypeScript are a response to this and it's fair bit more pleasant when either of them are involved.

Re:The Elephant in the Room: Web design work is drying up by rimantas on Thursday February 25, 2016 @01:37AM (#11172749)
I'd say it tells more about Angular than about developers.
Re:The Elephant in the Room: Web design work is drying up by manigandham on Sunday February 28, 2016 @04:26AM (#11190444)
Exactly. Server-side rendering is incredibly fast with modern browsers which makes a bunch of SPA sites completely infuriating. There are a few things that make sense like little button actions using AJAX but most of the page should just stay as a normal HTTP HTML request.
Re:The Elephant in the Room: Web design work is drying up by _ao789 on Wednesday February 24, 2016 @06:19PM (#11171046)
Or maybe you should not use IE5 for Mac to Dev in. Haha
Re:The Elephant in the Room: Web design work is drying up by sciurus on Wednesday February 24, 2016 @04:56PM (#11170548)
Leave a Drupal project idle and unmaintained for a year, and a new, non-backwards-compatible Druoal version has been released and you'll need to rewrite everything.

https://www.drupal.org/node/2613652

Re:The Elephant in the Room: Web design work is drying up by dack on Wednesday February 24, 2016 @05:15PM (#11170669)
I don't have experience with Drupal, but it says "plan for periodic upgrades of their project to the latest major release (every 6 years or so)". So, even if a new release comes out, you have _literally several years_ to decide when to make a switch. For perspective, Backbone.js was released 5 years ago!
Re:The Elephant in the Room: Web design work is drying up by mschuster91 on Wednesday February 24, 2016 @05:17PM (#11170686)
But the "old" major version will still be supported for a very long time frame. In the case of D6, it was supported over five years after the release of D7.
Re:The Elephant in the Room: Web design work is drying up by girvo on Wednesday February 24, 2016 @05:18PM (#11170694)
And this is not a theoretical: I've made a lot of money having to fix exactly that. Not very fun work, but definitely paid the bills.
Re:The Elephant in the Room: Web design work is drying up by 91bananas on Wednesday February 24, 2016 @11:15PM (#11172345)
Just coming here to give Backbone.js some credit. It is one of the most mature of the frontend frameworks, because it does almost nothing. It's what I'd call feature complete, its core probably will not change or grow much from here (in a good way). jQuery and Underscore back it, which also aren't changing or going anywhere. And as another commenter point out, it's 5 years old already, still in production all over the place.
Re:The Elephant in the Room: Web design work is drying up by btdiehr on Wednesday February 24, 2016 @04:51PM (#11170527)
What do you suppose you should do when people start demanding interactive features and capabilities that can only be done client side? For a lot of us the alternative of doing things on the server is a significantly worse UX.
Re:The Elephant in the Room: Web design work is drying up by mschuster91 on Wednesday February 24, 2016 @05:20PM (#11170704)
> What do you suppose you should do when people start demanding interactive features and capabilities that can only be done client side

You are free to use jQuery in your theme (aka frontend code), or D3 for visualization, or any other JS stuff you may need. On a private project, I'm using a current jQuery, D3, and SCSS and it works quite fine for me.

The only thing in D7 that can be a major PITA is proper multi-language support, because it's a bit sparsely documented.

Re:The Elephant in the Room: Web design work is drying up by eitally on Wednesday February 24, 2016 @02:32PM (#11169504)
I agree 100%. What this also means is that, because of these micro-domain specializations, unless a founder has either a lot of time or a lot of money, what they end up building is (usually, if the market opportunity is in the multi-billions) an advanced functional prototype wealthier companies can look at as bellwether to judge the scalable profitability they could generate through acquisition. There's still enormous space for web-based SMBs, but that's not what most people think of when they think "startup."
Re:The Elephant in the Room: Web design work is drying up by theseatoms on Wednesday February 24, 2016 @02:34PM (#11169520)
Pardon my ignorance. What's an SMB?
Re:The Elephant in the Room: Web design work is drying up by krisdol on Wednesday February 24, 2016 @03:14PM (#11169869)
Super Mario Brothers
Re:The Elephant in the Room: Web design work is drying up by jdminhbg on Wednesday February 24, 2016 @02:35PM (#11169541)
Small/Medium Business, usually.
Re:The Elephant in the Room: Web design work is drying up by scolson on Wednesday February 24, 2016 @02:35PM (#11169542)
Small/Medium Business
Re:The Elephant in the Room: Web design work is drying up by rectang on Wednesday February 24, 2016 @04:59PM (#11170576)
A Samba mount.
Re:The Elephant in the Room: Web design work is drying up by gnarbarian on Wednesday February 24, 2016 @09:43PM (#11172019)
Funny to see this downvoted on "hacker news". I think this site is long over due for a title change.
Re:The Elephant in the Room: Web design work is drying up by aws_ls on Thursday February 25, 2016 @05:19AM (#11173491)
So Many Bloated (apps)
Re:The Elephant in the Room: Web design work is drying up by junto on Wednesday February 24, 2016 @06:24PM (#11171082)
For small companies it is simple enough these days to have someone install WordPress, buy a theme that looks pretty good for $18 USD and you're good to go.

It might be a buggy insecure platform, but for non-tech savvy users it's brilliant. It doesn't make financial sense anymore to develop custom themes and designs from scratch. Large corps with their own branding is a different kettle of fish, but have fun trying to get on their preferred supplier list when you are a four person design agency.

Developing a one off, responsive, standards compliant website, that lookd good too, is expensive and clients don't want to pay for it.

Re:The Elephant in the Room: Web design work is drying up by busterarm on Wednesday February 24, 2016 @06:45PM (#11171192)
Mid-sized companies too.

We have a large content team and use WordPress across our company (several dozen websites) because it gets the job done for that content team. Our sites are ultimately just landing pages for ads and feed into our sales team as leads.

With our small 3-4 person devteam, we make our own themes and build into our WordPress sites all of the features that you'd want to host a site that's just content and a pipeline into our CRM (lots of handrolled plugins, custom functionality). We use modern ops practices (shoutouts to Pantheon for being a forward-looking PHP host) and write great code on a platform that's honestly not used to it. Some of the most interesting work that I've ever done.

As our team grows and our tools get more robust, we may explore using Wordpress to generate static pages for better performance. We also use other tools (Laravel, Rails, Node) when it makes sense to. Seriously though with good ops practices and developers who aren't lazy running the show, Wordpress can be a fantastic platform. This is absolutely some of the most interesting work that I've ever done.

WordPress runs 1/4 of the internet and not because 1/4 of the internet is cheap (though WordPress and PHP in general have fit that niche for a long time) - it's because training content authors to use custom/other tools costs money.

Re:The Elephant in the Room: Web design work is drying up by toxican on Thursday February 25, 2016 @08:26AM (#11174201)
I work in a small city in Maryland, so I'm not very concerned or familiar with the going ons in major cities. But for us at least, we've seen that when the companies go for the $18 WP theme, they usually come to us when they hit a point where they can't figure out how to expand the site and have us either step in or start over. Same with all of those shitty "build your own site" services. People will inevitably get frustrated with the limitations and want more, and that's when we step in. But then again, we don't have any shortage of people who want a fully custom/responsive website built from the ground up. And there's also a real sense of community here where a lot of small business owners would rather pay a local company to do it than pay out the ass for someone in DC/Baltimore to do it or deal with a faceless online service like Squarspace.
Re:The Elephant in the Room: Web design work is drying up by gnarbarian on Wednesday February 24, 2016 @09:03PM (#11171879)
Some 'pure' design jobs may be drying up but there is plenty of work in the front-end developer space. When work becomes thin designers should focus on Sharpening their JS skills and they will find plenty of work.

When someone is bemoaning the lack of work available I suspect the real problem is their inflexibility or technical stagnation. This is especially apparent when a novice roped in from the mail room can out-compete them and eat their lunch. The problem is the designer's skillset, not the industry trend.

The following anecdote is from my perspective as a Sr. Programmer. I've worked with many great designers over the last 10 years and this is an example of my worst experience working with a 'pure' one.

About 4 years ago I once worked with a designer who refused to break up a 60 meg psd file into separate elements I could use for buttons/background etc. I don't even have Photoshop. Her argument was she didn't know which layers/elements should be separated. She gave this to me the day before I had to have the site in prod. So I fired up gimp saw that it had 500 layers and just exported it to a jpg and used javascript imagemaps for the buttons just to get it out in time. This is after a week of work on another site they changed their mind on. I ultimately didn't get paid for any of my work and it was the last time I freelanced.

Primadonnas who do not put in any effort into learning basic technical skills to maximize their effectiveness can take a hike.

I've worked with great designers who were excited about the technical aspects of their craft. They understood that knowing what's possible makes them a better designer. Even when their graphic design degree did not provide them with any CSS training they quickly adapted because nobody has time to pass something back and forth moving elements around a few pixels at a time. I've seen more than one end up as great front end programmers and UX/UI designers. Even the ones who never quite got JS but embraced CSS were a great resource to have and made our sites look great. These are the kinds of people who make projects fun.

If jobs for people who consider CSS "beneath them" are drying up I say good riddance. Nobody has time for the overhead entailed from having programmers move elements around back and forth a few pixels at a time to please the designer who can't be bothered to learn valuable skills of their own trade.

The rule in technology has always been "Adapt or Perish" nobody bemoans the loss of COBOL jobs today for the same reasons people don't know what a "Printer's devil" is.

Re:The Elephant in the Room: Web design work is drying up by zaphar on Wednesday February 24, 2016 @09:34PM (#11171986)
Nowhere in that article was there any indication that the web designers were people who considered CSS "beneath them". 4 years ago you had a bad experience and now you are projecting it onto an article that is only related due to the use of one word, "designer".

The article was about a move to in-house design instead of agency/freelancer work.

Re:The Elephant in the Room: Web design work is drying up by gnarbarian on Wednesday February 24, 2016 @10:08PM (#11172099)
I clarified my comment a bit. The type of designer from my anecdote is becoming less and less common while simultaneously there is far more front end work available and designers who are willing to step up to the task.

So when someone is bemoaning the lack of work available I suspect the real problem is their inflexibility or technical stagnation. This is especially apparent when a novice roped in from the mail room can out-compete them and eat their lunch. The problem is the designer's skillset, not the industry trend.

Re:The Elephant in the Room: Web design work is drying up by flomo on Wednesday February 24, 2016 @11:04PM (#11172315)
Agree with your gist completely. I’ve worked in the agency world, and there’s loads of “designers” out there who come primarily from a print background and only have a vague clue how the web medium actually functions. They often try to do something unique or interesting, but the result ends up just being weird or not at all best-practice. (“Lets put the menus on the bottom of the page. Eureka!”) Plus, the client ends up with a website that was designed to be printed out on 8.5x11 sheets of paper. I’m sure a lot of companies have gone through this experience and decided it was a massive ripoff compared to buying a $15 wordpress template and hiring a freelancer to update the content.

Of course, I’ve worked with many incredible web designers as well, and it’s definitely worth it for major brands to have a good design team. But that whole middle-lower-end market is probably just disappearing.

Re:The Elephant in the Room: Web design work is drying up by gnarbarian on Thursday February 25, 2016 @02:14AM (#11172859)
That is definitely the most aggravating thing from both a user and developer perspective. Naive people pushing kitschy ideas caused us to have 100% flash, unlinkable and unindexable websites for quite a while and didn't really get eliminated until mobile killed flash and HTML5 CSS and JS caught up to all the glitzy crap.

And we still see people trying to 'fix' the expected behavior of things like the scrollbar. Stuff like that is a huge waste of time on something that actually hurts the user experience and almost always breaks mobile or cross browser compatibility.

Many of these people have the wrong goal entirely because they think visually standing out is the most important thing. In print that makes sense, because you're trying to capture their attention while they desperately try to ignore your advertisement. On a website you already have their attention because they came to your website. And here's the Key, they came to your website to accomplish something, the designer ought to be trying to help the user reach that goal as effortlessly as possible. It's a bad idea for login links and fields to be anywhere but the top right. You put the cash registers near the exit of your store, Hiding them is a bad idea. Other funny analogies:

Why put those boring gender signs on the bathrooms doesn't everyone do that? It clutters up the doors and doesn't fit with our minimalist design language. Also, if we do that then they won't look like any of the other doors in our store.

We want our customers to feel like they can share everything with us so we removed all the bathroom doors and partitions between toilets. It'll even save you material costs!

Wheelchair access ramps are ugly, we don't need them.

I think an escalator should speed up and slow down depending on how fast someone is walking up. (scrollbar overrides)

I think having signs that announce the products in a particular isle makes the store too cluttered and busy, If we make them wander around aimlessly for the product they are looking for they will see more of our store and end up buying things they otherwise wouldn't have.

Just to clarify, I think standing out is great but not when it comes at the cost of usability.

Re:The Elephant in the Room: Web design work is drying up by everlost on Wednesday February 24, 2016 @05:43PM (#11170849)
>A lot of the design problems have been solved already

This is partly true. Design problems have been solved for isolated cases. You still require designers to choose the right combination of solutions that work for particular use cases. And in my experience, all too often those "solutions" start conflicting with each other, resulting in new design problems!

Commoditization is definitely happening in design, but the design problems are not going away anytime soon.

Disclaimer/plug: I work on Squarespace design templates - http://www.square-mart.com

Re:The Elephant in the Room: Web design work is drying up by galfarragem on Wednesday February 24, 2016 @06:16PM (#11171027)
I just realised that all design markets behave in the same way: with maturity they shrink and most designers on that market _must_ adapt to survive.

E.g. on a mature architectural design market, the need for design projects of small scale buildings almost vanishes. It's common that the design project is offered by developers trying to get the building contract. Only on large scale buildings still persiat the need for specialist design. In web design the same trends seem to apply:

designers -> builders

generalists -> specialists

Re:The Elephant in the Room: Web design work is drying up by amelius on Wednesday February 24, 2016 @03:00PM (#11169728)
> I think there's a fundamental shift

Yes, there's a shift. But could it also be that, at the same time, work is also drying up? You speak of frameworks. Until recently we needed engineers to build the functionality of those frameworks; these engineers are not needed there anymore, but is there sufficient work left elsewhere? That is the important question, imho.

Re:The Elephant in the Room: Web design work is drying up by learc83 on Wednesday February 24, 2016 @03:07PM (#11169790)
Did the need for programmers dry up when off the shelf operating systems became mainstream, or when most of us started writing in higher level languages instead of assembly?

Software just get more complex and expands in scope when we can build on top of new abstractions.

Re:The Elephant in the Room: Web design work is drying up by ktRolster on Wednesday February 24, 2016 @03:15PM (#11169875)
Indeed, it seems software is getting more and more specialized, with more and more programmers needed in smaller and smaller areas. I know a guy who makes a good living programming specialized mining tools. I didn't even know such a profession existed before meeting him.
Re:The Elephant in the Room: Web design work is drying up by amelius on Wednesday February 24, 2016 @03:38PM (#11170051)
Perhaps he meant data-mining? :)
Re:The Elephant in the Room: Web design work is drying up by brbsix on Wednesday February 24, 2016 @05:36PM (#11170808)
What kind of mining? For data, cryptocurrency, or ore?
Re:The Elephant in the Room: Web design work is drying up by gaius on Wednesday February 24, 2016 @03:39PM (#11170057)
Keeping up with the frameworks is a full time job! Smart engineers don't bother. Find one you like and milk it for 5 years at least.
Re:The Elephant in the Room: Web design work is drying up by dragonshed on Wednesday February 24, 2016 @04:14PM (#11170277)
Milk the framework or the engineer?
Re:The Elephant in the Room: Web design work is drying up by hello_newman on Wednesday February 24, 2016 @04:42PM (#11170472)
yes
Re:The Elephant in the Room: Web design work is drying up by collyw on Wednesday February 24, 2016 @05:01PM (#11170587)
I don't think the work is drying up, but shifting to a higher level. The common problems are solved. Ten years ago we didn't use frameworks and development was slower and took more time. Frameworks represent the repetitive parts of development that are common to many applications. I am sure database technology was a similar shift before that. The same people building the parts that frameworks do are now building on top of the frameworks and building more functionality for less effort.
Re:The Elephant in the Room: Web design work is drying up by hellbanner on Wednesday February 24, 2016 @03:02PM (#11169741)
This is addressed on a larger scale by

http://thelightsinthetunnel.com

Re:The Elephant in the Room: Web design work is drying up by lmm on Wednesday February 24, 2016 @06:21PM (#11171052)
Engineer salaries keep rising. I think there's still plenty of demand from engineers - after all, you need an engineer to use a framework. More generally, when the price of a commodity drops, that often means the total gross sales of that commodity increase - greater demand more than makes up for the smaller unit price.
Re:The Elephant in the Room: Web design work is drying up by kriro on Thursday February 25, 2016 @01:52AM (#11172798)
Pretty much spot on. The flip side of this is that web interfaces (and mobile) are squarely in the mainstream (shocker :P) which is good to know if you're a software engineer. The biggest indicator of this is mentioned in the article. Companies internalizing web design.

I think there's plenty of work left in UI/UX but the "balance of power" with regards to base design has shifted towards software developers. I'm not very good at designing things and not too long ago I was almost ready to give up before getting started because I knew stuff would look ugly and I'd need a designer (wasn't easy to find good ones easily). These days you use bootstrap and a plethora of other tools and get pretty good results and then you can hire a designer to polish.

Re:The Elephant in the Room: Web design work is drying up by estefan on Thursday February 25, 2016 @07:04AM (#11173868)
> A lot of the design problems have been solved already. Questions such ... how to design forms effectively, what makes a good call-to-action

That's what I thought too until I tried to get the homepage of a web site designed. I'm using a popular "run a design contest" site with a higher bracket prize to try to attract good designers. Unfortunately, some of the crap the designers are turning in should be embarrassing for anyone calling themselves a designer :-(

Re:The Elephant in the Room: Web design work is drying up by patrickdavey on Friday February 26, 2016 @09:34AM (#11181543)
re " A lot of the design problems have been solved already. Questions such as when modals are appropriate, how to design forms effectively, what makes a good call-to-action, and how to structure IA effectively have been answered."

Do you have a book / resource / something where this information is distilled?

Re:The Elephant in the Room: Web design work is drying up by c4n4rd on Wednesday February 24, 2016 @02:48PM (#11169650)
"Questions such as when modals are appropriate"

Can you point me to a document for this?

Thank you.

Re:The Elephant in the Room: Web design work is drying up by FilterSweep on Wednesday February 24, 2016 @02:53PM (#11169685)
Perhaps start here:

https://www.nngroup.com/articles/overuse-of-overlays/

Then ux.stackexchange.com will undoubtedly have some useful pointers as well....

Although some tailored google searches will also help.

Back in my UX-only days, I used NN Group a lot in supplementing my own A/B testing - it was a bittersweet relationship, as they provide a suite of analytics-based trackers on many of the websites I visit.

Re:The Elephant in the Room: Web design work is drying up by epicureanideal on Wednesday February 24, 2016 @02:57PM (#11169708)
Read "The Humane Interface". The short answer is, almost never. Try to avoid them.
Re:The Elephant in the Room: Web design work is drying up by wmil on Wednesday February 24, 2016 @10:23PM (#11172155)
I am so glad to see someone write this. I've worked with too many designers who stack modals onto modals.
Re:The Elephant in the Room: Web design work is drying up by josephcooney on Wednesday February 24, 2016 @03:42PM (#11170078)
Agree. I figured the person asking the question was being amusing.
Re:The Elephant in the Room: Web design work is drying up by cvburgess on Wednesday February 24, 2016 @02:55PM (#11169695)
Here's one of many examples I found on the first page of Google.

https://www.smashingmagazine.com/2009/05/modal-windows-in-mo...

Re:The Elephant in the Room: Web design work is drying up by hmans on Wednesday February 24, 2016 @03:29PM (#11169994)
This is the correct answer.