To connect the dots, Mitchell is the creator of terraform. And honestly, I kind of feel the same. I think it points out that even if you "feel" it as the creator, that doesn't mean others will feel the same way, necessarily.
I get the feeing you're looking at this through the specific lens of a programmer. Terraform isn't made for programmers - you'll miss all the flexibility a real language gives you. It's made for ops people who deal with wrangling a whole bunch of different types of systems with different API's and languages and just need some way to standardize the management of disparate systems, whatever counts as "infrastructure".
The state file thing gets a relatively large part of the hate but it's that and the limitations of the DSL that make the DAG possible and useful. Pulumi and all the other wrappers don't solve this, though they can plausibly solve the "closer to programming" problem and I'm sure that has a valid audience.
I guess what I'm saying is, I think it'll stick around and we will in fact settle on it for a large part of operational work. I'll add that I also think k8s should die a quiet death and _that_ will be seen in retrospect as a necessary step to something better.
Not a popular opinion I know, but I really like writing Terraform in HCL2. Like, if I’d invented this, it’d give me the feels and I’d want to share it.
I quit a $400k+ job to get away from IaC. I loath yaml. More and more, my day was filled with "you have an error on line 1, good luck." It was more k8s than tf, but I get the same sneer on my face when messing with tf.
I refuse to let such a shitty experience be what defines my day.
I was hoping pulumi would help. Haven't used it yet, but it is sad to hear it doesn't live up to the hype.
Managers of 15 shouldn't make lots of decisions. The team should come together and use decision processes to make good decisions. Manager makes sure individuals are growing and are able to contribute at that level.
I agree with you. Based on what others have said about this article, it sounds like Google doesn't agree with us.
If anything, I would go further than the "two pizza" team sizing. Teams should be no larger than 4 people, one of whom is a lead who is extremely well compensated and is held to extremely high standards, else they are shitcanned ASAP.
Small team management is dead. Long live small team management. Yes. You fire them then your senior engineers fill that gap. Its just not formally part of the process. The cost didnt disappear. Either borne by employees working longer hours or lost velocity.