Brittbot

Upgrading from Data Center Tech to Software Engineer

A spiral-bound notebook laying on a desk with a pen next to the notebook. On the pages of the notebook has a person's handwriting.

Writing Code With Pen And Paper

—

by

Brittany Gates
in

When it comes to developing a new technical project I enjoy writing code with pen and paper. Yes, I don’t load up my favorite Integrated Developer Environment (IDE) and create a plan there. I rather use the notebook I keep on my desk next to my keyboard.

Why I Like Writing Code with Pen And Paper

The reason I like writing code with pen and paper because:

  1. It’s easier for me to make a thorough plan
  2. I can follow each step in that plan as I write code in my IDE
  3. Then I can mark off each item in the plan as I complete them

Example Of My Plans

Here are some pictures of my plans in my notebook. First up are the images of the plan that would later become The Infected Land:

The initial plans of my file backup program handwritten in a notebook (which later became The Infected Land).
The initial plans of my file backup program handwritten in a notebook (which later became The Infected Land).
The initial plans of my file backup program handwritten in a notebook (which later became The Infected Land).

Next are pictures of my plans that would later become Easy Home Directory Backup

The initial plans of my file backup program handwritten in a notebook (which later became Easy Home Directory Backup).
The initial plans of my file backup program handwritten in a notebook (which later became Easy Home Directory Backup).

As you can see by my chicken scratch I not only write some code, but I work out the logic (or conditional) statements for my program. I usually come up with potential problems I can run into (issues with user input) and find potential solutions. Finally, I just cross out a whole block of text and start over. Frankly, I do that quite a bit.

I think the best benefit I found doing this is working out problem in my logic. Sometimes I think I have it all planned out correctly on paper so I type it up. However, when I test out my application it doesn’t behave probably. Thus, I start debugging both in my IDE and on paper. And that’s when I discover my mistake (or three).

I think the reason writing code with pen and paper works for me because I take things slower. I actually think about the user will progress through the code. Thus, I can design my code to follow that workflow. Or I can discover a set of steps I can transform into a function, and use that function in different files.

If you find yourself lost in your codebase frequently I suggest grab a piece of paper and a pen and start writing!