Or even worse, Frankston.

From my perspective, you might be using take-home challenges incorrectly. The purpose for us is to have something that both sides are now somewhat familiar with, on which to base a technical conversation and ask questions. The actual solution delivered is a small part of the overall value.

Sandbox constraints. Windowing. Browser compatibility issues. Plugins and Integration compatibility.

So you're of the opinion that people who engage in voluntary activities for personal pleasure that put a higher burden on the health system, that those who are more wise about their choices have to use, should not have to pay thier way?

Or are you of the opinion that someone should be denied emergency medical care because they had some sodas on the regular?

You're missing the point. Those who pursue voluntary activities that "burden the health system" don't "pay their way".

Those who pay are everyone else. Healthcare t's a tragedy of the commons unlike other taxes where it's more difficult to abuse the common resource such as roads and other infrastructure.

Roads are frequently built on the expense of the many to the benefit of the few.

So what are you for?

Just need to put it in a big bag of rice.

I might agree with buying, it's pretty damaging with selling though.

I've been thinking about it sometimes and this seems correct. Abolish this law and delay every single selling. Of course I haven't think this through and this may end catastrophically but I'd like to see a simulation.

Because it's unique to the use case, complex, and nuanced. It has to be exactly correct, and it has potentially serious ramifications if the answers are incorrect, potentially with legal ramifications that I'm keenly waiting to see the first cases of.

He's parked in the wrong bay for that charger

It doesn't look like any bay would be correct for that charger.

Why on earth is your state in git? The tool has built-in functionality to handle just these kinds of workflows. This reads a lot like hitting your thumb with the hammer and blaming hammers.

Yes, this. Just supply a few flags to configure terraform backend to store the state in remote storage and encrypt it.

terraform init --backend=gcs --bucket="xxx" --prefix="my-deployment-name" --encryption_key="my-random-bits"

Again, that just puts a bandaid over the problem. You can’t individual audit access to or rotate secrets stored state files.

Presumably one would want to store the state in Git to get contextual diffing “for free” and possibly to avoid a dependency on another system.

If that then create a separate locked down Git repo just for this. Protecting your state file was a big deal when I first reading about Terraform. It was really drilled in.

And that's why many people don't like the idea of a state file. Sure there are benefits, but there are also drawbacks. You now need another system to manage your state. You don't with ansible.

Ansible is a different system, with a subtly different use case. It generally manages a preexisting list of targets. In that sense, there is some initial "state" in Ansible, this being your inventory.

Terraform (or CloudFormation, or Pulumi, or Crossplane, for that matter) shine when you need to create resources. Think of the state as the inventory of what you've created (or imported).

If you think of the resource you are managing with ansible being your AWS account (or your VMWare system, or whatever), then I guess it makes more sense. That state (the account you manage) doesn't really change. (I don't use ansible but that is my understanding)

Having 3 different sources of truth (what is, in AWS, what should be, in the .tf, and something else -- in the statefile) can mean nasty 3 way merges, which i

But I don't manage thousands of different resources, I manage 50. It feels to me that the overhead needed to manage thousand struggles to scale down without bringing all the required baggage. It feels like kubernetes vs docker-compose.

That said, the concept of using an S3 bucked for storing state I saw elsewhere in these comments is an interesting idea so I may revisit terraform.

Not always. I’ve used Ansible to stand up all the inventory that I managed with it.

I didn’t choose it, but my guess is that they didn’t know what they were doing.

Even so, git only exacerbated the problem of secrets being in state files.

One of the reasons that English has been so successful as a global business language is its ability to be flexible and splodgable and still make sense.