Exercise 8: cut

Hopefully you're learning more Python but even more about yourself and how you work. In this part of the book you're learning something about process as well as creativity by learning how to refine your process. It's true that you can't be creative with starting friction, but you should also be realizing that the easiest way to improve your own personal process is by watching yourself work. Simply doing exercises isn't enough. You need to take a look at your personal way of working and try to improve on how you do it.

As you refine your starting process you may find that you'll need a couple different starting methods to work on different kinds of projects. When I work on software similar to these little command line tools, I can start with just hacking on the code. When I need to work on anything with a GUI I find that I need to draw the UI out, implement a fake version of it, and then make that work. As you continue with the book you'll learn both ways of working and practice those processes.

In this exercise I want you to focus on your physical health and behavior. Too often programmers wreck their bodies trying to do this job. The job feels like it should not cause you any harm. You're just sitting at a desk all day, not cutting down trees or chasing after criminals in an urban setting. The truth is any job where you sit for long periods of time doing something stressful can destroy your body. To combat that you're going to keep track of the following things while you work:

• Do you sit up with good posture? Straight up isn't really good posture, but neither is hunched over. You want to have your body up and relaxed, head held up.

• Do you pull your shoulders up into your ears? Try to drop them down.

• Do you tense your wrist and rest them on the desk? Try to float them above the keyboard and keep them not too loose and not too tight.

• Is your head straight ahead and relaxed or are you straining it to one side to look at another monitor?

• Is your chair comfortable?

• Do you take breaks? 45 minutes is the longest you should work before you stop to take a break.

• Are you going to the bathroom? I'm serious. If you have to go, get up and go. The worst thing is to sit there holding it in.

There's more, but those are the big ones. I think many programmers feel if they get up from their computer it will explode while they're gone. The computer will wait patiently for you to return, and taking breaks gives your brain a chance to work on the problem in a different way.

You should also consider turning on your computer's web camera and record yourself working. You may think you don't slouch, but then in the heat of battle you do some strange things to your body without knowing it. Record yourself this session, and then look for anything causing you tension, problems, back ache or that is just weird.