Simple = quick + easy. But how?

This might be the reason, "When I got into the workforce, I always felt excluded. In my first job I got promoted to senior then team lead all within two years largely due to an amazing female manager. Then I got passed to a male manager and suddenly I was a bad employee." Highly detrimental.

OK, you just don't get it. I understand.

I think this reflects more on who you follow. People might have totally different experiences on X.

It's hard to quantify the answer to this question because nearly every frontend developer has to deal with current lack of native support for styling <select /> elements resulting in every design system or component library doing their own thing to be able to add a different color value or a border.

Read a novel or do something to experience something new (or bring back a memory) outside of work context... we're humans, not bees :)

use better tools

Use modern tooling like asdf (mac/linux) or vfox (windows) to manage nodejs. All you need to do is install versions you need and add .tool-versions file in directories you need specific version. No need for typying any commands.

What do you mean by that? I import CSS styleshets without any problems, but at work I see people use hierarchies of styled and MU components to add backgrounds and colors, and margins to an input element... and then they wonder why their aps are slow.

It's 10K words on your blog or 10K words here?

Some people in Texas worship HEB--it's a cult! But HEB stinks and sucks.

I bet it could not be the only explanation for this but in that case it sounds reasonable depending on the size of the stylesheet. But what you lose by doing this is probably not what engineers thought ... "Nobody will use these in browser DevTools, right?"

Nobody documented these steps before but that's what the team was expected to do before a PR could be merged.

Microfrontends for the win... WTF🤬

Today at work I wrote 28-step instructions on how to get to a point where you can test changes made to a couple of React components exported as a NPM package. They involve setting up four separate repositories, installing their dependencies and runnind a portal shell rendering an app in an iframe...

CSS is foundational, Tailwind is an add-on.

Are you validating my point that it is in equal measure that women treat other women like that?

Yeah, I've seen them in Russia eating nuts from chess players' hands but not here. In Poland, it's rare to see them, though.

When Justice Roberts tells you to raise your right hand you do what you're told :)

Oh yeah. The red ones are rare. Probably easier to find closer to the Rockies.

Oh, didn't know... I'm from continental Europe :)

It's history... and a show since it's indoor. The most interesting is to see how Barron has changed. Is he the future?

... roaming the streets in the suburbs when I visit my family. Always wondered why and how. In Europe, we see these creatures, if ever, only in the forest or in a zoo.

Say what you will about 'Murica but I see squirrels racing up and down the tree in my front yard almost every day... in the middle of a 8 million metropolitan area. And every other day in summer we can hear a pack of coyotes howling on the other side of a creek. In San Antonio I see herds of deer...

Will try that... btw, a slightly customized `open-props` was foundational in a CSS architecture and a component library I created and used throughout a company I worked for (that was two years ago :))... thank you! Great work!

Nested CSS layers 👍

I think it's awesome! At work (I'm new there) the place is riddled with a full gamut of `@mui/react` and `@emotion/*`... horror!!! `Select` might be too experimental, though :)... it doesn't seem to work in my latest Chrome Stable. I haven't looked that closely; do I need to set a flag somewhere?

I know that type.

But that guy has and will find no real place and any respect among real devs.

I have been around and seen my share of incompetence.