ndelage

The last few times I've gone to my local pharmacy (Rite Aid) I've watched a single cashier operate more than one checkout registers at a time. She did this because it took so long to process payment and print a receipt -- e.g. while she waited for my payment to go through (via credit card) she'd ring up the next customer on another register.

She's trying to ring up the most customers per minute possible and using a second register helps her increase her checkout rate.

It's not unusual that I spend more time waiting to check out than I do actually shopping. I'd love solutions like "just walk out" since my experience lately seems to be something along the lines of "grab what I need and stand in line unnecessarily".

Doesn't the article discuss how it's already been outclasses in real world tests by existing jets like the F-16?

Capabilities on paper are useless if they don't deliver in real world usage.

I usually start with Sinatra (without a DB). Instead of an ORM & DB I'll create simple Ruby objects in memory. Maybe I'll have a Post class with an #all method. Similar to AR, but I'll hold off actually creating a DB.

As a prototype (I'll be throwing this code away) this approach works well enough to simulate how the real app might work. Mimicking some of the conventions I'll be using later makes the transition easier.

I avoid a CSS framework when prototyping. I might pull in jQuery if it's essential.

Hi, i'm part of a tiny startup working on a subset of this problem, and would love to pick your brain on a few of the challenges you mentioned. If you're willing to help out with some advice, what's the best way to contact you?