It's alright. I'm on what you might call my 'second startup' at 23, but the main reason why my first one wasn't successful was that I didn't give it enough time to grow up and become it's own thing.
A startup is a serious commitment. At that age, I didn't understand that it was going to take time to actually grow the thing. I think it's something that a lot of people don't grasp. Instead we have 'startups' over the weekend, 'startups' that get abandoned when the next shiny idea comes along, and 'three startups before 18'.
I don't know that there's a way to have that many failures that young if you actually made an honest go of all of them.
Here's an entry out of my personal journal that I think applies here:
'Something Untrue'
When I was nineteen, I had my shiny idea I was working on. I’d written some software that proxied the iTunes Music Store, displaying third party content via the iTunes Music Store interface. You had to download and install the software, it required root privileges to install, there was no clear reason why looking at something in the iTMS was better than looking at it in a browser, it was hard to explain to non-technical people, there was no clear way other than advertising to make money out of it, etc. In other words, though it was a cool hack, it was a bad product.
I launched it, made a little splash, got a few news articles, and silently faded away. A few months later I just shut the whole thing down. Didn’t even bother to renew the domain name.
The biggest thing that’s stuck with me from the experience is how it wasn’t an overnight success. I wasn’t prepared to spend the couple of years on it that it would have taken to build up a really vibrant community and product. I wasn’t ready to iterate a few dozen times until I had something that really was worth taking the time to install and use.
I can’t help but wonder if this comes from our schooling where we work for weeks on a project, hand it in, and then get our A+ or our F back in one definitive stroke of a red pen. There’s no building upon previous work. You get the idea that a work, once presented to an audience, is immutable and complete.
This is completely tangential from the actual conversation, but I just had to pop in. I actually built a very similar proxy for the iTMS, in late 2005. I was hired on at an indie music store, with the original goal of showing their store inside of iTunes, then it was sidetracked into supporting podcasts natively (something like 2 weeks before Apple launched their support for it), then finally syncing to non-iPod devices from within iTunes. Was an interesting ride while it lasted. Just found it odd that someone else here had also done such a hack; quite cool.
Comments
It's alright. I'm on what you might call my 'second startup' at 23, but the main reason why my first one wasn't successful was that I didn't give it enough time to grow up and become it's own thing.
A startup is a serious commitment. At that age, I didn't understand that it was going to take time to actually grow the thing. I think it's something that a lot of people don't grasp. Instead we have 'startups' over the weekend, 'startups' that get abandoned when the next shiny idea comes along, and 'three startups before 18'.
I don't know that there's a way to have that many failures that young if you actually made an honest go of all of them.
Here's an entry out of my personal journal that I think applies here:
'Something Untrue'
When I was nineteen, I had my shiny idea I was working on. I’d written some software that proxied the iTunes Music Store, displaying third party content via the iTunes Music Store interface. You had to download and install the software, it required root privileges to install, there was no clear reason why looking at something in the iTMS was better than looking at it in a browser, it was hard to explain to non-technical people, there was no clear way other than advertising to make money out of it, etc. In other words, though it was a cool hack, it was a bad product.
I launched it, made a little splash, got a few news articles, and silently faded away. A few months later I just shut the whole thing down. Didn’t even bother to renew the domain name.
The biggest thing that’s stuck with me from the experience is how it wasn’t an overnight success. I wasn’t prepared to spend the couple of years on it that it would have taken to build up a really vibrant community and product. I wasn’t ready to iterate a few dozen times until I had something that really was worth taking the time to install and use.
I can’t help but wonder if this comes from our schooling where we work for weeks on a project, hand it in, and then get our A+ or our F back in one definitive stroke of a red pen. There’s no building upon previous work. You get the idea that a work, once presented to an audience, is immutable and complete.
And that’s just not true.
This is completely tangential from the actual conversation, but I just had to pop in. I actually built a very similar proxy for the iTMS, in late 2005. I was hired on at an indie music store, with the original goal of showing their store inside of iTunes, then it was sidetracked into supporting podcasts natively (something like 2 weeks before Apple launched their support for it), then finally syncing to non-iPod devices from within iTunes. Was an interesting ride while it lasted. Just found it odd that someone else here had also done such a hack; quite cool.