Live data from Hacker News

A one-side-project-per-month challenge

github.com

21–30 of 121 posts

Re: A one-side-project-per-month challenge

#21
post #9

Excuse my ignorance, but aren't we glorifying speed here at HN? I think one project per month is way too fast to acheive anything of substance. If you're spending one hour three days a week, you'll only have 12 hours to finish a project. Even if you quadruple that, 40h isn't all that much for completing anything interesting at all. I have spent more than a year off and on on my latest side project, and it's not finis…

Ken Thompson wrote Unix in a month.

Re: A one-side-project-per-month challenge

#23
I couldn't do this. My big thing is i always want to be working on personal projects that solve problems in my life. If that ends up with cool stuff, great! But i've been burnt out too many times on making things for other people.

It's one thing if i set out to make a passive income, but that's work in my opinion. My side projects are open source commitments of mine, and assuming the "thing" works well and solves my problem, i'm contributing to it for years to come. Or at least until the problem is solved in another way.

If i'm really lucky, side project can become passive income (ie, providing hosted versions, etc), but that has yet to happen, and i'm fine with that. I'm solving my own problems, which i find quite enjoyable!

(not trying to be negative, just my take on it)

Re: A one-side-project-per-month challenge

#24

Code is useless if it is for nothing. Don't write code just to write code, write code to solve a problem you are having. If you're having 1 problem per month, then write 1 project per month. If you encounter 50 problems in one month write 50 projects in 1 month. If you encounter 0 problems in one month, write 0 projects that month.

This is right when you're already at a certain level of competence. I would be pretty disappointed to hear John Carmack was taking on this challenge, but it's a good one for people who need to just put some pencil to paper to get the practice.

Re: A one-side-project-per-month challenge

#26
post #9

Excuse my ignorance, but aren't we glorifying speed here at HN? I think one project per month is way too fast to acheive anything of substance. If you're spending one hour three days a week, you'll only have 12 hours to finish a project. Even if you quadruple that, 40h isn't all that much for completing anything interesting at all. I have spent more than a year off and on on my latest side project, and it's not finis…

i think the idea is to put a ship date or it won't get done. A month is arbitrary of course, but long enough to make 'something' in part time, but not long enough where you can slack and eventually abandon it. it's a mind hack to keep you on "schedule" with a end goal in sight.

Re: A one-side-project-per-month challenge

#27
post #3
post #2

I had the same idea: starting one project per month for 2017. I guess 2016 is too now short to achieve something relevant ;-)

Still haven't finished my Game a Month project for January 2016...

I did 3 months in 2014 (I think?) then got stuck. It wasn't so much finding the time that was the issue for me, but deciding on a game I'd like to build. Although that's pretty much the story of my side projects, I spend more time procastinating over what to build rather than building it.
Post reply on HN