Hacker News new | ask | show | jobs
by untog 3458 days ago
> If you find that one of your projects takes off, or you really like it, then continue to work on it.

I think this is the thing. It's a slightly weird set of incentives for you to create a new project every month, irrespective of whether last month's worked out or not.

I'd instead describe it as "12 months of ruthlessness". Start a project at the beginning of the month. Has it gotten anywhere by the end of the month? Do you have a result (and that can be an open sourced module as much as it can be a user-facing product)? If not, shut it down, start something fresh on month 2. But if you do have a result at the end of the month, keep at it.

2 comments

I agree, I would prefer a milestone challenge where people put up demos/videos/blogs of their progress (same project or not). Maybe my first month's project is creating a site for people to share their progress towards whatever their goal is. If you think that is a good idea, vote me up :)
I have a nearly five old idea that is very similar. Eventually someone will build it (well) and it'll become very beneficial!
If you would like to work with somebody on it; hit me up. Or if you have some ideas you'd like implemented, let me know.
>I think this is the thing. It's a slightly weird set of incentives for you to create a new project every month, irrespective of whether last month's worked out or not.

It's not always necessary to spell out everything.

If one's 3rd month product proves widely succesful and shows great potential, they can always decide by themselves to continue on it and not go on to their 4th and next months' products.

They don't need that spelt out in the challenge rules... And if someone is so dense that they do, there are slim chances that they'd be creating any great product anyway...

Well, sure, but if you're doing the "The 1 side project per month challenge" and the "1 side project per month" part is optional, what are you actually doing?
Obviously the "1 side project per month" part is not optional, it's conditional, which is something different.

The "1 side project per month" challenge being conditional on not having too much success with one of the monthly projects (thus prompting you to stop and focus on that) is not that different on it being conditional on numerous other things:

1) In that you continue to want to do the challenge (e.g. it's perfectly legitimate to decide it's BS and give up after a few months).

2) In that you have the time to do it (e.g. you might suddenly have to stop because you have too much on your plate from your day job a few months in).

3) In that you are able to do it (e.g. you might have to stop if you have a health issue).

And tons of other things besides.

So the question makes no more sense than asking "if you decide to run at your local marathon, and you stop after 12 miles because you got tired, or because there's an emergency at your home, or because you strained your ankle, or because you just felt like it, then what are you actually doing"?

The answer is obvious: you are doing the challenge for AS LONG AS YOU PLEASE.

You are losing the challenge. And not caring the least.