Everything-as-Code
You may have heard about this one before: [insert software term here]-as-code.
Examples include infrastructure-as-code, config-as-code, tests-as-code, and now everything-as-code. This practice has been around for a long time but some organizations have been slow to adopt it.
Here's the problem – historically, organizations have had to get expensive specialists to deploy complex environments. They would spend hours going through pages of instructions, line by line, eventually getting the deployment to work. A number of weeks would pass and the organization would like to create another environment, exactly like this one, for further testing. What do they do now? Call the specialist and ask them to come back at a great cost! This is fine, if you like hiring expensive specialists a lot.
So, what's the solution? The everything-as-code practice is simple: you treat every part of a system as you would any other line of code. You write it down...