As we grow older, many of us quietly abandon structured study. We trade textbooks for Stack Overflow, deep reading for bug fixes, and deliberate practice for reactive problem‑solving. The result? We stop growing at the rate we used to.

I fell into that trap. So I built two things: a study scaffold (phases, books, mini-projects, milestones) and this blog to document the journey. This post explains the learning system behind both.

My Three‑Part Study Framework#

1. Active Recall over Passive Reading I used to highlight books and call it “studying.” Now I close the book after each chapter and write down everything I remember from memory. If I can’t reproduce a concept in plain language, I haven’t really learned it, I’ve just recognized it.

2. Project‑Based Immersion Every topic gets a tangible output. The mastery repo maps each phase to seven ~20-minute API mini-projects plus a larger milestone (board game, DSL gem, Rails app). My daily outputs include:

• A working code snippet or mini-project
• A diagram or visual note
• Or, as you’re seeing now, a blog post

Learning without building is like reading about swimming without ever getting wet. The golden rule: protect the daily 15–20 minute practice block.

3. Spaced Repetition with a Personal Twist

I use a simple Notion database to track what I’ve studied, with review dates scheduled for 1 day, 7 days, and 30 days later. At each review, I quiz myself on the core ideas. If I hesitate, it goes back into the rotation.

What You Can Expect Here#

I’m not aiming for perfection, I’m aiming for consistency. The goal is to document the journey, not just the destination.

So, here we are. This post exists to break the inertia. The next one will be technical.

Be curious, not judgmental.