This post was written by Shaun.
“I don’t have time” is the mantra of the procrastinator. I could not tell you how many times I’ve said it myself, and each and everytime I knew it was a lie. There are twenty-four hours in a day and seven days in a week, surely somewhere in there I can find time to do everything that needs to be done. Yet over and over again I find that to not be the case.
Procrastination has definitely plagued me my entire life, but I had always felt certain that it would slide into the background as my academic career ended and my professional career began. But if anything the opposite is true. It isn’t a problem at work, it is true, but I seem to be perpetually out of hours when I’m off the clock.
I think at the root of the whole thing, the node(0) as Brad might want to call it, is that I am perpetually grossly underestimating the time and effort involved in things. I either think it will be far easier than it is, or simply believe that I can soldier through it by foregoing trivialities like sleep and food. I pile expectations onto my plate like so many mashed potatoes and I end up disappointing myself.
Apparently this problem is not uncommon, and is even believed to be genetic. That doesn’t surprise me in the slightest. Everyone knows someone who is always late, always scrambling. I don’t think I am beyond hope. I have accomplished too many things to view the situation as intractible. It is just something that I will always need to be concious of. I have never bought the excuse of “that’s just the way I am.” I think the second you are cognizant of something the responsibility lies entirely with you. Shrugging and blaming your DNA for your problems solves absolutely nothing, and frankly I am more concerned with finding a solution than a scape goat.
My approach so far has been to be more careful about monitoring how long things actually take. My ability to estimate what time it is fairly accurate it seems, it is just my guesses at how long I actually spend doing things that is off. By noting the start and end time when I perform an activity some simple arithmetic solves that problem for me. This works great for things like getting to work on time, where I repeat a set of activities quite often. It doesn’t work so hot on things I’ve never attempted before, like a game contest.
So, it appears my only hope is experience. I will keep doing things. Eventually, I will have done enough of what I need to do that I will already know how long it takes me to do it. I think perhaps this is true more often than people admit. I find that people tend to downplay their previous failures in light of more recent success, so it’s easy to trick yourself into thinking that everyone does everything right the first time except you. Perhaps instead of working so hard to improve myself, I just need to lie more?
I have given it some thought. Would you agree that these procrastinators work as follows:
while( time - deadline > project.timeEstimate ) {
procrast.status = 'I have time!';
}
procrast.status = 'oh, crap.';
If so, we should be able to find a way to ‘hax’ this code. Perhaps adding a random break would even be sufficient?
if (Math.random()*2 == 1) break;
Thoughts?
I suffer from the same malady.
People say that a potential solution when working on a time limit is to bash everything together in the grossest generality possible, and then work down to the details as time permits. Personally, I love working the details out far too much to actually try that.
@Brad
I think you may have solved the world’s problems.
@Brad
Hahaha that does seem very accurate!
We should just maybe pad project.timeEstimate?
@Karl
Details can be fun! Often times what starts a project for me is an interface idea. I want to see how much better, or worse, some slightly different UI I’ve imagined would work.
In such cases, the projects themselves are often simply excuses to do that. For example, BHI @ webcomic navigation.
It works best when I start with the details of the experiment. Make something semi-complex (filled with arbitrary literals) is far easier to do when by itself, than than it is within an existing system (where you’re writing bits of code that will generate other code, which will all interact with each other).
Also, it gets you right to the fun, instead of right to the tedium.
@Brad
Sorry: “BHI @ webcomic navigation” ?
BTW, what happened to your old webcomic navigation interface?
@Karl
It got pulled off the other server with the GC, but I have it here.
BHI = Bradicon Heavy Industries. Although BHI was a webcomic site, it was never really meant to have webcomics. I wanted to attempt a webcomic interface that allowed for easy/fast navigation through the archives.
I think it worked out pretty well – I liked the interface.
http://www.gigglingcorpse.com/examples/bhi – you can navigate with just the keyboard, or by clicking on the comic :O