8 CSS gotchas to start your morning off right
Isaac Lyman

CSS Gurus are like philosophy professors who got called into a scrum meeting by mistake. what is a pixel? What does absolute really mean? Aren’t all values relative? Just change your paradigm of sizing!

CSS, as a language is fine. The syntax is simple. Yeah, you might have the occasional poorly named property (font-style, text-transform, text-decoration). And yeah, sometimes it might take some effort to write out the correct value for a property (here in the midwest, it’s not uncommon to worship those who can write working transforms as minor deities).

But, the real magic of CSS is its ~implementation~ interpretation. More precisely, the fact that every browser has to interpret the CSS specifications.

That’s what makes CSS Gurus so special; they’re philosophy professors who’ve accepted that visibility cannot be truly hidden, being is not being, and that a position is relative so long as there is also an absolute!

They’re the English literature professors who have written 200-page dissertations on the fluid meanings of four letter Dutch words in Shakespeare’s 5th act of Hamlet. They’re the people who’ve spent days pondering the meaning of “time” and can then use that knowledge to explain why your pizza was supposed to be 75 minutes late even though you literally live no more than 15 minutes from Dominoes (i.e. Opacity changes how position:fixed works)

CSS Gurus know better than to accept GiGo as axiomatic in web development. We can accept that an em isn’t an em. GiGo might be true of raw computer science. But in CSS development, nay. It’s more like GiBYGWYGO (Garbage in, but you get what you get out).

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.