Sleep IoT Quest - Day 12 Progress Update
Day Summary
All righty - got another day of progress done. I’ve stayed on track for a while now, kind of proud of that, despite it being two days since I last read a page. There were days in a row where I was only reading, so having days where I’m only coding - and coding from memory - is valid.
The main tactic that helped when I got stuck on the remembering part (recreating a coding kata from memory) was chunking it down - splitting it into several parts so I don’t try to remember too much at once. That got me unstuck.
I’ve figured out that maybe 60-minute sessions instead of 90-minute sessions are more in line with a natural flow. Ninety minutes is capacity-stretching; sixty is easy - so easy that, with a short break, I can just do two of them. I’m considering that for next week’s framework update: do a 60-minute Daily Quest, with an optional second 60 minutes as energy allows. That may speed me up or slow me down - I don’t know — but it feels better. The 90-minute block is like high-intensity interval training: great for increasing overall capacity over time; not so great to run daily while still building it. It’s doable - I’ve done it - but some days (especially on little sleep) are questionable in efficacy.
So, probably next week I’ll downsize the Daily Quest to 60 minutes (cleanly divisible into 3×20), with an optional second 60. Overall I’m happy with today’s progress: I got unstuck and was able to remember most of it. I did have to look up two things in the first half - annoying, but still progress.
In the end, the goal isn’t to read the book as fast as possible; the goal is to understand Rust well enough to implement the IoT project.
- Daily Quest: 90 minutes (completed).
- Timely Start: began 3 minutes late → 94% (≥85% = pass).
- Coding: finished first half of the new enums/Option kata from memory (clean); did guided coding for the second half; started from-memory recreation (made it ~halfway).
- Sleep: ~7h+ (solid).
- Reading: none today.
Context
- Yesterday’s sleep wobble is recovering.
- From-memory was stuck a day ago; unstuck now and still improving.
- Two sections remain to finish the kata.
Reading
- None today (all effort on coding/retention).
Coding Practice
- From memory — Kata (first half): complete and clean.
- Guided — Kata (second half): implemented with notes.
- From memory — Kata (second half): started, reached ~50% before time.
- Noted a compiler warning about dead code on a tuple-like enum field (
u8) despite methods using it; also hit a dereferencing required case.
Reflection
- Considering 60-minute blocks for sustainability (likely 2×60 vs 1×90).
- Chunking continues to work: smaller scope → better focus → higher recall.
- Protocols help: even with a slight late start, the DQF block preserved the win.
Key Learning
- Process: Split complex exercises into manageable chunks, then build → delete → rebuild from memory.
- Rust nits to revisit: enum field usage that triggers dead_code warnings; when/why explicit deref is required.
Total Time Spent
- Reading: 0m
- Coding: 90m
- Daily total: 90m
PCT (Project Cumulative Time): 17h39m