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. Answer the three prompts below, a few sentences each, written the same day as class. Ten minutes, done.
The three prompts
- What we did — the facts, briefly. The warm-up, the program you typed, where you and your partner got to before the bell.
- What surprised me — one specific moment you did not expect. In the code, in the machine’s behaviour, or in yourself.
- Where I stand with programming right now — honestly. Some people arrive having written code for years, some have never seen a terminal, and most are somewhere in between and quietly convinced they are the only one. Naming yours is the first piece of data in the record.
What honest looks like
These fragments are the register to aim for — plain, specific, true:
“My program printed my name five times because I wrote the print line five times. Sam did it in two lines with a loop. Mine still worked though. I keep thinking about that.”
“I typed the example exactly and it still crashed. Turned out I had a capital P in Print. The computer does not guess. Kind of unsettling. Kind of fair.”
“I assumed everyone else in here had coded before. Then half the room got the same missing-quote error at the same time and the room went ‘ohhh’ together. Okay. Maybe this is learnable.”
None of these is polished and none of them performs for a reader. Each names a real moment and stays with it, which already beats a page of “coding was fun today, I learned a lot.”
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. The honesty you risk in week one becomes your best evidence of growth by the end — but you decide who ever hears about it.