"Terrorform"

This is going back 20 years, but I once praised a colleague for his legible Perl code.

Once. 🤣

Terraform is the new Perl

They never do.

Let's put it this way...I was last there in 1994. Thirty years later, they are an indelible, fond memory. I can picture it like it was yesterday.

Bryce is wholly magnificent, and Zion unreal. The Narrows in summer is one of the greatest places I've ever been.

That's a good way to think of it!

kinto.sh

👍

Link is broken...would love to read this post.

`run` and `exec`

Fwiw, this also applies to registration. I once lost out on early bird pricing because I forgot about timezones.

Lots of interesting work happening in this space. I am hopeful that we might soon be able to abstract away, yet another, layer of complexity that has been driving immense amounts of developer toil.

If we define platforms with an abstracted specification outlining a resource's inputs, outputs, and even side-effects, it doesn't matter what the underlying implementation is.

Keep your Chef, Ansible, or whatever god-forsaken thing you prefer. Those are now just implementation details.

Exactly. The reason why platforms have, largely, failed to deliver is that they have lacked strong contracts by way of APIs.

Yes, everyone could build the infrastructure with a new, shiny tool, but all we got were bespoke half-measures.

It's so easy to think that your "too basic" presentation would be, well...."too basic."

IME, these are the best ones. What each of us sees as "too basic" is, very often, exactly what someone else needs to get to the next level.

Like some weird inversion of impostor syndrome.

Sometimes you'll even get something like "I can just do that with script/config management/whatever."

When you move beyond just deploying a container, you get crickets:

How do you create load balancers?
How do you manage volumes?
What about DNS?
And certs?

You're right back at bespoke complexity.