One way I can think of that will solve this problem is to do something like:

    resource "aws_instance" "nomadclients" {
      ami = "${count.index > 2 ? data.aws_ami.nomadclient_tick.image_id : data.aws_ami.nomadclient_tock.image_id}"
      instance_type = "t2.micro"

      count = 6

      iam_instance_profile   = "${aws_iam_instance_profile.consul-join.name}"
      subnet_id              = "${element(aws_subnet.consul.*.id, count.index)}"

      vpc_security_group_ids = [
        "${aws_security_group.rule01.id}",
        "${aws_security_group.rule02.id}",
        "${aws_security_group.rule03.id}",
        "${aws_security_group.rule04.id}",
      ]
    }

The downside to this approach (in TF < 0.12), however, will become apparent when you want to modify the number of instances in one or both pools. This arrises from the way hcl v1 manages the counter index with each resource in the state; That is each resource is linked to a specific index and when that index is altered in someway, terraform will attempt to adjust the resources at each respective index accordingly.

Because of these headaches, we decided to abandon hcl for these use cases and ended up writing our own preprocessor that takes a JSON configuration and generates individual JSON-based HCL (ie. .json.tf) that terraform can then use. We can leverage proper templating to generate many variants of a single resource in a higher level language, while still using terraform to manage the infrastructure and it only adds one additional step to the plan + apply process.

Alternatively you could put the AMIs in an array, and just iterate over that array.

  locals {
    nomad_ami = [
      "${data.aws_ami.nomadclient_tick.image_id}",
      "${data.aws_ami.nomadclient_tock.image_id}",
    ]
  }

  resource "aws_instance" "nomadclients" {
    count = 6
    ami   = "${element(local.nomad_ami, count.index)}"
  
    ...
  }

I'm sorry, but the safety features in question here were software upgrades. The incremental cost to Boeing to add it to every aircraft during manufacturing would be negligible.

In my view it should be criminal to withhold such safety features for profit.

This is really awesome. I just killed about an hour playing it part way through.

I was saddened by the fact that I lost progress when I left the page. It would be nice if progress could be save via cookies or something.

One other thing that would be nice is the ability to offer hints. These could even be just an external link to relevant material on wikipedia or equivalent.

If only it were that simple.

Unless you've physically removed or disconnected the wireless interface, there's still a chance that a firmware vulnerability could lead to your TV being hacked via a remote and/or side-channel attack similar to what was demonstrated in the article.

A lot of these systems were built such that date stamps were simple 6 character text fields within a larger ascii-based file format on computers build in the 60s and 70s or earlier.

Space (both RAM and storage) is a premium on these systems and therefore much thought is given to what you place within any given row. As a result, no one stored unix timestamps as that would have required 10 characters more per timestamp per row, which would have had other ramifications on other parts of the code and/or memory. It would have required all stored records to be re-written somehow, which depending on the available online storage may have been an impossible task in and of itself. Not to mention how one would handle the recovery of any existing backups.

Due to these complexities, most organizations settled for code that shifted the meaning of the 2 digit year by some predetermined offset.

I feel that part of the problem here is that booking sites don't tend to be fully transparent on how much any given flight really costs, beyond the initial ticketing cost. Extra costs are typically hidden and the UX is optimized for finding the cheapest possible ticket price, ignoring fees and overhead.

Tangentially, in some ways, its a fact of reality in the US that the price you see will almost never be the price you pay, which is generally higher. Americans seem to accept this as a norm and it still baffles me even after 17 years.

The thing I don't like about such plugins is that it suppresses the conversation surrounding the practice of forced removals and overbooking in general and the incident in particular.

A much better approach would be to be vocal about your choice and why it was made through common social media outlets. Even simple posts that express your decision to boycott and why help drive conversation around what's happening.

Besides, if you genuinely intend to boycott United why would filtering results make a such difference? Are people worried that seeing their prices may convince them otherwise?

Free market and competition in health care, really?

Delivering the same level of care and services for everyone is at odds with the notion of a free market. How exactly are providers to compete, over the long-term, when everyone demands the same level of care at the same cost or better?

Agreed.

I don't have a problem with airlines creating cheaper seats that they can market to a segment of customers.

What I do have a problem with is the lack of transparency of what you're getting when you attempt to research and compare fares. In my opinion, this is what the government should focus on.