I want to help expedite that process for you. It was undeniably effective-the end result is incredibly worthwhile-but the journey was long and arduous. So how do you learn the rules of CSS? Well, you can spend countless hours spelunking through MDN documentation and CSSWG specifications, and then spend a few years practicing. All of a sudden, the most frustrating part of your job becomes fun! As JS developers, we spend so much energy trying to avoid writing CSS, when we could be embracing it, and using it to build world-class user interfaces. If you learn the rules of CSS, you can be good at it too!īecoming proficient with CSS is game-changing. And it's the most unfair self-criticism in the world. We assume that we're missing some sort of “CSS gene”, that we're just not good at this stuff. Except it's even worse, since we blame ourselves! It's like trying to solve a puzzle when you're missing pieces.

We learn “cool tricks” for specific situations, instead of concepts that can be applied broadly to any situation. Think about how most of us learn CSS: we learn how individual properties work, instead of focusing on how layout algorithms use those properties as inputs. It doesn't matter how many years you spend practicing CSS-if you don't learn how its underlying systems work, your mental model will always be incomplete. It feels unpredictable because there are complex systems involved, systems that are totally invisible to us. No wonder so many of us don't enjoy writing CSS!ĭespite all appearances, though, CSS is actually a deeply consistent and robust language. These constant bewildering surprises take us out of flow state, and shake our confidence. In CSS, by contrast, you're left in the dark, without any clues about why you're not getting the result you expected. When you make a mistake in Typescript, you get a helpful tooltip telling you exactly what you did wrong. For a lot of front-end developers, CSS is the most frustrating part of their work.

Css for js