People ask me what I do, and I say, “I’m a full time programmer, part time writer.” I get varied reactions to this. Some people think those two activities go hand in hand, while other people marvel at how I can have such diverse outlets.
The truth is, the two pursuits use different parts of my brain, but they draw from the same energy source.
What it’s like when I program
Programming is one part problem solving, one part creativity, and one part mindless plodding.
When I sit down to write some software, I start with a plan. We call it them “requirements.” Sometimes the requirements are more well formed than others. The requirements describe the problem to be solved, and often examples of how to test and make sure the problem is actually solved.
When I write software, I try to be succinct. I try to make the code maintainable and functional, accomplishing the task as quickly and as efficiently as possible.
Sometimes I work with other programmers. Sometimes I work alone. Sometimes I have to make it fancy. Sometimes I just have to make it get do its job, without anyone seeing how it works.
When I’m deep in the zone, I can listen to music, as long as it isn’t too distracting. It can have words, and I can even sing along with music while I’m programming.
I use a whiteboard to sketch out parts that are unclear. When I’m tackling particularly complicated problems, I’ll write out comments first, which effectively sketches out a map of what the code I’m about to write will look like.
What it’s like when I write
Writing is one part isolation, two parts creativity, and one part obsessive compulsive disorder. Some people include caffeine, but I’ve been off caffeine for about 7 years.
When I sit down to write a story, I start with an idea. Sometimes it’s a big idea that I’ve mulled over for a long time. Sometimes, all I have is a vague concept. If I have too much of the idea mapped out, I lose interest in writing the story, because I’ve already spoiled it for me. If I don’t have enough of the idea mapped out, then I wander around aimlessly for a while, until I find my way.
When I write fiction, I am not succinct, which is okay in the first draft. I tend to use too many words, and my sentences are too long, especially in action sequences. It’s okay, though, because eventually, there will be editing. And with the editing, brevity is sought. Parts are cut. Sentences are made shorter.
I have not written a serious story with anyone else. I can sit down with other people and write, but it would be confusing to say that I write with other people.
When I’m in the zone while writing, it doesn’t matter what else is going on around me. I’m in another world.
I cannot listen to music and write. If there is a movie going on in the same room, I can’t write, even if I can’t see the screen. If there is an interesting conversation going on near me, I can’t write. For me to write, I need to be able to hear the words I’m typing, and I need to be able to listen to the words in my head without interruption.
When I’m planning to write a story, I open OneNote on my Surface and I hand write some notes. Sometimes I write sequences of events. Sometimes I ask myself questions that I think the reader will ask, then jot down the answers. I write down brief thoughts and descriptions of the characters.
I can tell when I’m writing well by how often I look at my notes. If I’m looking at them a lot, then I’m stalling, because I don’t know what I need to do with the story at that moment of time. When things are going, I don’t look at my notes at all, because I don’t need to.
Comparisons
Both activities are sedentary. Both activities involve a lot of typing, and I actually get a primal satisfaction from hearing that clackety-clack of the keyboard with both activities. Both activities involve a lot of trial and error. Both activities involve “drafts,” where I get an implementation of my ideas down, then go back and debug or edit later.
With programming, the work I do can be eloquent, but it is always dry and barren.
With writing, I strive for eloquence and words that transport someone else to a place in my imagination.
I write software in order to meet a set of goals. An external source requests a set of features and functionality, and I strive to meet the demand.
I write stories in order to express myself. All of the drive and impetus comes purely from within. At this point, the only one clamoring for my stories is myself and my wife.
I get paid to program.
I do not get paid to write.
Conclusion
I enjoy both activities. I am truly fortunate to have found and capitalized on some of the opportunities put before me. It wasn’t easy, and there were no hand-outs. I worked hard to become a programmer, and to get into the position I’m in now.
I suppose I’m greedy, because I want to make money as a writer, too. I’m still quite a ways from getting there, but I’ve received enough encouragement to believe that it might not be a pipe dream. I just need to keep working at it, one day at a time.
At the beginning of this post, I mentioned that both activities draw from the same energy source, and that’s true. They both rely on my ability to focus, and focus takes willpower and drive. I only have so much focus each day. Most days, I don’t really have enough to both program and write.
When I’m deeply involved with either programming or writing, the other suffers. I don’t know what to do about that. I have a job to do, and people depending on me to get that job done. But I also feel a need to pursue my writing dreams, because when I stopped that pursuit, I was extremely depressed.
If you have an answer, leave a comment and let me know. At this point, I don’t know how to keep all of the plates spinning.
