Coding journal for learning to code, with a 100-day streak tracker

This coding journal gives you 30 undated pages to plan your learning, record each coding session, keep a 100-day streak alive, map out projects, chase down bugs and grow a portfolio. It suits self-taught beginners, career changers, students and developers picking up something new.

You get US Letter and A4 PDF files as an instant download. Nothing is shipped, so you can print it before your next session.

How a coding journal keeps you consistent and confident

Learning to code can feel endless. Here you start by writing your reason for learning, sketching an eight stage roadmap and listing the languages and tools you picked. As you go, tick off each core idea when you first meet it, when you use it and when you can explain it to someone else.

Two kinds of session log, one detailed and one quick, record your progress, the spots that tripped you up and the trick that solved them. A streak tracker for 100 days plus two pages with a single line per day keep momentum going. A bug log, a step by step debugging sheet and a personal list of error messages make every mistake teach you something, and a portfolio tracker and write-up page let you show what you have made. Nothing is dated and no language or course is assumed, so print the logs again whenever you need.

Who this programming journal is for

• Self-taught beginners working on their very first programming language
• Career changers going through an online course or a coding bootcamp
• High school and computer science students who prefer paper notes
• Anyone taking on a 100-day coding challenge who wants an easy way to stay on track
• Working developers picking up a new language or tool who want notes, bugs and projects in one place

Design and printing

• Minimal, elegant pages: white with soft blush pink details that use very little ink
• Wide margins, so a home printer will not trim anything
• Portrait layout sized for US Letter (8.5 x 11 in) and A4 (210 x 297 mm)
• Undated, so day one can be any day of any year
• Generic by design: no specific languages or brands printed, so it suits web, data, mobile, games or automation
• Keep it in a binder or on a clipboard, or have a print shop spiral bind it

Inside the coding journal: 30 pages

1. 1Cover with the contents and lines for your name and start date
2. 2How to use this journal: five steps to get going, the few things you need, a prompt to finish (I'm learning to code because) and a printing tip
3. 3My coding why and goals: your reasons, where you hope to be a year from now, where you are starting, how much time you can give, a 6 line goal table, how you learn best, what you do when stuck and a note to your future self
4. 4Learning roadmap: an eight stage path that starts with the fundamentals and ends with sharing what you made; each stage gets two planning lines, a target and a tick box, plus the route you picked and the milestone that excites you most
5. 5Languages and tools list: 14 lines for each language or tool, its purpose, a 1 to 5 skill dot scale, start date and next step, plus tools to try later, setup notes and shortcuts worth remembering
6. 6Core concepts checklist: 24 concepts sorted into basics, data, building and thinking, with extra blank lines, each marked met, used and can explain, plus concepts that still feel fuzzy and one that finally clicked
7. 7Monthly plan: an undated calendar where you circle each coding day, with the month, learning focus, target hours, goals, project milestones and the courses or chapters to cover
8. 8Weekly study plan: focus, main goal and hours planned, a day by day grid from Monday to Sunday with what to learn or build, time, resource and done, then practice tasks and questions to look up
9. 9Daily coding log: start, finish and total time, the topic or project, energy and focus rated 1 to 5, the day's goal and resource, what you worked on and learned, where you got stuck and how you got past it, a dot grid box for a code snippet, the win of the day and plans for next time
10. 10Quick session log: 18 lines for date, minutes, topic or project, what you did and a win, with totals and your best session
11. 11100-day streak tracker: a circle to fill for each of 100 numbered days, notes on day one and the goal for the final day, treats at the quarter marks (25, 50, 75, 100) and a line for what I hope to reach by the end
12. 12100-day log for days 1 to 50, a numbered line for each day, plus your proudest moment and toughest part so far
13. 13100-day log for days 51 to 100, a numbered line for each day, plus your proudest moment and toughest part so far
14. 14Project planner: name, start and target dates, the idea in one line, who it serves, must-have features and extras for later, languages and tools, what you will learn, a box for a sketch or wireframe, what done means and the repository or folder
15. 15Project task board: three columns (to do, doing, done) with 14 tick lines in each, 5 milestones and their target dates, what is holding you up and who to ask for help
16. 16Bug log: 14 lines for date, the bug or error, where it happened, cause, fix and time spent, plus repeat mistakes and debugging tricks that work
17. 17Debugging worksheet for one stubborn bug: what you expected versus what happened, 7 steps to reproduce it, five debugging steps, ideas tested, the fix and what to remember next time
18. 18Common errors and fixes, your personal error dictionary: 16 lines for the message, what it usually means and the first thing to try, plus where you look for answers and how you search well
19. 19Concept notes: name the idea and its language or topic, explain it plainly, compare it to something from everyday life, show sample code or a diagram in a dot grid box, note when it fits, typical mistakes, open questions and linked ideas, then rate from 1 to 5 how well you could explain it
20. 20Syntax cheat sheet: 18 lines for what I want to do, the syntax or command and an example
21. 21Coding glossary: two columns of 17 lines each for terms and their meaning in plain words
22. 22Practice problems log: 15 lines for date, problem, topic, difficulty (easy, medium, hard), time, solved and revisit, plus patterns you notice and a problem you are proud of
23. 23Resources list, ready for you to fill: 16 lines to note each title, what kind of resource it is, where it lives, your progress and a rating out of 5 dots, plus what to try next and tips from friends
24. 24Milestones and wins: eight dated firsts, aha moments, encouraging words from others and evidence of how far you have come
25. 25Weekly review: days coded, hours, a 1 to 5 rating for the week, what you learned and built or finished, what was hard and what helped, a concept to revisit, wins and next week's focus
26. 26Monthly progress review: a 5 week overview (hours, main topic, best win), new skills, project progress, roadmap progress, what is still confusing, habits, changes to make, next month's goals and confidence from 1 to 10
27. 27Portfolio tracker: 12 lines for each project, what it does, the skills it shows, the link or location and status, plus portfolio to-dos and ideas for new projects
28. 28Project write-up: the problem, your solution, features, languages and tools, the biggest challenge and how you solved it, a box to sketch a screenshot, lessons learned and a one sentence summary
29. 29Dot grid page for writing code by hand, diagrams, flowcharts and wireframes
30. 30Lined notes page with a date line

Files you download

• Coding Learning Journal, US Letter PDF (30 pages)
• Coding Learning Journal, A4 PDF (30 pages)
• Read Me First, a short printing guide (PDF)
• Tip: the roadmap, concept checklist and portfolio pages only need one print; the daily log, 100-day log, bug log, concept notes and reviews can be reprinted whenever you need more

How to download and print

• Check out with PayPal, a debit or credit card, Apple Pay or Google Pay. Your download page opens as soon as the payment goes through.
• We email the same private download links to you, so you can download your files again later.
• Open the PDF in a free reader such as Adobe Acrobat Reader and print at 100% or Actual size.
• Print only the pages you need, as often as you like, for your own personal use.

Good to know

• This journal is a PDF for printing and writing by hand, not a hyperlinked digital planner. You can still import it into most note taking apps and write on it.
• It is a digital product, so nothing physical is mailed.
• Printed colors may look slightly different from your screen.
• Licensed for personal use. Sharing, reselling or redistributing the files is not allowed.
• Digital files cannot be returned. If a file does not open or print correctly, email us and we will help right away.

How this was made

Designed and written by PetiteDiary. AI tools helped draft parts of the text, and some background scenes in the preview images were created with AI. Every page was designed, reviewed and checked before release.

Questions about the coding journal

Related searches