Drew

What I Read in 2023 (Q1)

Shards of Earth (The Final Architecture, #1) by Adrian Tchaikovsky. This was a big book, both in terms of the number of pages and the scope of the story. Humanity has spread throughout the universe. The Architects—strange, moon-sized entities that destroy entire planets—are back. I really enjoyed the concept of Unspace—a plane of un-reality where faster-than-light travel is possible. Interesting science, great character building, and a complex and enjoyable plot made this one of my favorite books on the list.

What I Read in 2022

The Library at Mount Char by Scott Hawkins. This was one of my favorite books this year! It was bizarre and surprising and horrifying at times. I’ve yet to read a novel with such breadth that was so neatly woven together.
Piranesi by Susana Clarke. Imagine a house with infinite rooms full of thousands of statues. Imagine this house contains an entire ocean. Now imagine you live there. Piranesi was awe inspiring. I couldn’t put it down.
Breath by James Nestor. This book literally changed my relationship with breathing. It also helped me improve the quality of my sleep! If you want to know more about the science of breathing, and why it’s fundamental to our well-being, check it out.
Hyperion by Dan Simmons. This book has been on my reading list for years. I finally picked it up this year, and once I did I couldn’t put it down. There’s a reason this is a classic in the sci-fi genre.

Setting aside time to write is hard, though. I think I still haven’t adjusted to having kids after eight years. Making time to write requires sacrificing precious time with my kids, and that feels scary. Regardless, I think a little sacrifice might be in my best interest, so here goes.

I learned a lot about myself this year. I grasped that being truly present takes effort, but it can be transformational. I accepted that I am a deeply emotional being after decades of convincing myself otherwise. I discovered that until this year, the only emotion I truly embraced was anger. Finally, I realized that some of my strengths—the parts of my identity that I was most proud of—were keeping me from what I wanted most. After thirty-four years, I thought I had myself mostly figured out, but this year set me straight.

I’ve spent countless years pursuing mastery. It took me all those years to realize that what I really want is mastery of my own experience. Having discovered this, I’m genuinely excited for what’s to come. Next year, I plan to continue my journey to become the best version of myself I can be. Hopefully I’ll set aside time to tell you about it along the way.

Foraging in Washington

Yesterday, I spent the day in the Gifford Pinchot National Forest learning about fungi.

Into the Fediverse

This blog is now federated!

Backward Progress

Today I found myself needing to use the comm utility to compare two 20GB files. This ended up taking about 10 minutes and while it was running I got curious at how much time was left. Knowing that comm must read through both files before it finishes, I decided to see if I could build a simple progress indicator based on the read offset of one of it’s file descriptors.

Bash Argument Parsing

Bash is a wonderful and terrible language. It can provide extremely elegant solutions to common text processing and system management tasks, but it can also drag you into the depths of convoluted workarounds to accomplish menial jobs.

Simple Git Push Deploys

I recently got interested in supporting Heroku style push deployments in the AWS stack at Fullscreen, Inc. There are a few solutions for this in the wild like Dokku, but I wanted to use something flexible enough to grow with our deployment infrastructure that wasn’t dependent on container technology. The solution I came up with involves a deploy server, a Git hook and a bit of Bash.

Actual Zero-Downtime with HAProxy

The internet is rife with promises of 100% availability when using HAProxy for load balancing. THEY ARE LIES!

Cherry Picking Logs in Git

The git commit log is one of the best tools for understanding the history and direction of a project. I’ve found there are a ton of situations where the log can make complex interactions with a repo a breeze.