Retaking Coding Exercises: Getting Back in Shape

Lately, I found myself retaking coding exercises on HackerRank—not because I have an interview coming up or because I’m preparing for some specific challenge, but purely for personal growth. I realized that with the rise of AI tools and my everyday work routines, I’ve been thinking less and relying more on shortcuts. While leveraging technology is great, it felt like my problem-solving muscles were getting rusty. To put it simply, I wanted to get back in shape, mentally.

Realizing I’m Out of Shape

The turning point for me was when I attempted to solve the Magic Square problem. It’s a classic algorithm problem, and I was surprised at how complicated I was making it. I spent a whole hour struggling with it before I accepted that I was overcomplicating things. Eventually, I ended up researching the math behind it and asking AI for guidance—not the solution, just some hints. That moment made me realize how much my problem-solving instincts had dulled. It was a wake-up call.

On a daily basis, I’m coding similar types of solutions at work—front-end components, state management, API integrations—but when it came to something outside that routine, I felt almost… lost. It was like my coding brain had tunnel vision, only equipped for what I regularly see, but not ready to explore new terrains. That’s when I knew I had to do something.

What “Being in Shape” Means to Me

For me, being “in shape” as a developer means having the ability to think deeply, solve problems creatively, and execute efficiently without leaning on AI or Stack Overflow for every little thing. It’s about synergy: speed, accuracy, and creativity all coming together. I want to be able to think through solutions first, write code quickly, and then debug with minimal friction. It’s not about perfection—it’s about sharpening those mental gears again.

Focusing on the Basics

Right now, I’m diving back into the basics: algorithms and data structures. I’m not aiming for any specific stack-related problems—just pure problem-solving and logic building. I want to be confident that if you throw me a classic algorithm problem, I can solve it—not just Google it.

Even just starting with these exercises has made me change the way I code. Before, I would sometimes write bits and pieces of logic and then add features as I went. Now, I’m more disciplined—I write the core logic first, clearly understanding what each variable does before adding anything else. It’s a more structured way of coding, and it’s already helping me think more clearly.

Making Time to Practice

Balancing this with work hasn’t been too challenging, mainly because I’ve dedicated my nights to it. Sometimes it’s spontaneous, but mostly, I block out that time to just focus on solving problems. It’s not always easy after a long workday, but the mental workout is definitely worth it.

Advice for Other Developer

If you’re reading this and feel like you’ve been relying too much on AI or Stack Overflow, I recommend giving platforms like HackerRank, LeetCode, or Codewars a shot. It’s not about proving anything to anyone—it’s about sharpening your own skills. One thing I’d emphasize: study math. It’s the backbone of logical thinking, and you can’t solve complex problems without understanding the basics of how things work.

Are Platforms Like HackerRank a Good Measure?

For me, they are—at least when it comes to logic and raw problem-solving skills. They might not fully represent real-world application development, but they definitely keep your brain sharp. If anything, it just makes you faster and more aware of your code when building actual features.

What’s Next?

I plan to keep going. I’ve realized how important it is to maintain this discipline, and I don’t want to fall back into lazy habits. My next steps are to continue practicing, integrating these exercises into my routine long-term. The goal? To make sure that when I face a problem, I solve it by thinking through it—not by immediately asking AI for the answer.