Apr 24 2009

Crunch Time

I’ve been writing my dissertation in earnest for a couple of months now, for some definition of in earnest. As expected, things have come up to slow the process down—research that after closer scrutiny needed refinement, job hunting, sickness (my family and then I got the flu), presenting at a conference (remotely), some procrastination and writer’s block, and a general inability to write faster than is humanly possible. Just in case you were wondering, the rule of thumb to multiply coding estimates by 3 applies to writing as well.

That said, I’m still on track to graduate in August and making good progress. But because I don’t want that to change, and because I don’t know how the next few months will pan out with the job hunt and potential on-site interviews, I am going into super crunch mode. It’s like when they tried to make Knight Rider more exciting by modifying the car by adding extra drag so it would go faster. But not as glamorous.

This means that during the day when I should be working I won’t be haunting the usual haunts: IRC, Instant Messenger, email. I will of course check my email at least a few times a day, but when I’m writing my MUA will be closed. I will keep at least Jabber (Google Talk) online, set as away, as I have done previously. All this is not because I want to hide from you but because I want to minimize the event-based distraction mode I sometimes find myself in—constantly jumping between IRC, IM, email, social networks, RSS, etc. looking for the next communication task. If you do need to contact me urgently don’t hesitate to hit me up where you find me, or in the worst case talk to Erin, who will know how to get ahold of me.

While I’m on the subject, I’ll bore you with the methodology I’m employing in the never-ending battle against procrastination. First and most importantly, I have a goal to write 15 minutes every day, as a bare minimum. Even on otherwise-unproductive days (whatever the reason) I can squeeze in 15 minutes which means at least a little progress. More importantly, it means my mind keeps engaged on the problem and my dissertation doesn’t get swapped out. I’ve been doing this since January and it has made a huge difference in my productivity. I highly recommend it to anyone. For more information, check out the workshop homepage, read the summary, or grab the book. Or just write 15 minutes a day and let your success speak for itself.

15 minutes a day is great, but when you’re writing a dissertation and nothing else, it’s not sufficient. So I’ve had to kick it up a notch. Eddie Jung has some good advice: “Don’t get distracted. Keep starting. That’s all.” We’ve already talked about the public face of my efforts to not get distracted. I also have a plan for doing the “keep starting” part, which is I think the hardest part. Once I’m started and in the zone, you could be screaming my name in IRC or calling me on the phone and I won’t even notice let alone be distracted. So I think it boils down to “Keep starting. That is all.”

So how does one keep starting something that is frequently uninviting? “Just do it,” I can hear you say. That’s easy for a construction worker or someone doing something physical, but it’s hard for those of us who work with our brains, especially creative work. Because the very instrument we are trying to bring to bear is the instrument that is so easily distracted.

I like the metaphor of a train getting started. It’s big, it’s heavy, and at first the wheels spin and things move very slowly. Some glorious days, I wake up already rolling down the tracks. Maybe I went to sleep at the top of a hill, I don’t know, but I’m off and running before I’ve finished rubbing my eyes and the day is an outstanding success. Other days I sit down and keep trying to start without ever starting.

My plan to keep starting is to set up a ritual. A personal algorithm, if you will, for beginning to write. Just as the dog turns around three times before lying down to sleep. It has to be something that I can consciously do to trigger myself to begin writing. It has to be a trigger, and facilitate writing. It has to be portable—I have to be able to do it on my couch, in my “office” (the rocking chair in the kid’s room), at school in my real office, in the library (sometimes when I’m having a hard time focusing going to the library for a change of scenery helps), a café (ditto, but close to home), or just about anywhere. It has to be quick, like turning around three times and not like doing 30 minutes of yoga and upside-down meditation or something.

I have no idea if it will work, but here’s what I came up with: prep, timer, visualize. By prep I mean close my email client, IRC, etc., get situated, and get my water bottle filled if necessary. Minimize distractions and optimize the environment. By timer I mean grab my timer and set it for 15 minutes or whatever minumum chunk of time I feel up to. When the timer goes off, I can take a short break if I need to. It’s my sanity escape hatch—you can do anything for 15 minutes, even write. It’s also my distraction safety net—if the timer goes off and I am not writing, I got distracted and it’s time to start over. The visualization step is to close my eyes and engage my brain on the task, and not open my eyes until I have an action to perform. With my eyes closed, none of my distractions can reach me even if they made it through the cracks.

