Focus on customer value and velocity. Everything else will follow.
- Automate everything uniformly
- Code is the language of collaboration
- Every change is tested
- Security and velocity reinforce each other
- Application choices, then infrastructure choices
- Narrow the paths to production
- Continuously create customer value at velocity
Gaps between silos need to be eliminated.
- Duties - we do different jobs
- Knowledge - we speak different languages
- Process - we do things differently
- Empathy - we don't care about what you do
- Be marvelous at continuously shipping infra code
- Expand this marvelousness to the infra apps that you manage
- Then the same for legacy applications
- Move towards one path for all apps
- It is almost always a dependency problem
- Automation circa 2019 can help with the "modernize and migrate" problem
- Modern management can encapsulate the application and let you move to a modern platform
- Make sure the CIO/CTO knows about your successes
- Involve architecture teams
- Modern application teams should be consuming your infrastructure output
Collaboration through code enables groups with different goals to work together.
Code is the path to trust and velocity.
Conversations are easier around concrete implementations.
- Application
- Middleware
- Packages
- System Libraries
- Operating System
Originally, Chef cookbooks covered all of these - infrastructure centric.
Now, Habitat covers everything except the OS - application centric. Inspec covers the whole stack.
http://chef.io/migration - Free migration assessment
The best way to build software is to do it in close collaboration with the people who use it.