Spencer Krum

Title: Code Review for Operations


Code review has always been used by developers, recently operations has started as well. How is it different when operators are reviewing code that has an operations impact? How can it be optimized? Our team has been reviewing ops code for years, and I'm here to share the lessons we learned.


Spencer Krum

Spencer Krum


Spencer (nibalizer) Krum (http://spencerkrum.com) has been sysoping Linux since 2010. He works for IBM contributing upstream to OpenStack and Puppet. Spencer is a core contributor to the OpenStack Infrastructure Project. Spencer coordinates the local DevOps user group in Portland and volunteers for an ops-training program at Portland State University called the Braindump. Spencer is a published author and frequent speaker at technical conferences. Spencer is a maintainer for the voxpupuli effort(https://voxpupuli.org), which attempts to bring together a network of Puppet developers, modules, and infrastructure.

Spencer lives and works in Portland, Oregon where he enjoys tennis, cheeseburgers and StarCraft II.