How to Take Notes While Learning to Code

“Mac book on a table with a notebook and pen” Photo by Tracy Adams on Unsplash

I have found that I learn best when I take hand written notes. Processing information then writing it down sticks in my brain better than anything else I have tried. However, learning how to code has challenged my previously established note-taking habits. I have to digest a lot of information very quickly and I need to understand concepts as well as note specifics about syntax.

I am 1 month into my code school journey with the Flatiron School. Throughout this time and the time I spent preparing for the program, I have found a note-taking system that works for me. It leaves me with an easy to reference day to day record of my code school experience, gives me space to reinforce the material I am learning, helps me track my to-do list, and has already proven itself as a great tool to reference at a later date.

To start with, here are the supplies I use:

• Black or Blue Pens
• Pens of various colors
• A notebook
• Whiteout (I prefer the tape type)
• Stickers
• Note-taking App
• Text Editor

My notebook and the first few pages

I prefer to use a notebook with a dot grid and pages that are pre-numbered. This is not necessary but I have found it saves me from having to write in page numbers and the dot grid allows me to draw out concepts better than lined paper.

My first page lists a general title of what is in the notebook “Flatiron School Software Engineering Program 2020”. It then has my name and contact information. I also use this page for habit tracking. Right now it has a list of all of the weeks of my program and what my typing speed was at the end of the week (56wpm and getting faster!).

The next page starts my index. It has three columns; page number(s), date(s), and content. I left two pages for the index, based on how many pages are in my notebook.

Taking notes

My notes follow the structure of my day. I start with a list of concepts I want to focus on and bigger goals to work towards. I then write a quick schedule of the day; What classes I plan to attend, when I will take lunch, and any other obligations I may have. I also use this page as a running checklist. Throughout the day I often want to jot down something I want to review or accomplish later on. I start these bullets with an empty square and refer back to this page throughout the day and check them off once complete. I also often look at this list when I have a few minutes before a class and want to get a quick task checked off.

I am the type of person who loves checking tasks off a list so this works well for me.

I start each page with the date at the top left. Then the title of what it is I am taking notes on. Since I am often referencing a video, something that is being recorded, or something written I focus on main points, drawing out concepts that are new to me, and noting lines of code or commands to remember. I will use a different color when writing out code or when switching topics so it is easy to follow later.

How to handle blocks of code and code-alongs

When I get to a point where I need to save a block of code or a screenshot from a lecture I used Bear Notes. I indicate in my written notes that I am doing this with a sticker (mine are shaped like little teddy bears). I then put the screenshot or code block into a Bear Note with the date and a short explanation. Bear Notes has formatting for inputting code and also has an easy system of organizing your notes. There are lots of other similar note-taking apps, find one that works for you.

In some classes, our instructor will introduce the concept and then code at a slower pace so we can code with them and ask questions as they code. In these instances, I will note in my notebook that I am transitioning to my text editor and the file path for where I am saving. In my text editor, I will code along and use comments if needed to explain the code. I will also write in my notebook any major concepts to highlight or questions that come up.

Wrapping up

At least once a day I go back through my notes to check off any tasks I have completed, migrate tasks that still need to be completed, and update my index. This is a super important step!!! If you forget to do this it can quickly become a larger task than it needs to be. I find it is a great thing to get done when I have a few minutes at the end of the day.

At the very back of my notebook, I have a long term task list. When I go back through my notes to check off my checklists that develop, I will transfer anything long term to this back page. This allows me to remove these tasks from my immediate to do’s and create a log of tasks for later in my program.

So far I have found this system easily adapts to what I am learning and can be tweaked pretty easily as I need to. However, it is not going to work for everyone. Take what I have written and adapt it to what will work for you. Maybe stickers are not your thing, you can easily just have a symbol you put in your notes to indicate a typed note. Maybe you think this is way too much but have never thought of including an index. Take some of the ideas you got from this and get back to learning how to code!

Thanks for reading all the way though! Let me know in the comments if this helped you, if you have any questions, and how you like to take your notes!