I’m at the same chesscom rating as you and have watched a bit of Hikaru content but somehow felt like I was procrastinating on “real chess study”. Your comment has given me an excuse to try again!
13 karma · joined January 27, 2015
I’m at the same chesscom rating as you and have watched a bit of Hikaru content but somehow felt like I was procrastinating on “real chess study”. Your comment has given me an excuse to try again!
When you consider UX, accessibility, progressive enhancement, cross browser and cross device support - there’s plenty to know. And unlike programming, it doesn’t all flow logically. Some stuff is subjective, other stuff requires specific knowledge of browser quirks etc.
The only site that helped me gain some _understanding_ of CSS (as opposed to knowledge, tricks and hacks) was this one http://learnlayout.com
It’s a bit dated now - Flexbox is mentioned at the end and CSS Grid is entirely absent - but still important if you’re supporting older browsers.
But CSS has never “clicked” for me. For a start the whole idea of cascade is based on inheritance and I generally prefer composition. I like designing UIs and it’s quite a satisfying challenge to match a wireframe to the pixel. But overall, I’d rather be writing application code.
If users could just read JSON everything would be a lot easier...
Having said that, the long term stability of that path is definitely debatable!
For me it was more because I found chess to be such a demanding game. One can play well for hours (in a serious match) making many good moves only to have it all thrown away by one slip of concentration.
I've linked to the slides on currying but you'll need to back up to follow the whole example.
[1] http://scott.sauyet.com/Javascript/Talk/FunctionalProgrammin...