This is less about saying farewell to Estes Park than it is about a ride I’ve been eyeing for over five years. Not only did I have the wrong bike when I was here in September, 2015, but I learned that this route existed the day after I finished an out-and-back run of Trail Ridge Road on my old Giant roady. TRR is the downhill paved segment of today’s route.

Where am I? I’ve been wanting to write about what I’ve been up to the past couple of months and keep putting it off because I convinced myself that I need to write a long and protracted post about why I’m living in a travel trailer. Oh yeah, I live in a travel trailer now. But I don’t think I’ll delve into why I felt compelled to leave NYC and become trailerfolk because it’s really not that profound or interesting.

This is mostly a note to my future self since I couldn’t find any documentation on using Terraform with Linode Object Storage as a Terraform state backend. With that said, I hope to save other intrepid Linode users some time if they’re lucky enough to come across this post. While I’ve explained the problem in terms of Linode, the solution here applies to any non-S3 object store compatible with the S3 API.

Hey all, just a quick post about di-tui, my new di.fm terminal UI player. I’ve been playing hours of music with this player over the past two weeks and have to say that I really love it and am proud of its ease of use and simplicity. Most people who know me know that I work almost exclusively in the terminal: tmux, mutt, slack-term, vim, and now di-tui and many more.

Shipping production software requires a lot of housekeeping; so much so that many developers mentally block out just how much time a day they spend endlessly shepherding their work through the release lifecycle. Does the pull request have merge conflicts? Are tests passing? Is the linter happy? Is some other automated check failing? Most of these failures require intervention; whether it’s a finicky spec failing in a test suite or something more serious like a merge conflict.