2025-08-03

#1 Developer Mindset | One Problem a Week Can Change Everything

“Compound interest is the eighth wonder of the world. He who understands it, earns it... he who doesn't, pays it.”
— Albert Einstein

Hello Reader,
Hope you’re having the best time of your life. ✨

Welcome to the very first issue of Developer Mindset, a weekly letter from one developer to another. I’m super excited to hit send on this.

For the past few months, I’ve been trying a quiet little practice that’s had a powerful impact on my work, my startup, and how I think about code. Today, I want to share that philosophy with you.

One Problem a Week

To keep growing, and not feel stuck in a routine as a developer (or in life), you don’t need to build the next big thing or spend hours on Leetcode.

You just need to solve one small problem each week. Consistently.

I call it the One Problem a Week Challenge. It’s not for your portfolio. Not for interviews. Not even for your side project. It’s for something far more powerful: Your Curiosity. You know that moment when you think, "Huh, I wonder how that works…” Follow that thread.

For example:

Curious about drag-and-drop? Build a simple Kanban board. You'll dive into mouse events, DOM manipulation, and state.
Wonder why some websites load faster? Test a few in dev tools. You’ll explore image optimisation, caching, and UX trade-offs.

This isn’t about productivity. It’s about staying mentally alive. And here’s the magic: after a year of this, you’ll have solved 52 problems. You’ll start seeing patterns. You’ll become the kind of dev who just… figures things out.

This Week’s Challenge

Solve one problem outside work:

Pick something small - a bug, a feature, a curiosity
Keep it under 2 hours
Share it

Need an idea? Build an analogue clock using HTML, CSS, and JavaScript.

Coding Tip – TypeScript Edition

Did you know TypeScript can validate string patterns at compile time?

Here’s how:

Why this matters:
Instead of runtime validators or regex, TypeScript knows the format you expect. Catch malformed emails, broken endpoints, or typos before running your code

Template literal types = compile-time string validation.
Mind = blown 🤯

Social Media Highlight

🎬 33 Days of Software Engineering
We’re currently exploring the mindset and principles that turn a good developer into a great engineer. We’re on Day 8, diving into the SOLID principles.
Check it out on YouTube or follow along on Instagram/TikTok.

Final Thoughts

This is the beginning of something special.
Thanks for being here. I’ll keep it honest, helpful, and hopefully a little inspiring too. If this resonated with you, reply and tell me: What problem are you solving this week? I would love to hear from you. Take care.