The “Last Lecture” is a tradition inspired by Etsy and by Randy Pausch’s book, The Last Lecture, in which someone departing shares their perspective: “What wisdom would you try to impart to the world if you knew it was your last chance?” This version of Sarai’s Last Lecture has been modified to fit your scream.
Hi, I’m Sarai, insecurity princess extraordinaire. You may know me from such hits as
Content Warning: high-level discussion of traumatic events without details, including SA, hate crimes (Pulse 2016, Minneapolis 2020), and grief/loss. The discussion centers validation and empathetic action but may surface survived trauma.
I’ve been through personal trauma and community trauma. What I needed and how I felt varied wildly day to day. Some days, work provided routine and a sense of control. Some days I just couldn’t. I had managers whose empathetic support touched me deeply, and I had managers who hurt me through ignorance.
This is a resource for supporting our colleagues and direct reports through traumatic events. What can we say, how can we help, what should we avoid? …
Let’s, uhhhhh, hash this out a bit, because the distinction between “when is a hash okay” and “when is a hash not okay” is very important for teaching software engineers who will often use hashes in their work.
As summarized by renowned security and privacy expert Dr. Lea Kissner,
“Hash functions are tricky and I’ve seen a lot of people think they throw away all of the information you put in them. But they don’t, which is the precise reason why they’re useful.”
A hash is a “digest”. They identify the data that was hashed in a one-to-one relationship. Hashes have subtle properties that make them useful to attackers, which undermines security and privacy. As Dr. Sophie Schmieg (Google Lead ISE Crypto) remarked, hashes are in a dangerous grey area between “don’t use hashes for anything you want to keep secret” and “a hash is a one-way function with meaningless output”. …