Unleash Creative Possibilities: Exploring 9 Hidden CSS Pseudo-Elements
When many devs think of CSS they think of Peter Griffin trying to open window blinds. But for others CSS is more like putting their hand in the pain box from Dune while some product manager has a gom jabbar to their neck, daring them to pull their hand out.
There's a few reasons why tech continues to struggle with CSS.
We're bad at teaching CSS. While there are a ton of great CSS practitioners out there sharing their knowledge (Stephanie Eckles, Kevin Powell, and Adam Argyle, to name a few), a lot of people learn HTML and CSS in college or bootcamps from people who are perhaps not as knowledgeable, use outdated techniques or gloss over the basics in favor of frameworks like Bootstrap or Tailwind. As a result, you end up with a lot of folks who don't have a deep knowledge of HTML and CSS, which are the basic building blocks of the web.
We're bad at hiring for CSS. Just about every job listing for a full stack or frontend engineer lists HTML, CSS and JavaScript proficiency as a prerequisite, but when they interview candidates, they're rarely testing for anything other than JavaScript skills. If companies end up hiring people with CSS skills, it's usually by accident. And if you don't have people with those skills you can't vet other people for those skills and the problem perpetuates itself.
We're bad at writing CSS. Without deep knowledge of CSS and with an inability to hire people with that knowledge, people go to great lengths to avoid writing CSS, whether by relying on Bootstrap/Tailwind or trying to do everything in JavaScript. They end up over-complicating things to the point where their CSS is extremely hard to maintain.
There's a few reasons why tech continues to struggle with CSS.
We're bad at teaching CSS. While there are a ton of great CSS practitioners out there sharing their knowledge (Stephanie Eckles, Kevin Powell, and Adam Argyle, to name a few), a lot of people learn HTML and CSS in college or bootcamps from people who are perhaps not as knowledgeable, use outdated techniques or gloss over the basics in favor of frameworks like Bootstrap or Tailwind. As a result, you end up with a lot of folks who don't have a deep knowledge of HTML and CSS, which are the basic building blocks of the web.
We're bad at hiring for CSS. Just about every job listing for a full stack or frontend engineer lists HTML, CSS and JavaScript proficiency as a prerequisite, but when they interview candidates, they're rarely testing for anything other than JavaScript skills. If companies end up hiring people with CSS skills, it's usually by accident. And if you don't have people with those skills you can't vet other people for those skills and the problem perpetuates itself.
We're bad at writing CSS. Without deep knowledge of CSS and with an inability to hire people with that knowledge, people go to great lengths to avoid writing CSS, whether by relying on Bootstrap/Tailwind or trying to do everything in JavaScript. They end up over-complicating things to the point where their CSS is extremely hard to maintain.
With UX as a discipline transforming rapidly, emerging from the debris are specialisations that sound different but still focus on providing a strong user experience. It is time for us to agree on some sort of a model that explains the nature of UX and its relationship with business as a whole.
A free-to-use, locally running, privacy-aware chatbot. No GPU or internet required.
Pour un rendu réaliste stylo bic, c'est bien simple je n'ai jamais trouvé mieux.
The verdict is unavoidably in favour of just sticking to CSS. It costs nothing, and it’s an invaluable, transferable skill.
CSS Masking
mask-image:
mask-image:
Tailwind CSS est source de discorde chez Soumettre.fr : 16 heures passées au téléphone, 2 engueulades, et 8 tacles à la gorge. Suite à une longue discussion sur Twitter, j'ai décidé d'en faire un article dédié. Attention, on va parler d'intégration, de HTML et de CSS.
Improving CSS Shapes with Trigonometric Functions