r00k

However, you've got another big win waiting for you if you'll try something subtly different: write the tests first. Moving to TDD was another large improvement in my overall productivity because it drastically improved the quality of the code I write.

It seemed silly when I first heard of it, but now I won't write code any other way (except for short, exploratory programs). Give it a try!

I'll rerun the survey on a screencast post.

You can buy it once and use it as many times as you like.

"UI" refers to a landing page and checkout form that we pre-built and include with the app. We didn't do a good job of making that clear, and that's something we want to improve on the sales pages.

Your question about bugfixes is an excellent one. Eventually, we'll be moving this to an engine/gem, but for now you'd have to make manual changes. This is far from ideal, so we're planning on fixing it.

This is just for one time purchases. We'd like to add support for recurring billing at some point, but it's not planned for the immediate future.

Thanks for your feedback on the price. As this is at MVP stage right now, everything can possibly change, including that.

It's fixed now.

I've got good coverage with unit tests and cucumber features.

The tests do things like bang on the credit card form in a bunch of ways and make sure things work correctly. The integration tests actually hit Stripe's test servers to ensure that payment processing is working correctly.

Thanks!

I've found that with sufficient narration, I don't need it.

I'm the author of the site and totally agree that RSS is desperately needed. It's next on my list.

If you do map something on top of it, consider moving it elsewhere.

Once.

And then you could use shorter, more convenient syntax for the rest of your life. Worth it?

I never fully grokked Ruby's object model until I read that book.

I reread it often and always discover/re-discover useful information.

This sort of thing will likely be surprising to someone new to Rspec. However, as a general rule, I don't think it's fair to knock tools because they're a bit tough for new users to understand. Someone new to vim is hopelessly lost and slow at first, but I can fly with it, because I've taken the time to learn it.

Yes, I had to invest some time to learn about Rspec's 'be_' construction; yes, it confused me at first. However, having learned it, I always use it now. I really enjoy the readability of the code that results from it.

As in many things, there is a tradeoff here. It's fair for both of us to argue that we prefer to sacrifice different things.

If Twitter could have deployed the bar to a hundred or so real users, I think they would have quickly found that people mostly hated it.

I believe you're allowed to distribute test versions of your app to 6-ish handsets for testing, but I'm sure this barely covers the internal folks at Twitter. It'd be nice if they'd had the option to do some more thorough early testing. (Whether they would have done so, or would have listened to the results is outside my point).

The trick is to subscribe just to the subreddits that match your interests. If you'd like a searchable list of them, this appears to be a good resource: http://www.subreddits.org/search.html

One request: keyboard shortcuts.

If you'd like people to play a bunch (and I imagine you would), this would be a nice touch.