5 ms·
Hire HTML and CSS People
- the_clarence 2y agoI don't get it.
- FrustratedMonky 2y ago"Every problem at every company I’ve ever worked at eventually boils down to “please dear god can we just hire people who know how to write HTML and CSS.”" Isn't HTML and CSS a base line, every programmer knows this? "This UX is awful? " But that doesn't make them good UX designers.
- recursive 2y ago> Isn't HTML and CSS a base line, every programmer knows this? Yes, it isn't a baseline. I'm talking about what is, not what should be. In some (large) circles using HTML or CSS is regarded akin to writing machine instructions rather than python. It should be avoided because no one understands it and you'll create a maintenance problem.
- ivan_gammel 2y agoWow. I wonder who are those people in those circles. They clearly have no clue about frontend development, because a decent abstraction layer on top of those “low-level” instructions has never materialized. 100% of frameworks and renderers do leak abstraction and you have to deal with HTML and CSS anyway at some point.
- axelerator 2y agoThere are bunch of good UX principles baked into HTML and CSS. Plus to become good at HTML and CSS you will be exposed to a lot of UX talk as well. So one could argue it's really hard to get really good at HTML and CSS and not care about UX at all. But yes, a fool with a tool is still a fool - if that's the point you're trying to make.
- FrustratedMonky 2y agoNot directly making that point. Just that a lot of programmers aren't necessarily known for their design aesthetic. So you could 'not be a fool', and be very good at HTML/CSS, and yet not really understand or care about color, flow, layout. But, to your point, surely they will absorb something in the process. But it is far from a given. Isn't this the entire argument between Apple-Microsoft, Jobs-Gates? Gates isn't a fool, neither are MS programmers, but they aren't known for good 'ux designs' There are a lot more technology experts than good Design experts.
- icedchai 2y agoIt seems building SPAs and using related frameworks unnecessarily is now the baseline. People who really know HTML and CSS are few and far between. Many are just copy-pasting.
- Epskampie 2y agoI know CSS quite well, as I've been working with it over 15 years. I've been surprised that new programmers hardly know it at all, and heavily lean on component libraries or css frameworks. Can see why though, css has become very large and complex, and it's only getting worse. The upside is that my simple fixes sometimes seem like a superpower to others.
- notpushkin 2y ago> css has become very large and complex Respectfully disagree. I think CSS is simpler than ever, and it’s only getting more streamlined and powerful. E.g. what used to be a complex blob of floats is now a simple grid layout.
- hk1337 2y agoAs a markup language I think it's getting more complex but there's a lot more functionality that makes it a lot easier to do things with it. Knowing when to use what functionality can be overwhelming and seem complex though. There's a lot about it I like though. It seems like it's starting, or perhaps already has, made things like SASS obsolete. I am working through now creating a Hugo theme for my blog using just CSS (no Sass, Tailwind, etc), trying to avoid needing to use Hugo extended.
- legitster 2y agoHear hear. The tools are also so much easier. Every browser comes with a built-in inspector and console tool. HTML + CSS is the lowest bar to entry of any skill.
- karaterobot 2y agoIt's getting more powerful than ever, and it's easier to do things that used to be hard (vertically centering, etc.), but it's also got a lot more capabilities that have a learning curve (custom properties, color functions, container queries, etc.). I've been writing CSS since 1997, and I remember having to use invalid characters to fork CSS in the days of IE 6, and all the old school hacks involving floats, full-height content, etc. CSS in that era was hard, but it was hard in the sense of "there's stuff we just can't do in the browser, so let's design around that". Nowadays, it's hard in a different way, which is "oh, I guess there's an entire new hoard of CSS capabilities I've literally never heard of before, and I need to spend some time wrapping my brain around it, so I can add it to the massive and ever-growing pile of CSS things I need to know".
- ponector 2y agoI don't agree. Hire people who cares about results, actual product. Nowadays people cares only about closed stories. Performance? Usability? Usual response is: Not my job, don't care!
- hk1337 2y agoI agree, building a good company culture will dictate a lot with people's feelings about doing their job and also hiring people that share the same feelings.
- baggy_trough 2y agoI love the improvements to CSS over the past few years. Directly serving nested CSS rules with no build step feels awesome.
- solardev 2y agoThis has nothing to do with HTML or CSS vs any other language of the web. It should be "Prioritize frontend usability and design." For that you need good UX/UI people, who may or may not know HTML or CSS. It doesn't matter. Any competent frontend dev can copy a good Figma, but not every HTML/CSS/Tailwind/JS dev can make a pretty, usable, accessible website. If you think about your frontend primarily in terms of how "vanilla" to go... then you're writing a website by engineers, for engineers. It might have pretty source, but that doesn't in any way guarantee good usability or design. Regular users never see your source and don't care about it, but they will definitely see your UX work (or lack thereof).
- legitster 2y ago> Any competent frontend dev can copy a good Figma I think that's part of the problem. If UX people don't know code and code people don't know UX, neither has the ability to validate each other's work.
- solardev 2y agoThat's never been a problem in my experience...? As a frontend dev, I routinely work with designers who can't code. They send me a Figma, maybe talk me through the highlights, and I implement an initial prototype that gets maybe 80-90% there. A little back and forth later and we have something that's like 99% there, with minor bugs we fix after release. They didn't need to know any HTML or CSS. Figma puts pretty good guardrails around their design possibilities already.
- u8_friedrich 2y agoiykyk
- anotherhue 2y agoYou can't hire what you can't find (at your budget), so if you agree with the principle the imperative becomes 'teach html & css', and try to explain to the students why the guy next to him on react is already three projects ahead and has two 'native' apps to boot.
- cies 2y ago> This UX is awful? That UI looks old? Is was made by HTML+CSS people. That's why. If you want your UX to improve, look for a skilled UX designer. Then agree and sign off on some designs, and let your HTML+CSS ppl hammer it out. Usually HTML+CSS people are NOT the people that fix your UX (sure there are exceptions).
- alexfromapex 2y agoI have a different strategy: hire managers that are technically inclined.
- deleted 2y ago[deleted]
- legitster 2y agoI'm a crusty old HTML and CSS person. The problem is that most of the skills are in the marketing department - not engineering. I've noticed lately a huge "React-ification" in the past few years where the UI on apps are both getting overly designed, but also more confusing and worse. Bigger buttons, bigger text, overuse of whitespace, bad pagination and breadcrumbs, etc. There are a lot of best practices that were "solved" a decade ago that now seem to be getting lost. And the explanation that I have is that React and Figma have made it so easy to spin up a web app without any prior experience or reliance on prior works. "Enough rope to hang themselves" as the saying goes. I worked with an engineering team that was struggling with their UI. The buttons were all the wrong sizes, colors weren't consistent, placement wasn't consistent, etc. I asked them if they were using a CSS framework at all and the response was "we are using React, we don't need one".
- al_borland 2y ago> I asked them if they were using a CSS framework at all and the response was "we are using React, we don't need one". This hurt my brain. I recently saw a video where a guy was claiming that people who had gone through a web development bootcamp (using React and the whole nine), where unable to make a basic hello world HTML file. When people don’t know the basics, it’s no wonder everything is over complicated. They were never taught how it could be simple.
- ffsm8 2y ago> This hurt my brain. Why? It's straight up correct. Sure, you could still use a css framework, but you really don't need to once you're using any frontend library. Each component comes with it's own styles, that makes the css framework redundant, as a component library gives you a better development experience with the same effect. Add a few global vars for theme colorings, default spacing etc and it becomes pretty straightforward to maintain a coherent UI even across repositories/teams (or distribute a tailwind config,works even better imo)
- al_borland 2y ago
- wmil 2y agoI think the issue is that HTML and CSS are awful braindead work that are a career killer. If you hire developers who know HTML and CSS please rotate in some more interesting work for them. Also be careful not to elevate the design team above people doing the HTML / CSS. Too often the design people go back and forth with a higher up until an "approved final design" that makes no sense gets thrown in the laps of the devs.
- windows2020 2y agoWriting consistent, concise and elegant HTML and CSS takes practice. Mastery of a language and discovery of its patterns requires thought.
- wmil 2y agoI'm not seeing how that relates to my comment.
- arp242 2y agoI think the point that was being made is "if you hire HTML/CSS people, then don't make them monkeys that are only allowed to blindly follow instructions, but involve them in the process and treat them as professionals". Or at least, that's how I read it anyway. So basically, I think you agree with the previous poster?
- arp242 2y agoIn general I think the "design team" should be the "HTML and CSS" people. Today, by "design" people often mean "graphical design", which tends to attract more art-type people. But what is really needed is "UI design", which is a much broader discipline which involves art, technical stuff, and psychology. You need to think about "what looks good?", but also "what makes a good UI for our product", and "what can we reasonably implement without too much complexity?" Certainly in my experience this confusion between "graphical design" and "UI design" seems to be a huge chunk of the problem.
- afloatboat 2y agoI wish! I love working with HTML and CSS, but every front end job is covered by the blanket term “front end” that considers you as much a JavaScript ‘architect’ as they do a UI developer. Not realising that this does not make the slightest sense. Can’t tell you how many times I’ve had to tell experienced developers they should use anchors to link to other pages and not an onClick. Those same people are much better in architecting then I will ever be, yet technically we have the same job description.
- beretguy 2y ago> use anchors to link to other pages and not an onClick That's beyond bizarre.
- afloatboat 2y agoNot if you consider that a lot of front end developers today started learning web development through JavaScript. I started around 2000, when people were still using tables for layout and CSS was pretty new. If you wanted interactivity you relied on the built-in tools on the web because there was no other choice (apart from something more extreme like Java applets or Flash). Today’s web developer starts with something like React, learns JSX instead of HTML and doesn’t need the form tag or checkboxes/radiobuttions/select because they have useState, onClick and className to highlight whatever they think is active. I’ve been working as a React consultant for +6 years now, and every PR I see has the same issues. I wish I was lying about the onClick on anchor tags, and for primary navigation it’s usually done right. But once they see a block link that contains multiple components (a “card”) the mind always seems to jump to onClicks that call navigate. A more advanced error is when something is an anchor, they correctly implement the a tag with an onClick and preventDedault, but they forget to check if the user is holding down shift, hyper or control or if they pressed any other than the primary mouse button to try and open the link in a different tab/window. Semantics in general is a lost art as well. A Text component that only returns p or spans is used for titles, they don’t consider hierarchy at all. To be fair, there is so much logic in the client now that I understand that people with different ambitions have taken an interest in it. The only problem is that companies just blindly hire for front end developers without considering the different expertises. I think this is the root cause for a lot of the complaints HN has about JS. I want to build good UI and UX, but there’s so much other work and configuration that I’m expected to work on, in a limited timeframe to not ruin my velocity that I just never get to it.
- librasteve 2y agoi’m liking htmx.org since that puts the cognitive focus back on HTML and CSS
- jcauley89 2y ago[dead]
- Dgriccs 2y agoThe advent of technology has given rise to social media platforms and applications which have facilitated easy interaction and communication between individuals. However, such platforms remain vulnerable to misuse by individuals who are habitually unfaithful. In the case where you may need to monitor your boyfriend's phone, it may be advisable to seek the services of a proficient hacker, such as tomcyberghost @ gm a il com, who can provide a plethora of comprehensive details. Based on my experience, this hacker has demonstrated a track record of trustworthiness, reliability and dependability - even in situations where the individual under scrutiny is untrustworthy.
- Stevendonna 2y ago[dead]