Joe T

@ghostwriter Same here! Unfortunately, my personal quality standards influence my work, and that slower process to get it right once doesn't fly very well. I need a way to learn balance between good enough for the job and good enough for myself.

@Albright I'm obviously stepping outside my expertise; I'm incredibly rusty on front end. 😬 I only meant to agree with your point that CSS deserves to remain its own thing instead of becoming virtually embedded in all JavaScript work. 😉

@chris_evelyn This is generally the position I would take, too, I just struggle to actually *keep* that balance.

@norootcause As programmers, we should refuse any interview that includes one. I'm a good programmer, 20+ years doing this work. But I blew it last week because I couldn't convert comprehension of the requirements into code. My brain just locked up.

@Albright I feel like all the effort I put into learning how CSS actually works only for CSS-in-JS and Classname Slop take over. Considering the mess that the evolution of CSS created, what are the odds of a replacement language that starts from the position of standards (now that most browsers are playing nice at that level)?

@Albright I like CSS. It makes sense to me. But it gained traction in the middle of the Browser Wars. Standards were ignored and designers didn't want to learn all the hacks, let alone the logic. So layout moved back to JS (jQ, Bootstrap, TW, etc.). I often wonder how bloated site builds are because CSS is one of JavaScript's responsibilities. What if shallow DOM was a higher priority? Grid & Flex have matured, but it seems site builders still find ways to bury content 15 DIVs deep...