1,911 karma · joined October 6, 2009
That said, I'm not sure learning to code is the best use of your time. Given how murky health care is, an inside knowledge of the industry should be immensely valuable to a startup, especially when it comes to demonstrating formidability and landing early biz dev relationships. You might be better off working on on the ins and outs of daily business, inbound marketing and fundraising, so that you can support your team while they build whatever it is you set out to build.
MiddleManagement works great for my needs, but if these libraries serve the same use case(s), I'd rather converge towards one library than have things spread out.
One other thing you may want to add is a retry loop for the heroku API calls. Every now and then, the heroku gem will throw a RestClient::ServiceUnavailable: 503 Service Unavailable exception. In the worst case, I'm not sure if this is best handled in the gem or at the application layer; however it's definitely worth retrying a couple times if you can avoid the blowup completely. I got some feedback from the Boston.rb group on handling this if you're interested: http://groups.google.com/group/boston-rubygroup/browse_threa...
I wrote a similar gem back in January and have had good luck with it: https://github.com/freerobby/middle_management
It's fully configurable via environment variables, so you can make changes without redeploying. It also lets you specify a minimum number of workers (even if there are zero jobs) so that you don't have to wait for workers to spin up if you don't want to.
Personally I don't feel we have a "startup curse," but it is definitely something that others talk about. It's generally in reference to the fact that despite having all the things that you've mentioned, we're yet to have a company exit or grow on par with the most successful San Francisco startups.
1) It's bogus that I need to buy a subscription twice to watch it on my iPhone and my laptop. I'll pay a small fee for an iOS app but it's ludicrous to make me pay double licensing fees.
2) Why in the world would you build an iOS app oriented towards video and not build an iPad version?
3) Why are they burdening users with choices like "do you want to see seven teams or all teams?" This doesn't bother me as a user but it drives me crazy as a designer. They're making the signup flow gratuitously complicated. It's a bizarre segmentation that forces users to think unnecessarily.
4) The black hat UX like auto-renewal and email-to-cancel is irritating and makes me mistrust the service.
1) I was referring to portable all-in-one units like the Boss Micro BR, Tascam field recorders, etc. Maybe I should have been more explicit about this.
2) Ableton is great for recording and processing, but for creating virtual instruments without external hardware, I'd prefer the iPad interface.
Sorry you feel our tooltips are a gimmick - we used them because we felt it was the best way to convey the most information without crowding the screen with excessive copy.
Notable paid features include transcription of price/date/description/categories, and super-quick expense/reimbursement report generation.
We are not the first to enter this space, but we feel we can compete on ease of use for the receipt uploader.
Would greatly appreciate feedback on the service and product. Thanks!