Describing fault domains.

August 17, 2019. Filed under infrastructure 34architecture 26

Fault domains are one of the most useful concepts I've found in arhcitecting reliable systems, and don't get enough attention. If you want to make your software predictably reliable, including measuring your reliability risk, then it's an extremely useful concept ot spend some time with.

Head in the clouds.

July 7, 2019. Filed under infrastructure 34cloud 3

When I wrote about the public cloud expansion forcing infrastructure engineers to evolve their role, I sort of imagined that the precursor question--should we run our infrastructure on the public cloud?--was already quite settled, but it's a discussion that I find myself having more rather than less frequently each year, so I've taken some time to structure and document my thinking.

Notes on Escaping the Build Trap

June 30, 2019. Filed under review 13book 11product 5

Last year while thinking about product management in infrastructure I read Cagan's Inspired, which I thought was a very solid book. I just finished reading Perri's Escaping the Build Trap, which is similarly excellent, and I've written up some notes.

Some career advice.

June 22, 2019. Filed under career 11

One unexpected perk of publishing a book is that folks start to ask you questions about all sorts of loosely related things. One pretty common thread has been around career advice, I’ve written up most of my advice for easier reusability. Some of the ideas are a bit contradictory, which I suspect is the nature of all useful advice: you’ll have to work through the conflicts and details yourself.

Running systems library as Cloud Function.

June 16, 2019. Filed under systems 4cloud 3gcf 1

I was chatting with my friend Bobby Powers and he mentioned a systems dynamics app he's been hacking on. That conversation inspired me to want to finish a project I've been neglecting, which is exposing the systems library as an HTTP endpoint running within a Google Cloud Function.