It's 2023, here is why your web design sucks
heather-buchel.com
heather-buchel.com
I disagree, what happened was that javascript got fast and now everyone wanted web apps instead of web pages. Web designers makes web pages, documents with little javascript. Web developers makes web apps with huge amounts of javascript. They are two very different roles, it makes sense to have different job titles for them.
Then why call people who can do both developers? Because developers are paid more than designers, so people who can do both prefer the developer title. This means that there is no longer anyone who is called web designer.
Haha. I'm afraid you are right.
I make web apps. This means that I have to know about Docker and Kubernetes (because our deployment is complex), protocol buffers (because our services talk to one another), Kafka (because they talk asynchronously), parsing abstract syntax trees (because apps that I do are IDEs), git and its internals and filesystems (not only to work on our source code, but because our apps actually launch some git commands behind the scenes), SQL and quirks of different OLTP and OLAP databases, Rust, Python, Go and other programming languages, WebGL and other 3d rendering topics like writing shaders and projection matrices, processing RTL texts, emojis and all other wonderful aspects of unicode (including utf16 surrogate pairs), HTTP protocol, TCP, UDP and websockets...
You know what I would do without? Keeping up to date with Photoshop, Illustrator and color circles. I'm still doing a lot of UX decisions, of course. But for the love of god, just give me sensible defaults and component library.
Ctrl+w
> and just hear me out, I am going to explain that.
Honestly, I ponder whether reacting to the mention of gender as harshly as this is remotely healthy or even logical.
>And, the boys in the industry at this time made it known that we were not "real" developers.
>the gendering of design as women's work is why people don't use the title "web designer" anymore. It's been belittled and othered away.
>Well, the area of front-end work, which has been heavily gendered as "feminine" work, was finally being viewed as "serious" or "real" programming because, to no one's surprise, something that is designed well is good for business. As a "real" career option for developers, now men are interested. You're welcome.
>Sorry, building websites is for us serious manly man engineers now who can do very difficult things like making the computers go beep boop.
>Since the "design" piece of web design is still viewed as a feminine role, that part of being a web designer was largely cut off from the front-end development role, now that men were all in on that role.
You are going to tell me that this person has any kind of numbers or studies to back any of this up? Show me something solid that says the majority male devs view web design as women's work. Until then it's just a rant.
https://news.ycombinator.com/item?id=38031363
95% male.
This is all fine, because it's her article and we can all do as we will, but I really cannot understand how you think this point is reasonably made.
>Just a PSA: No, I won't be providing you data to prove that design has been viewed as women's work and thus anything related to design that touches development work (like web design!) has been eroded and chipped off from the block of knowledge you're expected to know. I'm tired. Do your own homework.
>"what data do you have" Me, bitch. I'm the data.
So, "Web design sucks cause of men. Source: trust me bro". Hard to believe anyone would think this could be taken seriously.
The field of web design hasn't been recategorised due to it being gendered - in fact most web designers pre-2010 were men - it got refactored due to variances in how we see frontend and shortcuts to profit (capitalism).
It is now a lot more profitable to run a single or small sized team doing full stack and use templating, the various scaffolds of tailwind, bootstrap, etc or simply outsource the design elements, which are often a one time thing. Modern dev allows frontend and backend to be built in the same languages, abstracts heavily and often provides all the infrastucture too.
Web designers are broadly a dead category due to this, as are sysadmins, backend devs and frontend devs (all predominently male areas).
I've encountered plenty of UI developers that have very little visual design sense and are mostly fine, and I've encounter plenty of UI designers that don't know the intricacies of the front-end. Sure, sometimes those two have to hash things out, but that hasn't seemed to have been a large blocker in my experience; just part of the process.
Nowadays, most companies building websites have split the responsibilities into multiple roles.
Frontend Engineers aren’t called “web designers” because that’s not what they do. A UX Designer and graphic designer decided how a button should look and feel, and the frontend engineer is the one who implements the functionality in code. They literally are not designers.
The article acknowledges the splitting of the roles but doesn’t explain why this is supposed to be a bad thing. It’s pretty obvious why the split took place: because websites are more complex and standards are higher (unless you think the space jam website is the pinnacle of web design).
However in my experience the best “front-end engineers” are designers. One of the best I’ve ever worked with called himself “Devsigner.” He was a passionate Android developer who knew the platform conventions better than the designers did, he was able to identify tiny flaws in designs (incorrect font weights, inconsistent padding, adherence to platform conventions), as well as larger flaws in the UX, for example, how to consistently and intuitively navigate between screens, when and where to place navigation elements, etc
Development wise, he was able to devise the app architecture clearly. Write end-to-end mock servers to perform UI testing, build the dev ops pipeline, manage app releases, and implement the UI using best practices
I am the same sort of designer/developer, and I expect that many people are capable of doing both things like this. They just need the opportunity and positive feedback to get there
Websites are more complex, but I expect people to be capable of learning complex things and to be aware of, and apply, design principles
I won't presume to analyze the root causes of gender bias in tech, but it's just lazy thinking to blame the decline of the hybrid designer/coder as being due to sexism and "role gendering". The more obvious answer is that the depth of expertise needed for modern UX design and front-end development grew by a lot, and hence the generic "web designer" role disappeared in favor of greater specialization. Blaming this on the patriarchy might get you sympathy and clicks in the current zeitgest, but it doesn't really say antyhing about causality or what's actually going on.
WTF? This is the literally first time I've heard someone describe web-design as "women's work."
I find myself worrying that it's the opening move of some sort of "damned-if-you-do, damned-if-you-don't" scenario from the author, e.g.: "Oh, so it's men's work!? How sexist!"
While I believe every word of that article I still think it's a very personal view of a very personal situation.
Were I lived girls were just <5% of IT in university and while they actually had great grades and only half of them dropped out/resigned (it was 3/4 dropouts for guys ;/) I know only two that wanted to stay in the field. One was actually a dropout as well, but switched to construction engineering and is a doctor in that field. Other one was always a Linux enthusiast and became a somewhat known security researcher. That's 2 out of over 400.
"dude": a man; a guy (from Oxford Languages)
I’m a dude, he’s a dude, she’s a dude, ‘cause we’re all dudes, hey.
Yeah ... nope. The reason for the split (and I think it started earlier) is that front-end development changed from being a bit of HTML, CSS and a smattering of JS or PHP, to real actual structured, architected programming with complex frameworks etc. Web design similarly become something much more professional, and more aligned with design in other fields. Therefore 'web design' carried an air of amateurism, and was no longer fashionable versus simply 'design'.
I started out as an animator/designer, and then became a developer. I became a developer because I wanted to write plugins for the 3D modelling software I used. Over the decades I have become extremely jaded at how companies I have worked for organise into “UX Design” and “Development” teams. It is utter nonsense
Everyone I have worked with, once trained, is capable of doing both — perhaps not everyone tackles design or development with the same passion, but teams who have comfort with both areas of app/web design and development often produce superior products
Now I am in a position to build a team at a company that is divided into “UX” and “Development.” I hope to ask people on the design team to install Xcode and Android Studio, to get comfortable making quick prototypes in Compose and SwiftUI, to update asset catalogues and colours, and to make branches and commit changes. Designers are genuinely excited about this
Similarly, I have started giving developers edit access to Figma, helping them produce design and visually communicate on a Figma board, tweak and suggest designs, and even build parts that can be approved by people on the “design team.” Developers have no problem doing this
I am hoping that the lines between “designer” and “developer” dissolve and we simply have coordinated teams, with talented people able to direct the vision for both aspects of a product
In my personal side projects everyone is treated as both designer and developer, no one “blindly implements” design (which I have experienced at many large companies) and no one creates design without understanding the nuances of the platform. This results in much less back-and-forth, and products that ship with more consistent UI design
edit: typo
Ballistics computing was obviously done by women as the men were drafted & overseas, but all paid at 'subprofessional rates'. Another good history at https://confluence.gallatin.nyu.edu/sections/research/how-co...
There are definitely some parallels between OP's article and the history of computing.
YMMV but personally, while I've met both male and female developers of all stripes and strats, I’ve only met male web designers, so this thesis doesn’t resonate strongly with me.