• Day Summary

  • Context

• Reading

• Coding Practice

• Reflection

• Key Learning

• Total Time Spent

Day Summary

Right, so what happened? Yesterday was a break day—I took a day off. I had this thought about a pattern I noticed in my work and life, and I realized it might apply more generally. A bit of research later: it does, to pretty much everyone. It’s an old mechanism we’re never taught. Funny how that works—the things that explain how you function are the ones you have to discover because nobody tells you. Maybe people don’t realize, or they assume it’s obvious...

I slept three hours and a few minutes. Not much, but I’ll manage. I’ve switched to a 60-minutes-per-day Daily Quest sprint for this week (there’s a system behind it; I’ll write a separate post). I made four pages of progress—small, but decent given the sleep debt.

The rest of the time got eaten by me arguing with my AI about vocabulary—choice of words. A waste of time, really. But the annoyance probably means I’ll remember it tomorrow since there was emotion behind it. The task at hand is learning how Rust works and how to use it; nitpicking terms that don't add to learning behavior or application is dead weight right now.

Today will be a big chunk of job work—~10 hours—which will be a bit strenuous given the sleep. It’s also moving day: I’m finally moving into the new apartment, moving more stuff between places, and sleeping there for the first time tonight.

Adventurous times.

• Daily Quest: 60 minutes (reduced-load week).
• Reading (60m, +4 pages): p.190 → p.194.
• Concept Q&A: debated generics mental model with ChatGPT (beginner-friendly analogy vs. jargon).
• Coding: none today.

Context

• Week 3 = reduced workload: doing 1-hour sessions instead of 90 minutes (reasons to be posted separately).
• Sleep: <4 hours — capacity low, but still moved the ball.

Reading

• 60 minutes, ~4 pages (190 → 194).
• One note captured; progress slowed by a deep dive discussion on generics.

Coding Practice

• None (reading + concept debate only).

Reflection

• The 60-minute session intentionally felt easy — that’s the point this week.
• Arguing over terminology (e.g., “monomorphization,” “zero-cost”) isn’t useful at a beginner stage; tying concepts to familiar ideas is.
• The aim is to understand Rust enough to build the IoT project, not to memorize the cabals secret magic words.

Key Learning

• Beginner mental model for generics:
  Think of fn foo<T>(...) as adding a type parameter that tells the compiler: don’t lock the concrete type here; when code elsewhere uses foo with a specific type, create a copy of it and initialize it with that type.
  Useful takeaway: concept > jargon while learning (the names can come later).

Total Time Spent

• Reading: 60m
• Coding: 0m
• Daily total: 60m

PCT (Project Cumulative Time): 22h29m