I've been thinking a lot about writing as I work on my master's thesis (notice that I say that I've been thinking a lot about writing, not that I've been doing a lot of writing). Anyway, I've been thinking about why I've been having trouble writing, and I had an interesting thought.
People always say that the best way to get over writer's block is to just write stuff down without worrying about it, then to go back and make it good later. Unfortunately, I find that as hard as writing good stuff in the first place, if not harder—I almost always plan every sentence and paragraph in my head before I start writing it—and I think I may know why: I write a lot of code. It's what I did for classes, what I do at work, what I do for my master's research, and not infrequently what I do with my free time. And what's the number one rule of writing code? Don't write any code until you know exactly what you are doing. No one ever says, "Write a lot of free-form code, then go back and try to make it into a good algorithm later"—that's a quick road to buggy, broken code.
So now I have two plausible theories. Theory one: I've written so much code that I've absorbed the doctrine deep into my psyche. Theory two (and this is my favored theory): That's simply the way I've always tended to think and approach problems, which is why I've always found writing papers painful, and writing code relatively easy. Either way, I now have something besides my laziness to share the blame for my slower-than-I'd-like progress.
Category: Random

Subscribe