SREcon18 EMEA

Documentation can often be forgotten when it comes to the pillars of SRE practice; developing tools and new infrastructure has supremacy, and a constant sense of urgency leads to documentation being a "we'll get around to it later" task. Even in places where documentation is actually written, it's often done quickly or poorly in the first place, not maintained, or not organized in a way that makes it easy to use. This can impair onboarding, obfuscate problems, and impair incident response. But if done correctly, documentation can preserve institutional knowledge, streamline incident response, and allow new team members to quickly begin contributing. This talk will discuss the biggest problems surrounding creating, maintaining, and providing utility with documentation, and how to solve them.