next »

[seagaia]

during the working week, I can manage a theoretical limit of 8/day, not including time spent on random design thoughts at work. However that's usually impossible and it usually ends in the range of 4-6, depending on the night's events.

Weekend, usually from 6-14. Depends if I decide whether or not it's worth exploring the city of New york during the day

But I'll be ending my internship this week, and I'm guessing the number will hover around 12 a day. I have friends and family I'd like to spend time with, after all!

[Radix]

14 to 16 hours when it's something really exciting and I'm on a roll, which never lasts longer than two weeks. 8 hours when it's something important and I'm trying to get into that mode, which never happens on purpose. <1 hour when I'm being a lazy piece of shit.

[C.A. Sinner]

3-5 hours usually. i could work more but i found that it becomes drudgery and the work suffers if i work longer hours, with no actual increase in productivity. but this varies on the type of task; if it's simple tasks that i'm working on i may work 10 or even 13 hours a day on something, but if it's complex or creative tasks i prefer 3-5 hours

Yup. Actually I found I've become MORE productive since I started doing that. Previously I'd just work on the game until I got sick of it. I also take breaks between tasks to give my mind a little time to "reset" and adjust to the next thing.

[Fallsburg]

On weekdays, when my wife is working, I probably work for about 5 hours.
Weekdays, wife isn't working, ~1-2 hours.
Weekends, wife isn't working, varies greatly depending on plans for the day, but probably ~4 hours.
Weekends, wife is working, ~8 hours.

[moi]

work 3 hours a day on your game consistently and you will be unstoppable. More than that would be counter productive

[Graham.]

You mean if you're full time elsewhere.

I work whenever I can be productive. money-work + game-work: 40-80 hour weeks.

But in my off time I spend a lot of energy reading about games, watching videos about games, reading about business... blah, blah. I don't always know where life ends and work begins.

[Muz]

I love Google's 70/20/10 model. I think even more so for indie games, it should be distributed that way.

8 hours a day is ideal, IMO, with a fat hour long lunch break. Too short and you don't get any momentum. Too long and you're burned out the next day.. and work enough to cover up for that and you'll be burned out the following day, and so on.

There are some tough tasks that require you to slog through. A strict 8 hour a day actually helps with that, otherwise, it's just too tempting to run off and play some game for the whole day.

Usually do the 70% thing early in the day. The 10% thing late in the day when I'm more tired and feel like clicking through tons of articles or messing with graphics/music/sound. That 20% of not-so-core stuff I usually spend a whole day or maybe a week on when I'm tired of looking at core work.

I like to save the hard stuff early in the day, easy stuff late in the day or near lunch hour. If I'm having a particularly rough day, I force myself to take a full 1-2 hour lunch break, maybe even cook something nice and watch a movie.. then get back to work right after.

With a full time job, I normally don't spend any time indie at all.. I already spend the whole day coding, and it's pretty similar to personal projects anyway. So usually I just read through emails, look for forum skins, better Notepad++ fonts, find cooler tools, learn keyboard shortcuts. That kind of optimization stuff.

Weekends I sometimes spend full time on my games, but lately it's just spent improving programming technique.

[John Sandoval]

Not as long as I should be.

[James Coote]

When I first started working, I was doing maybe 3 or 4 hours a day of coding, and the rest playing online games or surfing the web.

Once I quit online gaming, my productivity went up, because if I got bored, there was nothing else to do. So after a break, I'd sit back down at my game and get another 3 or 4 hours done.

I probably average about 30 hours of coding per week, plus another 10 or 20 doing all the writing blogs, posting on forums, "keeping up with trends in the industry" plus business admin stuff like sorting bank accounts or reviewing contracts

Being self-employed, days of the week are irrelevant. However, the biggest productivity killers are the days when I have to go do something like pick up my passport from my parent's house about an hour and a half's travel away. And inevitably, I'll stay and chat for a bit and then have dinner and then only leave at 9:30 pm so I get back really tired at 11pm, and the next day I'm like "fuck you alarm! I'm sleeping in" and by the time I get back to the code face, I spend the rest of the day trying to remember what I was in the middle of when my friends and family and people that care for me rudely remind me of that fact!

I'm in London and I have tickets to the olympics on 3 or 4 days, but I'll probably lose at least a week of productive work over the next month or so

Still, can't really complain, as I'm incredibly lucky that I can even do this full time

[ANtY]

14 to 16 hours when it's something really exciting and I'm on a roll, which never lasts longer than two weeks. 8 hours when it's something important and I'm trying to get into that mode, which never happens on purpose. <1 hour when I'm being a lazy piece of shit.

[Conker]

For me LoL gets in the way.
Maybe I should just uninstall it..

[John Sandoval]

nop

noooop

nope

not gonna happen

[ANtY]

For me LoL gets in the way.
Maybe I should just uninstall it..

I double dare you

[Molten_]

I'm currently learning python ... so I would say I spend about 1 hour when I can? I'm profoundly lazy, so I find myself spending hours on my computer doing things that I really shouldn't be doing.

However back when I was actually making stuff and didn't have real life obligations, I could easily dedicate an entire week to development if I was passionate enough. Lonely Dreamer was made in one week.

[Graham.]

Learning when to work, and when not to work, takes practice. It's a skill all on its own. It's a skill like anything else.