Although it's geared specifically toward web designs, I've found some value in http://www.criticue.com. Although (the last time I used it at least) the community wasn't dominated by sophisticated designers, it was a reasonable way to get design feedback from "normal" web users.

No one needs real-time???

I beg to differ. Running > 100k transactions per second, it's saved us a lot of pain over the years. High latency data is fine if your overall transaction rates are relatively low. But at really high rates, timely updates on your KPIs can really help.

SpendLight - I'm helping couples/families/individuals get their bad spending habits under control. Think of it as a spending journal with simple prompts for self-evaluation. Users give themselves actionable feedback to keep in mind for the next occasion.

I've had a few designers express interest, but the dialog petered out. Good reminder to give it a kick in the pants.

Adding some new notification features to spendlight.com. Sometimes feels like a slow slog, but I'll get there eventually.

Ari, what aspects of money management are the most important to you? Are you looking to fix some financial problem or just generally pay attention to income and expense?

I'm interested,but the "free sample" doesn't give me a good feel for the "meat" of the booklet.

My wife and I found the most success tracking not just the dollar value of our spending, but also some notes about our decision making process. We try to capture the frame of mind which drove our spending decisions. Consistent and frequent self-evaluation have helped us cut out a lot of careless spending.

I love the idea of YNAB, but I'm also brewing something that focuses more on the behavioral aspect of spending. spendlight.com

I think I asked for an invite when the concept was pitched as the Screening Room. Is a functional demo required? In other words, are you suggesting those in concept or early development wait to submit their project?

On one hand, I'd not want to exhaust the group with an idea before it was ready to have a thorough discussion. On the other hand, the discussion might yield some input which is better heard sooner rather than later.

I'm mostly doing backend work these days on bare metal with a shoot-from-the-hip deployment model. I've got a half dozen scripts that make a last-known-good, scp the file out to production and then restart services.

For web development I'm running a fairly straightforward Capistrano workflow to deploy a rails app to two boxes. Rails runs on Unicorn behind Nginx with pfSense keep load balanced hand handle one of the boxes going down. Those boxes (thankfully) never go down.

We have DEV databases, but typically don't stand up a full DEV environment. We have TEST and STAG (aka staging) and even PRODSTAG to run new code before unleashing it to PROD. TEST and STAG have their own sandboxed databases. PRODSTAG is a separate Rails install running against PROD data.