"You can absolutely write bad Pulumi code. You can over-engineer it. You can create abstractions nobody understands. You can make something simple feel clever for no reason.

But that is not a Pulumi problem.

That is a software design problem."

An uncomfortable idea is that these are basically the same thing. There's a reason the phrase "just enough rope to hang yourself" exists. A system that requires more software design <can be> a problem in and of itself.

It's pretty much ubiquitous to me.

And, BTW, I usually joke Terraform had bugs before the first line of code was written. What's even the point of caching a state if the state can be changed behind Terraform's back.

undefined

Feels like a shill article for Pulumni.

I am not bashing Pulumni, or glorifying Terraform, but the examples shown in the article are simple, and do not proof any of the mentioned advantages.

Seemed like trash when I used it

Terraform was always been trash. It lacked functionality it said it had on the tin. Hashicorp was good at marketing