Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You're right. And maybe average number of hours per month is more appropriate. Or lets, say average number of hours per week. Usually the top end goes to 100 when I'm working on some new feature and am completely obsessed with it. However, following that there is definitely burn-out which causes me to go down to the 0-20 per week range.

Also, considering that I've been working on this since high school, I used to have a lot more time for it back then ;)

In a regular month I probably average around 20 hours per week. However, during a particularly overzealous month I may go to 35 or higher. I think at 20 it still falls under passive income.

Just to give you an idea of how my commitment varies. A year ago I had a full time job and I would sometimes work only 5-10 hours per week on it. Also, I completely neglected it in my first year of college (yet it paid for my college) and by my 3rd year there were enough problems that I had to again spend considerable time bringing it up to spec :)

I'd love to call it a hobby - because that's how I feel about it - but when 24 hours of downtime can cause more than a few hundred dollars of losses - it becomes tough not to take things a bit more seriously =/



Well the way you talk about it, it sounds like you are conflicted in how to describe it. Your word choice seems to acknowledge that its a job to an extent, while the intentions behind it are insistent that its your hobby.

I found that interesting.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: