your infrastructure should be boring

Recently, my work team listed an infrastructure engineer opening (note: that link will probably rot once the position description is taken down, sorry…). There’s one part of the JD that I’m fairly proud of having written, both because I believe, very strongly, in this approach to infrastructure, and also because I think this gives a great feel for the team and company culture:

At Neochromosome, we think that infrastructure should be fully managed by Terraform, checked into a Git repo, updated by PRs that are extensively code reviewed, and not change all that often. Our infrastructure is not overly complex, and has even been described as “boring” and we like it that way. Our team builds and operates software that enables and supports cutting-edge, potentially world-changing biological research — and our aim is to do that using the simplest possible parts of AWS. If you’re looking for complicated cutting-edge infrastructure work, this is probably not the role for you. On the other hand, if you like looking at an infrastructure and thinking about what parts of it you could simplify, we should definitely talk!

Just wanted to preserve that somewhere where I’ll be sure to be able to get to it again…