I have high hopes for my new plan. I know some parts work already, and I’m optimistic about the rest. I think it’s simple enough to actually work. Maybe my sharing it with you will inspire you to refine your process a little bit.

How do you avoid distractions and keep starting?


Nov 6 2008

Irssi on a Laptop

I love irssi, but it has laptop issues. It’s really unintelligent about network disconnects and waking up from sleep. It usually either takes forever to time out and try to reconnect, or tries to reconnect immediately upon wake before the wireless connection is established and then takes forever to time out and try to reconnect. So I tried it in screen on my server, and that works fine, but it lacks some usability features. Plus, it lacks some niceties that I’ve come to need on OS X from chat clients. I need my chat client to use growl to tell me when someone talks to me (directly to me, in the case of IRC). Then I can read the message quickly and decide whether I need to stop what I’m doing right then to respond, or if it can wait a few seconds while I complete my thought, or if it can wait a few minutes while I complete my thought. Plus, with the right theme, growl notifications can be easy to tune out as well (but your mind still registers that something happened and wants your attention, when you can give it). Second, it’s really nice to have IRC in a different application, so it can be hidden without affecting the rest of the Terminal.app windows. I use the terminal too heavily for productive work for IRC to insert itself on a terminal tab or in a terminal window. But, I could work with this by starting irssi in its own window and getting used to minimizing IRC. Not a deal-breaker.

I’ve been using Colloquy, and before that X-Chat Aqua, and while both meet the essential needs listed above (smart reconnect after sleep and growl), the both have the same problem: they’re not irssi (plus they don’t get much attention from the developers, and X-Chat Aqua is all but officially abandoned). Colloquy in particular crashes more frequently than a demolition derby car. So I find myself yearning for irssi. There are a couple wrap-irssi-in-cocoa apps, but they are also abandoned and incomplete.

In one last stab of hope, has anyone discovered a way for irssi to be intelligent about reconnecting? This is just as applicable in linux as in osx, and I know a lot of you linux users have laptops and use irssi—do you all just punt and use it in screen on a server? Has anyone found/written an irssi plugin for growl? (I assume someone probably has, or that it would be easy to whip up, but I haven’t bothered to look because I haven’t found the solution to the first problem yet.) Or, has anyone found an IRC client that actually comes close to being as awesome as irssi, reconnects intelligently, uses growl, and doesn’t crash frequently?


Jun 30 2006

macirssi

Ok, scratch that part about Irssix. Irssix is cool but has some issues:

  • pgup/dn don’t work from the input box
  • it automatically scrolls down when something new happens, making it really
    difficult to read backlogs. (I hate it when my terminal does this too, btw)
  • it tends to crash when reconnecting after waking my laptop

But macirssi is even better. It does let me
change the font, already comes with a dark background, has more preferences to
set graphically, and doesn’t crash. It does look a little funky, though (as in
not really OS X-ish).


Jun 28 2006

Irssix

I’ve been using Colloquy for my IRC needs in OS X for
some months, but I always have this nagging feeling that I should be using
something a little bit more perfect. See, Colloquy is high on the OS X
interface scale, but surprisingly low on the geeky features that matter scale,
especially considering its roots in Irssi. At long last I
decided it’s time to give Irssix a try again. I
quickly remembered why I abandoned it before–I don’t like the font and white
background–but as I was really yearning for the ol’ Irssi experience again I
quickly overlooked that. If I get really ambitious I’ll pay my dues and add a
font and color dialog.

In any case, I’m staying with Irssix. It’s faster, and I mean lighting fast
compared to Colloquy. I reckon it also takes much less RAM. Colloquy had a
tendency to get up there in RAM usage, and I’d occasionally have to restart it.
And of course, it’s basically the Irssi we all love in every single way.