4 ms·

> The content is dated, using hacky techniques to work around deficiencies that no longer exist. While I certainly agree that a lot has changed in the 4 years

> The content is dated, using hacky techniques to work around deficiencies that no longer exist. While I certainly agree that a lot has changed in the 4 years since Magic was authored, I think this statement is a little strong. I’d argue that chapters 1, 4, 5, and 6 hold up quite well and that 2 and 3 still contain useful information for newcomers to CSS—despite the absence of flex. A chapter on flex is long overdue, no doubt, and chapters 2 and 3 should be written with this in mind. I’ll definitely get to it at some point, but I’d also be happy to collaborate with the community if anyone were interested in submitting a first draft [1]. [1]: https://github.com/adamschwartz/magic-of-css/pulls https://github.com/adamschwartz/magic-of-css/pulls

dlo83 9y ago
Still a wonderful resource, along with You Might Not Need jQuery. Fun fact: I interviewed with you for a front-end developer job in 2013(?) when you worked at a different company in Cambridge. Let's just say: I didn't get the job. You asked me about if I was familiar with X in CSS, and I said something like "well, I've never implemented it, but I've read about it." Your response stuck with me to this day, and I'll paraphrase: "I don't care if you've read about something 'til your face turned blue, you'll never actually learn something until you do it." It stung at the time, but it was the best kick in the ass I've ever received. I took your advice, and am now gainfully employed as a senior frontend developer. Thanks.
chrismorgan 9y ago
I wrote several versions of that sentence and ended up deciding on one of the stronger ones, because I feel that the float/absolute/ruby stuff is sufficiently terrible advice these days—and that flex is sufficiently valuable in understanding how things work. I confess I didn’t pay too much attention to chapters 1, 3, 4, 5 and 6 after that; with a little updating of some of the advice in chapter 3 they’re pretty sound. I apologise for not being more specific in that sentence.

dlo83 9y ago

Still a wonderful resource, along with You Might Not Need jQuery. Fun fact: I interviewed with you for a front-end developer job in 2013(?) when you worked at a different company in Cambridge. Let's just say: I didn't get the job. You asked me about if I was familiar with X in CSS, and I said something like "well, I've never implemented it, but I've read about it." Your response stuck with me to this day, and I'll paraphrase: "I don't care if you've read about something 'til your face turned blue, you'll never actually learn something until you do it." It stung at the time, but it was the best kick in the ass I've ever received. I took your advice, and am now gainfully employed as a senior frontend developer. Thanks.

chrismorgan 9y ago

I wrote several versions of that sentence and ended up deciding on one of the stronger ones, because I feel that the float/absolute/ruby stuff is sufficiently terrible advice these days—and that flex is sufficiently valuable in understanding how things work. I confess I didn’t pay too much attention to chapters 1, 3, 4, 5 and 6 after that; with a little updating of some of the advice in chapter 3 they’re pretty sound. I apologise for not being more specific in that sentence.