We can't populate those other dropdowns at that time because they're based on real values. Here's what a filled-in set looks like: http://i.imgur.com/tMLtncD.png

Well then I would recommend a video or screenshot instead, or just populate with fake data. I personally just wanted to see what the possible values could be.

I know the service is new so I am giving you the benefit of the doubt. But if I came to your website from Google or a news article, I would be immediately turned off by that giant sign-up popup.

Thanks, we're going to address this in the next release.

No problem. I do see the service being useful and I think it has potential.

Right now the automation is done by a service (no autoscaling groups are created on your behalf). Do you have triggers in mind that you would like to create autoscaling groups for you?

No I mean that AWS provides a lot of this sort of automation internally, for example by configuring autoscale groups to respond to various cloudwatch metrics. I was wondering if finally.io is a UI layer on top of the existing AWS tools.

Our initial set of automation rules consists of things that are not readily doable with autoscaling. We do use the AWS APIs but I wouldn't consider what we do to be a UI layer. We automate things that are currently hard or impossible to do with the AWS console. A great example of this is scaling RDS storage or DynamoDB capacity based on actual use (and not just as a one-off operation).

Palo Alto, CA - About.me (parent company is Aol)

Help make public identity on the web more beautiful.

We're looking for Javascript and Python developers.

Email me with your information: luke@about.me

The Python analog would be something like this:

assert (object() < object()) == False

(try running this in the interpreter a few times)

Not really.

The example given is equivalent in badness to:

  g = Timer()
  assert g.startTimer() == 0

... and then wondering why the timer doesn't start when you run your program in "optimized" mode.

Woah... so this is coercing it to a string and the address in hex is being compared. Am I off on this?

Yes. Python is not that mysterious.

For generic objects, the __lt__ and __gt__ methods are simply defined the only way that's sensible, which is effectively as a pointer location comparison.

We're an AOL company now but I think that wording is reasonable.

I'm more interested in a Q&A with Watson about Ken Jennings

It'll probably read Ken's wikipedia page out loud.