Programming Warm Ups?
ResHippie asks: "No athlete or musician would think about just diving in to the day's activity without doing some series of warm ups first. Aside from starting most computing sessions with checking email and the like, I pretty much try to dive right in to the task at hand. It usually takes me a while to get going, though. Does anyone have any routines they go through before coding (or any other work-like activity) that helps?"
I don't know, five years at a University?
I work at home, and the work day starts at 0900, so this is my routine:
0830: alarm goes off
0840: actually get out of bed
0842: start brewing coffee
0844: pour cup of coffee before it's actually ready
0845 (optional): small scream as I pour hot coffee on my hands since I haven't opened my eyes yet
0846: go out on deck with copy of whatever magazine is closest to hand (generally some ancient copy of Linux Journal). Smoke cigarette, drink coffee
0859: come back in
0900: log onto computer and check for emails from co-workers
0901: quick scan through various mailing lists for security alerts and the like
0903: try to remember what I was working on yesterday when I called it a day and get back onto it
`fortune -o`
I usually start the day's coding session with a slow progression of vocal cord exercises that simulate what will be done later in the day.
Start with simple cursing. "Dammit. I can't believe I left that variable uninitialized." Then gradually build your way up to more intense grumbling, being careful not to overstrain your vocal cords. "Holy crap that goddamn idiot Jack still didn't fix that bug? That was a week ago! What does that fat sack of shit do all day long?" From loud complaining you work your way into loud yelling and screaming. "Fuck you, MSVC++! Don't tell me 'internal compiler error'! What the fuck kind of shit is this! You goddamn cocksucker! Fuck you Gates! Yeah, fuck you!" Now that your blood temperature has raised a few degrees, you can begin doing whole-body exercises. Jump up and down and scream "Fuck! Fuck! Fuck! There's no error there you shithead compiler! That's perfectly legal C++! Just compile it you fuck!" Then pick up your monitor and pretend to throw it against the wall. Start gradually at first, eventually working into really whipping your torso around. This will make sure you down strain any ligaments in your lower back when you finally do snap and start trashing your computer.
Remember people, safety first!
GMD
watch this
Obligatory Office Space quote:
Bob Slydell: If you would, would you walk us through a typical day, for you?
Peter Gibbons: Yeah.
Bob Slydell: Great.
Peter Gibbons: Well, I generally come in at least fifteen minutes late, ah, I use the side door--that way Lumbergh can't see me, heh--after that I sorta space out for an hour.
Bob Porter: Da-uh? Space out?
Peter Gibbons: Yeah, I just stare at my desk, but it looks like I'm working. I do that for probably another hour after lunch too, I'd say in a given week I probably only do about fifteen minutes of real, actual, work.
1. Drink Coffee ...
2. Read Email
3. Read Slashdot
4.
5. Profit!
IMO the best browser game ever http://wittyrpg.com
Make sure to do exercises for each part of your body:
Hope that helps,
GMD
watch this
I am staring at my hands thinking: but that's what I actually do... Maybe I should have gone to college where they teach proper technique...
Then again, taking a break from coding and reading the other replies: everyone else seems to be answering humorously, so maybe I can save my ego by saying:
of course I don't really do any of that, heh heh... that would be silly... I mean, coding is hard and I... Hey - look over there - the Matrix!!
Keep your packets off my GNU/Girlfriend!
and by that time, it's time to go home!
sssshhhhh
I'd say in a given week I probably only do about fifteen minutes of real, actual, work.
X(7): A program for managing terminal windows. See also screen(1).
One time Hunter S. Thompson was lecturing at my college campus (with John Belushi!) and I had the opportunity to ask him about his preferred method of preparation for a writing session.
Thompson's complete answer: "Booze and speed."