[bionhoward]

Kudos for infrastructure as code. Surprisingly many companies, particularly database companies, don’t deliver infrastructure as code yet, which makes it harder for their prospects to become paying customers.

One way to make your examples better would be to make one block of code with all the commands at the bottom or top of the page, or a link to a Makefile, so the motivated reader can copy paste everything into their IDE at once. Terraform provider docs are great for this: code at the top ... however the code is often limited to just one resource, when the user goal requires a number of resources.

It’s subtle, but declarative programming could mean one of two things: declare the systems to achieve your goal (this is how it usually works right now) or declare the goal. The latter is much better UX for devops folks because the goal is what we care about. You want to host a site, not connect a bucket to a cdn and dns. Declare the purpose, not the mechanism, and everyone saves a lot of time, because there are many micro states (implementation options) per macro state (big picture goal) (entropy 101)