3 ms·

I don't know about this interpretation of "just start". My take on the "just start" thing is to avoid procrastinating forever, and feeling like it's not the ri

by arn 16y ago

I don't know about this interpretation of "just start". My take on the "just start" thing is to avoid procrastinating forever, and feeling like it's not the right time, or your idea isn't good enough, or you aren't ready. The point is nothing will get your idea honed and your skills improved than just starting. Maybe it won't succeed... but that's actually not the point. I don't think anyone is saying "just start" is the key to success (though clearly a prerequisite). I think they are saying that trying and not succeeding is better than never doing anything. The startup's take on "better to have loved and lost, then never to have loved at all"

j_baker 16y ago
"I don't know about this interpretation of "just start". My take on the "just start" thing is to avoid procrastinating forever, and feeling like it's not the right time, or your idea isn't good enough, or you aren't ready." My experience has been that if I can't resist procrastinating to begin with, then I likely won't be able to resist procrastination once I've started either. If you need to do "productivity hacks" to get started, is the project really worth doing at all? I mean getting started is the easy part.
ryanlchan 16y ago
I think we're all interpreting 'just start' differently. Cal might not have done this intentionally, but it's not really fair to compare 'just start' for skills vs. for start-ups. Cal's advice, as he says in the article, is for a very specific audience. His whole spiel is to get so fanatically good at one specific, tightly niched skill or knowledge set that it starts returning exponential returns relative to how much time you put in. This is pretty antithetical to the 'just start -> fail early, fail fast' mindset of startups. And that makes sense: If you're trying to develop a skill (say, being an awesome ruby programmer), then you're better off clearing a week and deepdiving into ruby; the criteria and the bounds on this process are clearly defined. However, if what you're trying to found a start-up from an idea, your scope is totally unknown; there's no way that you can clear off your week and decide to become really good at 'creating the next twitter', because no one knows what that skillset from the outset. The idea of 'just get started' in startups is to help you define that scope of what it is necessary, then give you a chance to see if it's reasonable to develop and execute on it (FEFF).

by arn 16y ago

j_baker 16y ago

"I don't know about this interpretation of "just start". My take on the "just start" thing is to avoid procrastinating forever, and feeling like it's not the right time, or your idea isn't good enough, or you aren't ready." My experience has been that if I can't resist procrastinating to begin with, then I likely won't be able to resist procrastination once I've started either. If you need to do "productivity hacks" to get started, is the project really worth doing at all? I mean getting started is the easy part.

ryanlchan 16y ago

I think we're all interpreting 'just start' differently. Cal might not have done this intentionally, but it's not really fair to compare 'just start' for skills vs. for start-ups. Cal's advice, as he says in the article, is for a very specific audience. His whole spiel is to get so fanatically good at one specific, tightly niched skill or knowledge set that it starts returning exponential returns relative to how much time you put in. This is pretty antithetical to the 'just start -> fail early, fail fast' mindset of startups. And that makes sense: If you're trying to develop a skill (say, being an awesome ruby programmer), then you're better off clearing a week and deepdiving into ruby; the criteria and the bounds on this process are clearly defined. However, if what you're trying to found a start-up from an idea, your scope is totally unknown; there's no way that you can clear off your week and decide to become really good at 'creating the next twitter', because no one knows what that skillset from the outset. The idea of 'just get started' in startups is to help you define that scope of what it is necessary, then give you a chance to see if it's reasonable to develop and execute on it (FEFF).