Not a dis, just an observation.
Not a dis, just an observation.
If we'd had perfect knowledge of what we were going to build in the beginning, we could have cut a lot of time off customer development / exploratory phase of the product development, but I've never realistically heard of that before for a new product.
I wish you guys all the best, but I wonder if you'll look back at this in a year and think that maybe you should have just taken another month or two to build 1.0.
FWIW, pretty much the entire time we were in the office working, so was Justin -- asking what he could do to help, if there was anything to test, that needed doing to free up some time, etc. Working that much kind of sucks. But, there are much worse ways to work that hard than with a bunch of smart people who are working just as hard as you are.
</one of the people who built the iPhone version of Socialcam>
"The first 90 percent of the code accounts for the first 90 percent of the development time. The remaining 10 percent of the code accounts for the other 90 percent of the development time."[1] —Tom Cargill, Bell Labs
We were guilty of being overly optimistic for sure. When you're doing something new, you just have to be really really pessimistic.
There's also something to be said about working on awesome teams. If you've ever been fortunate enough to experience it, awesome teams make you want to be there in the trenches and not at home sleeping. I'm sure this changes as life's priorities change, but to anyone that's ever been there you'll understand what I mean.