Everything as Code

The idea here is to make everything visible and allow anyone to see how things are configured and make changes to them if needed. This makes things more reproducible, it also reduces the cost and speed of a change. Changes can be reviewed and discussed in a normal workflow compared to doing things manually without a quick way to revert changes.

The idea here is to allow all changes to go through the same tooling and review process as every other piece of code. This can help make it easier to reproduce environments and verify the current state of everything from infrastructure to code. Making updates or changes easier and less stressful for the people making the changes. It also helps preserve history and make rollbacks or other changes easier across your whole system. It makes it easier to share knowledge and get people up to date on what things look like and what changes were made.

Instead of having to update a wiki or some other place you have have discussions and review changes like you do with any other changes to code that you would normally make. This make is easier to understand the progression of changes and can give you reasoning behind changes that might be hard to find in wikis or docs. It also means that all of your changes can be visible through your deployment and validation systems. Giving you more confidence and also providing everyone else visibility as changes are rolled out.