Sigh.<p>"Don't reinvent the wheel." Classic advice. And it has some merit. But it's a broken idea.<p>Google? Not the first search company. The iPod? Not the first mp3 player. The iPhone? Not the first smartphone. Hacker news? Not the first tech oriented community site.<p>"Don't reinvent the wheel...<p>unless you think you can do much better."<p>Also, if you're merely iteratively improving the wheel, do so whenever you like. We don't drive around on hand-carved roughly circular hunks of wood any longer, and that's good.
That's a hell lot of things to change, break, go down, lose your data, start charging ridiculous prices, be discontinued, etc... I'm all for SaaS and not re-inventing wheels, but I'd be nervous if I had to rely on so many external dependencies.
I was hoping for a slightly higher-level look at what problems not to solve. It seems that Collections.me solves a solved problem - convenient online storage. It iterates a bit on it, but you seem to be building something that is largely a pile of already-solved problems, both in its implementation and use cases. Just my opinion, of course, and that is how many services advance, but I thought I'd voice it in light of the purpose of your post.
OP: thanks for mentioning us (<a href="https://circleci.com" rel="nofollow">https://circleci.com</a>)!<p>That's a lot more 3rd party services than most use - do you find major differences in reliability?
I second most of the listed services. Just because you can code or host your own systems, it doesn't mean you should. Any time spent on extraneous internal devices is a disservice to your core and customers.
Lastly, shameless plug but I think we have a better accounting solution in <a href="http://cheqbook.com" rel="nofollow">http://cheqbook.com</a>
"MongoDB is how we store things"<p>Is mongodb really a good solution for storing things? IIRC one concern about coinbase (YC) is that they used mongodb for storing financial information.