I had taken my kids to see DuVernay's superlative Selma years prior, and I had heard about 13th (and I had recalled my wife saying she wanted to watch it), but it was – like many things – "in the queue."
A post urging readers to watch Ava DuVernay’s documentary in the days after the murder of George Floyd.
Let me close by offering a sincere thanks to those in the Rust community who have been working so long to develop such a terrific piece of software – and especially those who have worked so patiently to explain their work to us newcomers.
A long account of learning Rust, ending with the resources he recommends to newcomers.
Since reading it over two decades ago, I have recommended The Soul of a Machine at essentially every opportunity, believing that it is a part of computing's literary foundation – that it should be considered our Odyssey.
A post about re-reading Tracy Kidder’s book two decades after it set him on a career in computing systems.
If you were as I was and are contemplating diving into Rust, a couple of pieces of advice, for whatever they're worth: I would recommend getting both The Rust Programming Language and Programming Rust. They are each excellent in their own right, and different enough to merit owning both.
A long account of learning Rust, ending with the resources he recommends to newcomers.
not only did I buy the canonical reference (The Rust Programming Language by Steve Klabnik, Carol Nichols and community contributors), I also bought an O'Reilly book with a bit more narrative (Programming Rust by Jim Blandy and Jason Orendorff).
A long account of learning Rust, ending with the resources he recommends to newcomers.
Check out the New Rustacean podcast by Chris Krycho. I have really enjoyed Chris's podcasts, and have been working my way through them when commuting or doing household chores.
A long account of learning Rust, ending with the resources he recommends to newcomers.
And amazingly enough, if you insist on looking at the world through a bucket of shit, the world starts to look an awful lot like a bucket of shit: by the end of the book, Rosenberg has left the lay reader with the sense that we are careering towards some sort of software heat-death, after which meetings-about-meetings and stickies-on-whiteboards will prevent all future progress.
A post explaining, at length, why he panned Scott Rosenberg’s book in a Google Tech Talk.
Every entry is a verbatim quote and a link to the public post it came from. Nothing is paraphrased. If it is not on record somewhere public, it is not here.
The verdict is what they actually said: loved and liked are explicit; recommended means they told others to get it; uses means they only say they use it; read is a book on their public shelf with no verdict; mixed and disliked are kept too.
A dashed affiliate link, sponsored or their own label means the post disclosed a relationship. It is shown, never hidden.
The shading behind a date shows how dated a recommendation is for its kind of thing.
The shading behind a date shows how dated a recommendation is, for its kind of thing. Fully green is recent. It drains a quarter at a time as the post gets older, and is empty once it reads as dated.
What counts as old depends on the thing. A laptop praised four years ago has been replaced twice; a book loved twenty years ago is probably still loved. The shading is gone after about:
Hardware, services4 years
Software5 years
Podcasts, courses, other8 years
Books25 years
Stripes mean the post carries no date and the date shown is an estimate. No date at all, no shading.