Planning the work for infrastructure engineering organization can be a challenge, in part due to a lack of clarity around what such an organization contributes value to the company it operates within. I have thoughts, and a simple thinking aid, for that.| lethain.com
We often try to force all usecases onto a single internal platform, and I think doing this causes our platforms to age poorly and with an excess of accidental complexity. This post suggests some alternatives| lethain.com
We’d like to give you some additional information about the service disruption that occurred in the Northern Virginia (US-EAST-1) Region on the morning of February 28th, 2017. The Amazon Simple Storage Service (S3) team was debugging an issue causing the S3 billing system to progress more slowly than expected. At 9:37AM PST, an authorized S3 team member using an established playbook executed a command which was intended to remove a small number of servers for one of the S3 subsystems that i...| Amazon Web Services, Inc.
There is a moment in every company’s growth when top-level planning shifts from discussing specific projects to talking about goals. This can be a very empowering moment because goals decouple the “what” from the “how”, but it can also be a confusing transition for everyone involved: writing clear goals takes a bit of practice. This post takes a look at how to write effective goals and how to use them during planning.| lethain.com
Migrations are both essential and frustratingly frequent as your codebase ages and your business grows: most tools and processes only support about one order magnitude of growth before becoming ineffective, so rapid growth makes them a way of life. This post takes a look at why migrations are so important, and also how to run them effectively.| lethain.com
