|
|
|
|
|
by eneifert
3821 days ago
|
|
I've worked the standard 40-? hr/week programming jobs for years and about a year ago I took on a project where I was the only developer and before I took the job I made the decision to work about 20 hours a week. Turns out that 20 wasn't quite enough so I ended up doing 25-30. Looking back I think 25-30 hours is about as efficient as I could have been as I gave the best hours of my day. But when it came to the last month before the release I found I did have to give some more time to get it done on time. Short bursts of working long hours seem to be effective for me, but I also noticed that I needed to take some time off after the project. It's been a great year and I've really enjoyed the other things I was able to do with my time. If you are able it's worth considering even if you take a little less pay. |
|