はてなブックマーク

charity.wtf charity wtf's about technology, databases, startups, engineering management, and whiskey. Lately I’ve been doing some career counseling for people off Twitter (long story). The central drama for many people goes something like this: “I’m a senior engineer, but I’m thinking about being a manager. I really like engineering, but I feel like I’m just solving the same problems over and over

charity.wtf charity wtf's about technology, databases, startups, engineering management, and whiskey. Last night I was out with a dear friend who has been an engineering manager for a year now, and by two drinks in I was rattling off a long list things I always say to newer engineering managers. Then I remembered: I should write a post! It’s one of my goals this year to write more long form instea

charity.wtf charity wtf's about technology, databases, startups, engineering management, and whiskey. Hey kids!  If you’ve been following along at home, you may have seen my earlier posts on getting started with terraform and figuring out what AWS network topology to use.  You can think of this one as like if those two posts got drunk and hooked up and had a bastard hell child. Some context: our t

charity.wtf charity wtf's about technology, databases, startups, engineering management, and whiskey. Last week was the West Coast Velocity conference.  I had a terrific time — I think it’s the best Velocity I’ve been to yet.  I also slipped in quite late, the evening before last, to catch Gareth’s session on DevOps vs SRE. I had to catch it, because Gareth Rushgrove (of DevOps Weekly glory) was t

charity.wtf charity wtf's about technology, databases, startups, engineering management, and whiskey. I’ve been using terraform regularly for 2-3 weeks now.  I have terraformed in rage, I have terraformed in delight.  I thought it might be helpful to share some of my notes and lessons learned. Why Terraform? Because I am fucking sick and tired of not having versioned infrastructure.  Jesus christ,