Perhaps, like the uber/lyft light-on signage, when FSD is engaged some sort of visual cue should activated on the exterior of the vehicle. It can be subtle like an extra set of LEDs eliminated either on the front or back. The end effect might be that other drivers will make it more predicable for FSD to safely navigate.
But I as one of other drivers should not have to change my driving habits just for elon to make more money.
No, Ansible or Terraform by themselves are terrible. Together they will collapse into a singularity of awful which will consume the world into a goo of self-replicating YAML.
Terraform is hard because it can be a different way of thinking about deployments and your infrastructure. And since it's declarative you can't do conditionals in normal ways.
What I used to do is create things in my target environment then try to recreate them in terraform (without the import, because import didn't really work so well). Then do an apply/plan and see what changes were listed.
What I would do today is ask ChatGPT for terraform for specific things, then see what it outputs, compare it with the registry, then do the apply.
Terraform is half the battle, the other half is figuring out how the specific provider represents their stuff...which is why ChatGPT is helpful.
Oh, and also look at your provider's examples. You presumably know how things work in your provider, so looking at their terraform registry will help you figure out how they model stuff in terraform so you can model your stuff in terraform.
If my 2p is worth it, I believe this framework is dynamic. This means that, on a quarterly basis or per project, members will organically slot into the mentioned types. Managers should be cognizant of this and allow it to happen, rather than fighting the natural order due to biases from past outcomes. There are rare situations where a manager or group has to explicitly slot people in.
Lastly, I like the content of this framework, and it reminds me a lot of "Total Football."
