Ask HN: How do you determine which project you should work on?

Re:Ask HN: How do you determine which project you should wor... by walesmd on Monday February 02, 2009 @09:50PM (#463402)

1. Do I find it interesting? If it woke me up from my sleep or prevents me from sleeping, because I am so interested in working on it - it's time to work on that idea.

2. If not that extreme - is it worth losing X months of work on my current project. When I set code aside, I can rarely every just jump back into it. I tend to rm -r and start all over. So, is this new idea worth those 6 months I spent on my current project?

3. If not - it goes into Backpack in order of "excitability" and I'll get to it eventually.

[ Parent | on HN ]

Re:Ask HN: How do you determine which project you should wor... by anotherjesse on Monday February 02, 2009 @10:49PM (#463468)

Instead of a backpack, I use a "uservoice" page for projects that are interesting but I'm not going to do them. Then others can add comments, add ideas, implement the ideas, ...

Similar to Tantek's reasoning for wikis, I like sharing the ideas that I'm not going to implement any time soon

[ Parent | on HN ]

Re:Ask HN: How do you determine which project you should wor... by walesmd on Tuesday February 03, 2009 @11:20AM (#464141)

That's a really good idea - I may have to look into doing that.

I don't place ideas in Backpack to keep them in the "walled garden" - it's just the most web-accessible, easy to use area I have for information of that nature (I keep losing sticky notes).

[ Parent | on HN ]