The first entry in your Code Journal is the hardest, because the page is blank and you do not yet trust what belongs on it. So for week one only, the entry is guided. Class one hands you a working program nobody in the room wrote and asks what it does, so you will have plenty to write about.
Answer the three prompts below, a few sentences each, the same day as class. Ten minutes, done.
The three prompts
- What we did with the inherited program — the facts, briefly. What you tried first, what you tried second, and what actually told you something.
- The moment it started making sense — or did not — one specific moment. The line you changed, the value you printed, the experiment that answered a question. If it never started making sense, say that instead and say where you stopped.
- Where I stand right now — honestly, on two axes. How comfortable are you writing code, and how comfortable are you reading somebody else’s? Most people arrive with a large gap between those two, in the same direction, and quietly assume they are the only one.
What honest looks like
These fragments are the register to aim for — plain, specific, true:
“We read it for eleven minutes and learned nothing. Then Dev ran it with an empty file and it crashed, and suddenly we knew where the input was handled. Running it beat reading it and I did not expect that.”
“I can write a loop from scratch but I froze completely looking at someone else’s forty lines. It is the same language. I do not know why one is so much harder than the other.”
“I found a comment that said ‘do not remove, breaks the export’. Removed it to see. It broke the export. I feel like I should be embarrassed but honestly that is the most I learned all period.”
None of these is polished and none performs for a reader. Each names a real moment and stays with it, which already beats a page of “today we looked at some code.”
Nobody reads this but me
As Code Journal promises, entries are private. I read them, other students never do, and nothing you admit here is quoted or used as an example without your explicit okay. That promise holds even when the honest thing to write is about your team. The candour you risk in week one becomes your best evidence of growth by the end of the course — but you decide who ever hears about it.