1. Do not have access to the internet on your work machine. If you don't have 2 computers, get a netbook for < $300 and connect it to the internet. They should be in 2 different workstations, ideally in 2 different rooms. The thinking is that if you have to get up, you'll only do it if it's really necessary. It works pretty well.
2. You should have 2 modes: coding and not coding. For coding, you should be at your desk coding. For not coding you can be anywhere, but not at your desk. One of my biggest problems is that I often find myself in one mode when I should be in the other. If you're having trouble writing code, then you probably don't know what to write. Grab source code listings, pen, & paper and get away from your computer. Don't come back until you know exactly what you're going to be working on. Better yet, until you're dying to work on it. OTOH, if your doing analysis and are stuck, stop. Go back to the computer and code something, anything small, just to get going.
3. End every day in analysis mode. Don't go to sleep until you have tomorrow's plan ready. You should wake up knowing exactly what you're going to be working on and excited to do it. More about that:
You are a wealth of information on productivity. Everytime I see your posts there is always something of great value in them. You really should start a blog (unless you have one?) and cover these subjects there as well as I really enjoy hearing about your routines and experience.
Now I'm off to setup a timer on my G1 so I can test out the 48/12 method.
Blogging is one of those things I'd love to do (along with bridge, piano, & foosball), but I don't because I don't want to do it "half way". I'd be afraid of having 3 posts one week, then none for the next month. And I don't want any of these things to interfere with the time I dedicate to my projects. I know that by the third Wednesday night, I'd have to choose between coding and blogging, and I don't want to be in that position (at least at this point in my life).
So instead I come here. hn is perfect for someone like me; I come when I can and don't come when I'm really busy coding. I suppose my posts here comprise my "pseudo-blog".
Getting work done really isn't all that complicated, and I'm glad to share what works for me. Most importantly, work on something you're passionate about and find those habits that work best for you. All the rest is details.
I was thinking from more of a concentrated, documented library of your productivity tips instead of a social blog, but I definitely see your point and commend you on your "productivity > x" mindset.
I'll just have to start saving clips I've read that have been very inspiring for reference.
Agree totally on 3 and 6. Not a coder, no advice on the others, but I zone out and work for 3-5 hour stretches when I come to work prepared and put on some music I'm familiar with and like (lyrical or otherwise).
Fell into that pattern in college when I had to write my philosophy papers.
I'm not a coder, but I generally agree with all your rules. I have pretty good self control, so I usually just nail my wireless on my laptop and plug away with my work, so I generally avoid the need for 1 & 2, however that is how I used to work before I left my desktop in another country.
#3 is an unbelievably important point and I fail to do it myself and I get bitten in the ass. When I finish writing I always try to add a quick 'to do' of my thought process for the next day, I find it helps me get back into the groove a lot faster. The past couple of days I forgot to do it and it seriously feels like going against a brick wall and basically feels like how writing used to be for me at the beginning.
#6 I practice myself, but I'm never sure of. I have music going and then like 40+ minutes later I become lucid and I'm like 'SOAB I missed the song I like', so I'm unsure if the music helps me or if it's just background noise. Although music can certainly help set the mood for working, so I suppose it helps in some way.
You have to set an alarm. The minimum amount of time I sleep is 30 minutes, max is 45. Longer than 45 you start going into deep sleep and you'll be pretty unhappy if an alarm wakes you from that.
Comments
1. Do not have access to the internet on your work machine. If you don't have 2 computers, get a netbook for < $300 and connect it to the internet. They should be in 2 different workstations, ideally in 2 different rooms. The thinking is that if you have to get up, you'll only do it if it's really necessary. It works pretty well.
2. You should have 2 modes: coding and not coding. For coding, you should be at your desk coding. For not coding you can be anywhere, but not at your desk. One of my biggest problems is that I often find myself in one mode when I should be in the other. If you're having trouble writing code, then you probably don't know what to write. Grab source code listings, pen, & paper and get away from your computer. Don't come back until you know exactly what you're going to be working on. Better yet, until you're dying to work on it. OTOH, if your doing analysis and are stuck, stop. Go back to the computer and code something, anything small, just to get going.
3. End every day in analysis mode. Don't go to sleep until you have tomorrow's plan ready. You should wake up knowing exactly what you're going to be working on and excited to do it. More about that:
http://news.ycombinator.com/item?id=191275
4. Never text or IM when working. Have the cell phone nearby only for emergencies. For email, go to the other computer once an hour (see #1 above).
5. Try 48 minutes on, 12 minutes off. For long coding sessions, this works pretty well for me:
http://successbeginstoday.org/wordpress/2006/09/the-power-of...
6. Ipod.
You are a wealth of information on productivity. Everytime I see your posts there is always something of great value in them. You really should start a blog (unless you have one?) and cover these subjects there as well as I really enjoy hearing about your routines and experience.
Now I'm off to setup a timer on my G1 so I can test out the 48/12 method.
Thank you, thismat.
You really should start a blog
Thanks for reminding me, I forgot...
7. Don't blog.
Blogging is one of those things I'd love to do (along with bridge, piano, & foosball), but I don't because I don't want to do it "half way". I'd be afraid of having 3 posts one week, then none for the next month. And I don't want any of these things to interfere with the time I dedicate to my projects. I know that by the third Wednesday night, I'd have to choose between coding and blogging, and I don't want to be in that position (at least at this point in my life).
So instead I come here. hn is perfect for someone like me; I come when I can and don't come when I'm really busy coding. I suppose my posts here comprise my "pseudo-blog".
Getting work done really isn't all that complicated, and I'm glad to share what works for me. Most importantly, work on something you're passionate about and find those habits that work best for you. All the rest is details.
I was thinking from more of a concentrated, documented library of your productivity tips instead of a social blog, but I definitely see your point and commend you on your "productivity > x" mindset.
I'll just have to start saving clips I've read that have been very inspiring for reference.
Agree totally on 3 and 6. Not a coder, no advice on the others, but I zone out and work for 3-5 hour stretches when I come to work prepared and put on some music I'm familiar with and like (lyrical or otherwise).
Fell into that pattern in college when I had to write my philosophy papers.
I'm not a coder, but I generally agree with all your rules. I have pretty good self control, so I usually just nail my wireless on my laptop and plug away with my work, so I generally avoid the need for 1 & 2, however that is how I used to work before I left my desktop in another country.
#3 is an unbelievably important point and I fail to do it myself and I get bitten in the ass. When I finish writing I always try to add a quick 'to do' of my thought process for the next day, I find it helps me get back into the groove a lot faster. The past couple of days I forgot to do it and it seriously feels like going against a brick wall and basically feels like how writing used to be for me at the beginning.
#6 I practice myself, but I'm never sure of. I have music going and then like 40+ minutes later I become lucid and I'm like 'SOAB I missed the song I like', so I'm unsure if the music helps me or if it's just background noise. Although music can certainly help set the mood for working, so I suppose it helps in some way.
Try 48 minutes on, 12 minutes off (power nap!).
This has never worked for me. Everytime I try to sleep for a few minutes I end up taking a whole hour or more. Just my personal experience.
You have to set an alarm. The minimum amount of time I sleep is 30 minutes, max is 45. Longer than 45 you start going into deep sleep and you'll be pretty unhappy if an alarm wakes you from that.
Agreed, I can't sleep during the day, I can hardly force myself to calm down for bed at night as it is.
I sleep for 20 minutes after lunch and it is great. If I didn't, I wouldn't work in the afternoon.