I write up my teaching practice as it happens: what I did, what it was for, what I used, what happened in the room, and what I'll change next time.
Entries about lessons and approaches: the context, the intent, what I ran, what resources I used, how students responded, and what I'll adjust next time.
I build a tool, use it daily for a fixed period (usually 30 days), and then write up the real findings: friction, surprises, what stuck, what failed, and what I'd change.
I'm planning the structure for these first — so the write-ups are consistent and useful.
I'm Reece. I spent years in software development, working across insurance, vehicle sales, and a mix of charities and businesses. I later moved into teaching, gaining experience in a secondary school, and these days I lecture in Computer Science at a university.
This site exists for one reason: to document what I try and what happens without pretending every idea is a win. If you're a teacher, a developer, or somewhere in the middle, feel free to borrow ideas (or challenge mine).
P.S. I'm keeping this practical: short entries, honest outcomes, and clear "next time I'll..." notes.
This isn't a highlight reel. It's process notes. Some entries will be messy, some will contradict earlier entries, and some will document failure, that's the point.