What do you do if its the late 1950’s and you need to project live video? Overhead LCD projectors–let alone the computers to drive them–haven’t been invented yet. The answer is the Eidophor, the most bonkers overhead projection system you’ve probably never heard of.
Every since I started giving my High Performance Go workshop I’ve been fascinated with the physics of semiconductors. This presentation from Hope Conference ’09 doesn’t cover the latest EUV shenanigans, but does an excellent job of detailing the difficulties in semiconductor manufacturing ten years ago. The problems have only become more complicated as semiconductor fabs attempt to push feature sizes into the single digits.
As the tech lead on non SaaS product I spend a lot of my time worrying about testing. Specifically we have tests that cover code, but what is covering the tests? Tests are important to give you certainty that what your product says on the tin is what it will do when people take it home and unwrap it, but what’s backstopping the tests? Testing lets you refactor with impunity, but what if you want to refactor your tests?
This presentation by Ian Cooper takes a little while to get going but is worth persisting with. Cooper’s observations that the unit of the unit test is not a type, or a class, but the API–in Go terms, the public API of a package–was revelatory for me.
A fascinating wide ranging interview with Dave Cutler, the creator of RSX-11M, VMS, and Windows NT.
Bonus: Show Stopper!: The Breakneck Race to Create Windows NT and the Next Generation at Microsoft. The book on the early history of the creation of Windows NT.
An excellent talk about the importance of simplicity in the language which is anything but:
The interaction between career development and on-call is actually really, really, bad. Bluntly, the profession takes on-call seriously, tries to be good at it, yet it is very very rare for this to be rewarded in any meaningful way. In 11 years at my previous employer, I never saw anyone get promoted for on-call performance.
One of my favourite talks from the elusive Systems We Love conference series.
Ousterhout’s opus is tearing up tech twitter at the moment. But for those outside the North American prime shipping service area, we’re shit out of luck until a digital version is available. Until then, here’s Ousterhout’s Google Tech talk:
“It turns out that style matters in programming for the same reason that it matters in writing. It makes for better reading.”
— Douglas Crockford
I stumbled across this old (in internet years) presentation a few weeks ago and it’s been on high rotation since. If you can look past the recording difficulties (and the evacuation siren) this presentation is chock full of sound advice applicable to all programmers.