Good rule of thumb: Don't set `height` on your elements (often, the same applies to `width`). Even on stuff like images, this can cause unexpected issues like overflow (aspect-ratio can cause this, too). Using display properties on the parent container is frequently the better solution. Grid, gap, and padding go a LONG way. I rarely ever need to use margin or float. The cascade is your friend!
Scott missed the opportunity to do the segue like: While we have drama in the break dance. Your code is breaking dramatically and sentry is here to help you... Or something like that 😂
From my experience, people have harder time wrestling with CSS compared to JS. It seems that CSS' global nature and cascade trips people up way too much. Even with guidance and mentoring from more experienced people, it seems CSS is still super hard for people. Too many people seem to just randomly apply CSS properties until something sticks as Scott mentioned.
Absolutely, it's a very different, declarative mindset that requires learning the cascade, inheritance, intrinsic vs extrinsic sizing, etc, and many people just never learn those fundamentals. Some then call the language "broken" without really understanding it's true capabilities and shortfalls.
Good call on flexbox vs grid. My rule of thumb (not an original thought, heard it somewhere...) is flex for 1-dimensional layouts, grid for 2-dimensional layouts
![[Live] : ONE 169 วันนี้!! "อนาโตลี vs อูมาร์"](http://i.ytimg.com/vi/IK3YZVWuFJg/mqdefault.jpg)
Good rule of thumb: Don't set `height` on your elements (often, the same applies to `width`). Even on stuff like images, this can cause unexpected issues like overflow (aspect-ratio can cause this, too). Using display properties on the parent container is frequently the better solution.
Grid, gap, and padding go a LONG way. I rarely ever need to use margin or float.
The cascade is your friend!
Scott missed the opportunity to do the segue like:
While we have drama in the break dance. Your code is breaking dramatically and sentry is here to help you...
Or something like that 😂
05:45 - Podcast about CSS starts here
But if you want to hear about Olympic breaking start from 0
From my experience, people have harder time wrestling with CSS compared to JS. It seems that CSS' global nature and cascade trips people up way too much. Even with guidance and mentoring from more experienced people, it seems CSS is still super hard for people.
Too many people seem to just randomly apply CSS properties until something sticks as Scott mentioned.
Absolutely, it's a very different, declarative mindset that requires learning the cascade, inheritance, intrinsic vs extrinsic sizing, etc, and many people just never learn those fundamentals. Some then call the language "broken" without really understanding it's true capabilities and shortfalls.
WET code - "Write Everything Twice"
Good call on flexbox vs grid. My rule of thumb (not an original thought, heard it somewhere...) is flex for 1-dimensional layouts, grid for 2-dimensional layouts
That Syntax hat needs to be on the Sentry swag store!
14:45 - "I'm healed, nice" - tears in my eyes🤣
4:50 "for a country that's upside down you'd think they would be pretty good at breakdancing" - Wes 😂😂
DAMP code: Duplicate Appropriately in Multiple Places
12:28 are we talking about CSS
Nice Frosty Freeze reference!!
RYFT - repeat yourself few times
Why the F are you talking about the state of Olympic breakdancing? 😞