Common patterns that get the job done are handy because if we come across it in a codebase, we know exactly what’s going on… but sometimes, familiarity holds us back. I get pushback when I use new methods to solve things we already have solutions to, but I don’t do it just for the sake of it, I do it because I feel like the new ways are better.

Plus, some old patterns, like declaring `flex: 1` on all the flex items to have even columns isn’t exactly common sense, it’s just something we’ve grown familiar with because it works, so there’s no reason other somewhat strange (at first glance, anyway) solutions can’t become common patterns over time.

Links
✅ My video explaining the * 999 flex switch:
✅ Every Layout: https://everylayout.dev/

⌚ Timestamps
00:00 Introduction
00:50 using width: min() for a wrapper
04:30 did you never start using arrow functions in JS?
05:10 Using custom properties to make things more readable
07:48 main with sidebar
11:00 main with sidebar where the breakpoint is based on one of the children’s size
14:45 The flow class ( * + * )
21:00 why is flex: 1 for equal columns not considered bad practice?

#css



Come hang out with other dev's in my Discord Community
  / discord  

Keep up to date with everything I'm up to
✉ https://www.kevinpowell.co/newsletter

Come hang out with me live every Monday on Twitch!
  / kevinpowellcss  



Help support my channel
‍ Get a course: https://www.kevinpowell.co/courses
Buy a shirt: https://teespring.com/stores/makingt...
Support me on Patreon:   / kevinpowell  



My editor: VS Code https://code.visualstudio.com/



I'm on some other places on the internet too!

If you'd like a behind the scenes and previews of what's coming up on my YouTube channel, make sure to follow me on Instagram and Twitter.

Twitter:   / kevinjpowell  
Codepen: https://codepen.io/kevinpowell/
Github: https://github.com/kevinpowell



And whatever you do, don't forget to keep on making your corner of the internet just a little bit more awesome!