It's been about 4 years since I took a compilers course (from OMSCS, graduate program) and still shutter ... it was, hands down, the most difficult (yet rewarding) classes I've taken.
Really interesting format (and appreciate him / Guido being explicit about preferring written prose over [audio] podcasts).
> I remember my niece had a problem with it because her son wanted to drop out of school and pointed to me as, look, I don’t meet school, look at Thomas. And I had to go, no, no, no. I was in a unique situation where the industry was open to anyone who could do the work and I could do the work. That’s not the case anymore. So you have to finish school.
Reminds me of this YouTube video (below) on how difficult it is (nearly impossible) to re-learn how to ride a bicycle when you have the handles are reversed (i.e. pulling left handle bar towards you, the wheel goes to the right)
> As a precautionary measure, the hospital followed mandatory reporting statutes and my wife and I temporarily lost custody of David. Thanks to our incredibly effective defense lawyer, we were cleared of all charges within two months, during which we stayed at the hospital 24/7 with David until we sorted out the legal procedures.
Holy shit. Parents bring baby to ER ... results reveal that baby was shaken (article later confirms this was not the case) ... parents lose custody for 2 months. Horror story.
> Recent reports that these exploits are caused by a “bug” or a “flaw” and are unique to Intel products are incorrect. Based on the analysis to date, many types of computing devices — with many different vendors’ processors and operating systems — are susceptible to these exploits.
I wonder how this will play out since it seems that everyone, apart from Intel, view this issue as a "flaw".