DevOps: Manage the Cognitive Load
Speed, cost and quality are considered the vectors that you can control. If you are moving to cloud to get the “ilities” that comprise quality, you need to seriously consider Cognitive Load.
Speed, cost and quality are considered the vectors that you can control. If you are moving to cloud to get the “ilities” that comprise quality, you need to seriously consider Cognitive Load.
Seems like everyone is clammoring for DevOps folks. Do they really know what they want? That term means all things to all people. Some thoughts.
You will get the most bang for the buck from cloud by destroying it.
Everyone is all on fire about SRE. But what is it really? It’s as easy as 1-2-3 if you boil it down to the basics.
In AWS the AMI ID for a particular VM image is unique to that region. But it’s name is consistent across AWS. When building infra-as-code (such as terraform) use the name, not the ID. And some musings on terraform. Is it still the right answer for infra-as-code?
What exactly is Cloudy DevOps? How do you go from classic data center Enterprise deployments to the cloud? Here’s some of what I’ve learned across a half-dozen teams who’ve done it.