Absolutely fantastic. I spend about 30% of my time in Python and 30% in Node.js, using WingIDE and Aptana, respectively. I'm not going to abandon my current IDEs, but this has the potential to change my workflow significantly.

I've never been called "demon," but people are constantly calling me "DAY-MEE-ON."

Ain't that the truth.

Video of the talk can be found here: http://free-electrons.com/blog/abs-2011-videos/

Previous, related discussion: http://news.ycombinator.com/item?id=490851

Does anyone know what kind of "prototyping tools" they're referencing?

I'm not interested in this position, but I am in the middle of creating my first Android app and I'd love to know what additional tools might be available to enhance my workflow (I'm just using Eclipse and JDebug).

Wow, what a shame. There doesn't seem to be any decent Android UI prototyping tools. Looks like Keynotopia is working on an Android app but it's not out yet.

A bunch of wireframe stuff being called prototyping tools, but nothing for interactivity. We'll update the post, thanks.

Awesome. I'm developing my first Android app and this should prove to be very helpful.

I'd imagine that merely asking the potential users if they'd buy now, if it were available, would serve the same purpose.

No, it wouldn't. "Would you buy know?" doesn't select the same people as "Click here to buy now".

From firsthand experience: no, it doesn't.

It's possible they were turning down the terms of the deal. If someone offered me 1M for my site, I'd take it in a heartbeat. If someone offered me 1M and I had to dance nude in the lobby for a year... I'd still take it. But some people wouldn't and observers would say they turned down 1M.

What if your $1MM site was giving you like $10K/mo and was still growing?

The majority of my day is spent working on projects on Google App Engine, so I'm forced to use 2.5.

I have a couple of toy projects in 3.x, but I'm stuck until GAE changes.

Yup, and that will be the same story for some time. Again, we're talking years.

I hire developers from time to time. I avoid the situation you are currently experiencing by asking for a development plan which includes milestones and a requirement for "reasonably" documented source code. After agreeing on a price, the fee is split based on the milestones, and paid as code is checked-in and the milestones are reached. If the developer doesn't meet the schedule or decides to bail on the project, then another developer can pick up where the previous "coder" left off.