Welcome Back to The Insight Letter!
Volume One: Second 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 was quieter than I expected, but more revealing than it looked on the surface.
I spent most of it reworking my developer portfolio, getting stuck on design decisions, and feeling that uncomfortable gap between how I want things to look and what I can currently execute.
This edition is a reflection on that gap, why it shows up, and what it usually means when it does.
The Taste Gap…
For a long time, effortless design felt like something I could admire but never fully control.
I can write code, make things work, and structure logic perfectly. But turning that into layouts, spacing, and colours? Always frustrating.
It wasn’t that I didn’t care or wasn’t trying — I just didn’t have a system to experiment and learn in a way that made sense for me as a developer.
That’s when I realised the problem wasn’t my taste or effort; it was the process. I was jumping between tools, guessing at colours, and manually adjusting layouts without understanding why something worked or didn’t.
Design matters because it shapes how people experience what we create. It’s not just about making things look good: it’s about making interactions feel intuitive, ideas easier to grasp, and work that actually solves problems instead of confusing people. Even as a developer, understanding design helps me make my code meaningful, not just functional.
It’s the difference between building something that works and building something people actually want to use and understand.
Every switch between apps, every trial and error, made the gap between my vision and execution feel bigger. I needed a way to bridge code and design so I could learn by doing, not just by guessing.
My Solution
AI Assisted Design for Developers
Figma AI in Action preview
Instead of fighting the disconnect between development and design, I started using tools that meet me in my comfort zone as a developer: tools that allow me to experiment, iterate and learn by doing.
Here are my top recommendations:
1️⃣ Canva: manual design experimentation
Canva lets me test colours, spacing, and layouts without worrying about code. I can move elements, swap fonts, and quickly see what works, then bring those insights into my projects.
2️⃣ Figma AI: design and code in one place
Figma’s AI lets me generate layouts, see the design, and peek at the CSS/HTML behind it. It’s like looking under the hood of a car I’ve been driving for years, suddenly I understand how design translates into real code.
Even a few hours of AI assisted experimentation gave me insights I can carry forward. These tools don’t replace skill; they accelerate understanding, the fastest way I’ve found to level up in design.
Thoughts for the Upcoming Week
Growth in small increments
I have been thinking a lot about how growth actually happens. It rarely shows up as a big breakthrough — most of the time, it consists of tiny, almost invisible choices stacking up over time. There is this idea (and some simple math behind it) that improving just 1 % every day can make you nearly 38 x better in a year. It blew my mind when I realised how small tweaks really do compound. learningscience.net
For me this week, growth looked like paying attention to the gap between how I wanted my portfolio to look and what I could actually make happen. I took notes on what felt off and what worked, and suddenly small mistakes turned into insights I can reuse next week.
Here is what you can take from it: pick one thing you want to improve, track the little wins and the frustrating failures, and reflect at the end of the week. Over time, those tiny experiments add up, skills you once thought were hard start feeling natural, and what once felt impossible slowly becomes just another tool in your toolkit.
Growth isn’t glamorous, but if you notice the little shifts, you will see it everywhere.
A question I’m thinking about this week
Over the last week, I’ve been asking myself what actually moved the needle this week versus what just felt busy. It’s helped me notice patterns I usually miss.
If you want to try it too, here’s what I’m reflecting on:
1️⃣ What am I uncomfortable with right now, and what skill might that discomfort be pointing toward?
For me, the answer is product design.
The frustration I felt while working on my portfolio wasn’t a sign that I’m bad at it. It was a signal that my standards have grown faster than my skills, and that there’s something new to learn here.
If something feels frustrating or clumsy, it might not be a failure. It might be the next thing to learn.
Wishing you a week of growth and momentum!
Kind Regards,
