3 ms·
>> 80% push/change/adapt/enhance, 20% scrap ... > That's pretty good advice in principle but I'd swap the numerical values :) The reason for putting them the
by RiderOfGiraffes 17y ago
>> 80% push/change/adapt/enhance, 20% scrap ...
> That's pretty good advice in principle but I'd swap the numerical values :)
The reason for putting them the way I did is to stop things from being abandoned too early. I think you need to be willing to do lots, scrap lots, but you also need to put in hard work on each one. Scrapping them too early means you don't get a chance to discover and fix the flaws.
Perhaps I should write more about that, but I really believe that 75/25 (to go with the coin toss idea) really is close to right.
Having said that, you've built and are running sites for money, and my advice is based on models of building real world businesses.
But I do believe that things should be built fast, deployed fast, and given time to develop and be developed. That's why I say you should only scrap things 25% of the time. Work hard to prove an idea won't work. If you can't do that - persist and pursue. But once you can prove it won't work (or won't work well enough) abandon it and use the experience on your next attempt.
Finally, don't do these things serially, but don't go for too many at once. Two or three is my gut feeling for a sweet spot.
</blather>