Welcome Back to The Insight Letter!
Volume One: Third 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 felt like running on a treadmill while juggling plates, busy, overwhelming, and less productive than I had hoped.
I spent most of it juggling multiple projects at once: trying to create resources for the new WACE Computer Science ATAR syllabus, keeping up with my studies, and managing smaller personal projects. In the process, I felt the familiar tension between everything I wanted to accomplish and the limits of what I could actually execute.
This edition is a reflection on that overwhelm, why it shows up, and what it has taught me about focus, priorities, and making progress even when life feels chaotic.
Growth in the Chaos…
This week, I felt the pressure of creating something from scratch: new CSC ATAR resources, fresh questions, and explanations of concepts I wasn’t even sure anyone would understand the way I intended.
Every sentence, every example, felt like a test, would it make sense? Would it actually teach anything?
It was overwhelming, less productive than I’d hoped, and full of moments where I doubted whether I could get it right.
Even under the pressure of writing new questions and explanations from scratch, I started noticing patterns in what worked, what confused me, and where small adjustments could make a big difference, insights that became clear before any of the work was “finished.”
1️⃣ Small, iterative experiments beat big leaps
Instead of trying to finish entire resources in one go, I tested small chunks, writing a single worked example, drafting one concept explanation, or creating one diagram. Each tiny experiment revealed gaps I hadn’t noticed and gave me a clearer sense of what works before I invest too much time.
2️⃣ Overwhelm exposes the real bottlenecks
When everything demands attention, it becomes obvious which parts of a project are slowing you down, unclear instructions, missing examples, or repetitive tasks. Recognising these bottlenecks early lets you address the root cause instead of just spinning faster.
3️⃣ Partial work still teaches lessons
Not everything got completed this week. Some drafts will need rewrites, and some ideas won’t be used. Yet even unfinished work clarified concepts, helped me test explanations, and gave me a better sense of the audience’s perspective. Progress isn’t always about finished products, it’s about learning faster and making better decisions next time.
This week reminded me that productivity isn’t about cramming tasks or finishing everything on a list. It’s about experimenting, noticing patterns, and making small, meaningful choices that compound over time.
Thoughts for the Upcoming Week
Thinking Out Loud
I spent hours on the very first chapter of the new CSC ATAR resources, just deciding the questions, examples, and explanations for one topic. Doing it alone made everything so much harder. Without feedback, every choice felt like a guess: Is this question clear? Will anyone get this explanation? Am I even starting in the right place?
At first, it was frustrating, and I almost treated it like a barrier. But by the middle of the week, I started noticing something new: doubt isn’t just a warning that you might be wrong, it’s also a lens. It highlights the places where your thinking isn’t fully formed, where assumptions hide, and where experimenting can lead to real breakthroughs.
Some drafts were messy, some questions confusing, and some explanations awkward, but those felt like the most valuable moments. They exposed blind spots I wouldn’t have seen otherwise and forced me to make decisions I could actually trust. For the first time, doubt didn’t feel like a barrier, it felt like a guide.
If you’ve ever had to start something completely alone, where every choice is uncertain, you’ll realise that paying attention to what feels uncomfortable can teach you faster than getting everything “right” the first time.
A question I’m thinking about this week
It’s easy to measure productivity by finished tasks, but this week showed me that sometimes the most valuable work isn’t fully “done.”
Here’s what I’ve been reflecting on:
1️⃣ Which parts of my projects are teaching me the most, even if they’re incomplete?
2️⃣ Where am I feeling uncomfortable, and what is that discomfort pointing toward?
For me, the answer came through creating new CSC ATAR resources. The questions that felt messy, the explanations that needed multiple rewrites, and the drafts that weren’t ready to share, they weren’t failures. They were signals of what I needed to focus on, clarify, and improve next.
Sometimes the most important lessons come not from finished work, but from the pressure and uncertainty of trying something new. The challenge isn’t just to complete tasks, it’s to notice the patterns and insights hidden in the messy middle.
Wishing you a week of growth and momentum!
Kind Regards,
