I spent 3+ years on my startup without being able to secure funding, getting by, fully commited [1]. I wanted to succeed really bad, but made too many mistakes from the get go and ran out of time/money eventually. To reflect on the topic of discussion, when evaluating why my startup failed (or another one succeeded), whether the founders wanted it bad enough is not a good core metric, which is what the grandparent claims.
Heal your wounds, save some dough and same player shoots again.
You have to play a lot of chess games before you start winning. Start-ups are no different, the learning curve is quite steep but if you persevere at some point it will start to pay off. If your first start-up takes off in a couple of weeks or months that's the exception not the rule.
Establishing any kind of business normally takes about three years so you have to plan for that.
Don't give up. I just saw this 2 days ago at a talk given by Venu Anuganti (the url was on the final slide, he didn't actually vocalize it though). Seeing something for the first time twice in two days in startup land could be a fluke, or it could be a trend.
You may be on the brink of success. In fact, I'm going to download and compile this right now.
oh man, is my face red :(. I'm still your new watcher on github though ... :)
I just moved back to the 2.6.0 tag. works.
This looks like a scalable database. I don't know if it was a for-profit company that you just open-sourced at the end or what.
All I know is that I don't see what I'm using. This is about a day worth of authorship on your part. Literally.
1. Write something to help a noob like me find out what I'm doing.
2. Give some (it can be silly and contrived) but useful example to bootstrap the user.
In programming you are fundamentally building something abstract that lacks concrete reality. The key to success, I've found, is giving it that concrete reality through coherent narratives, consistent verbiage, probably more.
I made it very carefully; being light hearted, poking fun at myself, trying to balance what people would think of it, being overall positive. I was trying to strike a really delicate balance in basically an advertising-to-geeks campaign.
Well, I think it worked pretty well. The project has 203 followers, which is my most successful by far.
I've found that this stuff matters a lot. Man does it ever. Backbone, underscore, and socket.io are probably popular not only because they have functional code (there's a lot of functional code out there) but because they have pretty websites (pretty is a POV word, but I think most people would agree those three sites follow aesthetic rules of thumb or modern web design ideas).
The readership of my blog entries went up phenomenally when I spent about 2 hours on my CSS. I spend 2-3 weeks on my longer articles ... that's 100+ hours, per article, it seems ludicrous that 2 hours on layout could lead to a larger gain than an extra 20 hours on citations and research.
But let me tell you right now, that is irrefutably true if you hadn't done it at all yet.
I think jQuery was so successful (and probably PHP too) because their documentation is so easy to navigate. No, it's not that it was so well written (Python is better written), but because google picked it up well and it was a cinch to navigate, and it worked.
Can someone far more successful than me weigh in on this, I hate to see people doing solid work and not getting acknowledged; that's enormously frustrating.
I spent 3+ years on my startup without being able to secure funding, getting by, fully commited [1]. I wanted to succeed really bad, but made too many mistakes from the get go and ran out of time/money eventually. To reflect on the topic of discussion, when evaluating why my startup failed (or another one succeeded), whether the founders wanted it bad enough is not a good core metric, which is what the grandparent claims.
[1] http://github.com/scalien/scaliendb