> For instance, if you can standardize on `make setup`, `make test`, `make docker`, etc. on all of your organization's code, it's very easy for a new develop on a project to start contributing quickly.
This is the real magic trick. In fact you can even go one step further and standardize on just one command: `make help`. Then you walk over to your QA lead and say "Clone the repo, type `make help` and if anything about setup, deployment etc. isn't clear or doesn't work, log a bug." Now your infrastructure is subject to your regular software development lifecycle. You have achieved "Infrastructure as code" with a tool that was authored in 1976.
This is the real magic trick. In fact you can even go one step further and standardize on just one command: `make help`. Then you walk over to your QA lead and say "Clone the repo, type `make help` and if anything about setup, deployment etc. isn't clear or doesn't work, log a bug." Now your infrastructure is subject to your regular software development lifecycle. You have achieved "Infrastructure as code" with a tool that was authored in 1976.
Unreasonably effective.