It maybe a good framework for writing applications, but since so much of the tech industry has run away from it for years it hasn't kept up on other areas like deployments and debugging. Lots of things are 3-5 years old.
I also liked it about eight years ago, but the developers still using it like to use all the sugar and auto-magic. Which leads to spaghetti code.
He has a real point, but it doesn't really give a good alternative other than "read my book".
The crux of the problem when writing Terraform code is that it doesn't have if statements. Without them you end up doing hacky things to try to recreate them. Environments are not all going to be exact replicas of each other for 100 different reasons, and so trying to use the exact same code for each just doesn't work.
I don't consider dynamic/for_each an elegant solution with the current syntax.
Terraform leads to this pattern. Unless you can make your environments exact mirror images of each other, this is what you end up with. Almost no one does exact mirror images for cost reasons. Every environment would have to be at production scale.
I would say it is still a common pattern. I don't see how workspaces really improves anything. The fundamental problem with Terraform is it lacks if statements. There are solutions that involve dynamic blocks and for_each, but I don't think they completely solve the problem. I would say they don't have great readability.
I would love to hear a reasonable way to not snowflake that doesn't dive down the dynamic hole.
Overall I think this is all an argument for Pulumi over Terraform.
I just got a new System76 laptop for work. I have used to Lenovo P Series in the past. The System76 laptop has a Nvidia GPU. For ports it has HDMI and Mini DisplayPort. I was expecting dual 4k@60hz to work, but instead got 4k@60hz via the Mini DisplayPort and 40@30hz via the HDMI. The reason is the HDMI is tied to the Intel GPU, not the Nvidia GPU.
The laptop also lacks Thunderbolt, which would provide more port options.