Chapter 94. Read the Documentation—Then Reread It
Jennine Townsend
Moving to the cloud can really reduce the number of infrastructure vendors you’ll need to keep an eye on. But you can’t slack off on reading documentation, since understanding your cloud vendor is as important as understanding all those others used to be, combined, and if you don’t know about a feature, it might as well not exist.
But even if you read the documentation, another challenge remains: cloud providers are constantly working to improve their offerings. In many cases, the improvements will appear as new services or splashy new features, and you’ll find out about them in the normal course of keeping up. Follow all the vendor’s tech blogs! But often the improvements are to a service you aren’t now using, or you just don’t happen to notice the announcement, or maybe it never gets officially announced. How can you know to use a feature you don’t know exists? Even the infrastructure you’re already using may be changing right this minute! The documentation you read last month might already be out of date.
It’s helpful to have a strategy. Brain upgrades require as much intentional planning as any others.
DevOps practitioners already ought to have a good understanding of infrastructure costs and the contribution of various technologies and projects to the overall costs. Always keep up with ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access