consumed content week ending 03-06-20

Summary

My quest to reduce friction in publishing weekly content continues. I’ve got a template created via yasnippets with some lisp to automatically populate the date. Regardless of when I create the file, the date will always be Friday of the current week. Unfortunately I’m still having to manually grep for my “finished” timestamps. Next on the to-do list is to find a way to automate searching for last week’s timestamps, and populating the fields below. Once that’s done, automating the tag generation for the post should be trivial.

All that being said, I want to be careful to emphasize that my goal is to reduce the friction, as much as possible, that is present in writing and publishing. It is not the idea to automate the entire act, “soup-to-nuts”. The act of purposeful consideration and summation of what I’ve read or listened to is the real benefit in doing this, and will ideally allow the creation of novel and unique ideas of my own.

Content-wise, I definitely enjoyed this week. The podcasts were awesome, and I even managed to read a(brief) research paper from Google. Some awesome blog posts as well, covering things from startup burnout and mental health to software deployment.

Hope everyone has a good weekend, and does their best to stay healthy.

Podcasts

Articles/Blogs

  • How to Deploy Software - A technical deep-dive on operational and technical best-practices in making software deployment as pain-free as possible. As a devops engineer, this topic is near and dear to my heart.
  • Post YC Depression - A poignant article from a startup founder who lived the dream of going to Silicon Valley to run a startup, only to burnout and collapse after an unsuccessful year of 80+ hour weeks. Add this to the growing list of repudiations of “hustle porn” and the idolatry of working yourself to death.
  • Finite and Infinite Games: Two Ways to Play the Game of Life - Do you play the long game or the short game? This post is only a brief summary of the ideas in a book(which I plan to read), but the general idea is infinite players, those that want to continue the game, look to educate themselves for what may come. In contrast, finite players seek immediate power, with little concern for future unknowns.

Papers

  • Meaningful availability – the morning paper - A team of engineers at Google, primarily responsible for the service health of G-Suite services like GMail, wanted a better way to quantify what it meant for their application to be “available”, primarily from an end-user’s perspective. They came up with “windowed user uptime”. This is a great, fairly easy read, and should be of great interest to anyone in the SRE/DevOps space. The only difficult math is if you decide to follow the proof of the metric’s monotonicity.
comments powered by Disqus