Nat? Nat. Nat!


My friend @alexbaldwin has been telling me to do this for a long time, and I figure it is time to bite the bullet.

I'm going to start offering what he always calls "DevOps Super Friends" or more plainly: "Site Reliability Engineer Office Hours".

The idea is simple: I have created an email mailing list, and I'll send out announcements for office hour signups. You can book 30 minute increments, and I'll do any of the following over hangouts:

  • code reviews
  • architecture reviews
  • Advice on deployment tools, scaling, monitoring or alerting
  • Interview Practice
  • Talking about anything else that you think is "DevOps", "Site Reliability Engineering" or "Software Reconnaissance Engineering".

This is just an experiment, so please signup and I'll email out office hours in the next few days!


Email list powered by TinyLetter.



Related Posts

I was playing around with the new and found that it was pretty easy to get a bunch of data about who is donating to what. So I wrote a little script to download the data and figure out how much Google employees were donating to political campaigns from January 1st, 2015 until now.

Google OKRs are pretty awesome. Not everyone in the company uses them, but they really are a great way to measure what you're doing. The thing this article misses though, is how to write good ones. You need to make sure your Key Results are measurable. If you don't have a way to decide if a KR has been completed at any time during the quarter, it's not a good KR.