Welcome Back to The Insight Letter!
Volume One: Twelfth Edition
For those who are new here
Hi, I’m Anisha!
I’m a front end developer and software engineering student, and this newsletter is where I document my learning as I grow through technology, productivity, and life.
I created The Insight Letter as a space to share what I’m discovering throughout my learning journey from studying computer science, mathematics, and engineering, to building better systems, habits, and soft skills for navigating the real world. Some weeks it’s a lesson from university, sometimes it’s a self paced online course, and other times it’s a reflection that changed how I think.
Along the way, I share the insights and approaches that have helped me most so you can pick what resonates, adapt it to your own life, and skip a bit of unnecessary trial and error.
If you enjoy learning alongside someone who’s curious, honest about the process, and focused on growing consistently, you’ll feel at home here.
Welcome back to The Insight Letter!
This week, I noticed something that completely changed how I think about progress.
For a long time, I was taught that consistency meant never missing a day, never breaking a streak. Every productivity book, planner, and newsletter I followed drilled the same message into me: if you miss a day, you fail. To some extent, it may be true but hear me out.
And for a while, I lived by that rule. I counted streaks like scores, measured progress by perfect attendance in studying, coding, building projects and even tracking my “daily productivity percentage score”. Missing a day felt like losing all the work I had done.
Then life started proving me wrong.
Over the past two years, I’ve faced challenge after challenge, hospitalisations, car accidents, periods where everything that could go wrong did. Days, weeks, even months of plans completely wiped out. The old “never fail” metric suddenly became meaningless.
“Return Speed”…
I realised what really mattered wasn’t how long I stayed on track, it was how fast I got back up each time, speed.
Every time I returned after a pause, I was able to pick up more quickly, focus more sharply, and avoid the mistakes I had made before. Missing a week didn’t erase the skills I’d learned; in fact, the gap often gave me clarity on what mattered most.
And that’s when it clicked: life will always give you hard problems: something I had a hard time accepting. The people who succeed aren’t the ones who never fail, they’re the ones who fail, recover, and accelerate.
Why Return Speed Matters More Than Streaks
Psychologically, perfection and streaks create a trap. When progress is measured by “never failing,” every slip triggers guilt, shame, and self-criticism. Your brain starts associating growth with fear of failure instead of learning, which slows you down over time.
Logically, streaks reward duration, not effectiveness. Missing one day wipes your streak, but does it really erase the skills, knowledge, or experience you’ve built? Of course not. Meanwhile, the ability to restart quickly compounds over time: each recovery reinforces habits, teaches lessons from mistakes, and accelerates growth.
Return speed captures the real essence of progress: it measures resilience, adaptability, and learning efficiency, all of which carry far more weight in the long term than the superficial metric of “perfect streak.”
Once I understood this, it changed how I approach learning, projects, and even life challenges. Instead of fearing failure or breaks, I started tracking how fast I could recover & rebuild momentum and that’s when I noticed exponential growth happening.
The Return Speed You’ve Never Thought About
Return speed is about more than just getting back to your routine. It’s the ability to restart with more clarity, more focus, and more intentionality than before. It’s about using the pause, the gap, the failure, the interruption, as fuel and for me: to stop damaging my mental health.
Here’s how I apply it in practice:
1️⃣ Reset Immediately. Even in Small Steps. Missed a day of studying or coding? Start with the smallest action, open the project, write one line of code, or review one note. The key is to reignite momentum immediately, even if imperfect.
2️⃣ Reflect Before Restarting. Don’t just jump back in blindly. Ask: What caused the pause? What can I do differently this time? Using gaps as data gives your return speed exponential power.
3️⃣ Prioritize What Actually Moves the Needle. Not all actions are equal. After a pause, focus on the 20% of tasks that create 80% of progress. This ensures your return is faster and more effective than before.
4️⃣ Build “Recovery Habits.” Have systems in place that make restarting easier: templates, checklists, quick wins. The faster you can step back into flow, the faster your return speed compounds.
5️⃣ Track Your Return, Not Your Streak. Instead of counting days in a row, track how many days it took for you to recover each time. Over months, this gives a far more accurate measure of real growth than perfect streaks ever could. More importantly, it removes losing hope from the equation which is far more dangerous.
A question I’m thinking about this week
Over the last week, I’ve been asking myself: which of my setbacks are actually accelerating my growth, rather than slowing me down? It’s helped me notice when I only focus on streaks or “perfect” progress.
If you want to try it too, here’s what I’m reflecting on:
1️⃣ Which moments of falling behind are teaching me the most about recovery?
For me, the answer is learning to restart quickly after interruptions, whether it’s missed coding sessions, delayed projects, or weeks when life completely derailed my routines. The frustration I felt during these pauses wasn’t failure; it was a signal that I had a chance to practice returning faster and smarter.
A setback might be the exact thing that teaches you how to accelerate after falling, the skill that actually compounds over time.
Wishing you a week of growth and momentum!
Kind Regards,
