Free to read link (Non-members)
I was six days into my 90-Day War Time Routine and I have myself a 3 day break from writing.
FYI, the coding streak is alive.
The problem-solving momentum is high (In fact, higher).
I’ve been covering graphs.
So, why did I change the process of writing what I’m doing everyday?
Because I noticed a bug in my process.
Every night at 11:30 PM, instead of winding down or getting an extra 30 minutes of sleep, I am stressing about formatting a Medium article, finding SEO tags, and making sure my Day X title sounds catchy.
No, thank you.
When you tackle a challenge like #100DaysOfCode, it is easy to fall into the Meta Trap where talking about the work becomes more important than the work itself.
On day 7, I found myself rushing through a problem just so I would have something to write about, rather than sitting with the problem and deeply understanding the edge cases.
That defeats the entire purpose of this roadmap.
So:
Bi-weekly updates:
Starting today, I am shifting from daily logs to Bi-Weekly Updates.
The Logic:
- Higher Signal, Less Noise: Instead of “Day 4: I solved 2 easy problems,” I can group an entire topic (e.g., “The Graph Theory Week”) into one comprehensive breakdown.
- More Sleep: This requires recovery. Those 45 minutes of writing time are better spent on rest or one extra LeetCode Hard.
- Better Technical Depth: It allows me to write articles that actually teach you something (like my recent piece on dopamine), rather than just listing what I did.
The Commitment Remains
To be clear: The Code Streak is daily. I am still grinding 7 days a week.
But the Public Log will now drop on specific weeks (e.g., Wednesdays and Sundays randomly in 2 weeks or so). This keeps the accountability alive without turning me into a content churning machine.
This is a Rough Notebook, and part of using a notebook effectively is knowing when to write and when to shut up and work.
See you in a few days with the Graph Theory deep dive.