Feeling Stuck After 3 Years? How to Know if You’re Improving
by Arif Ikhsanudin, Backend Developer
You’ve been coding for a few years, but it feels… flat.
No big jumps, no clear progress—just work on repeat.
Progress Doesn’t Always Feel Obvious
Early on, growth is visible. You learn syntax, frameworks, tools.
Then suddenly, it slows down.
- You’re no longer Googling basic things.
- Tasks feel routine instead of challenging.
- You stop getting that “aha” moment as often.
This doesn’t mean you’re stuck—it often means you’ve leveled up.
Look Beyond Code Output
Improvement isn’t just about writing more code or learning new tech:
- Are you making better decisions before coding?
- Do you spot edge cases earlier?
- Can you explain systems more clearly to others?
Thinking quality is a stronger signal than typing speed.
Pay Attention to What Feels “Easy” Now
Things that used to be hard often become invisible:
- Debugging takes less time.
- You understand system flow without tracing everything.
- You make fewer “random fixes” and more intentional ones.
It’s easy to ignore this because it feels normal now.
Ease is often the result of past growth, not lack of progress.
Compare Your Past Self, Not Others
This is where many people get stuck mentally:
- Comparing to senior engineers can feel discouraging.
- Comparing to peers can feel inconsistent.
- Comparing to your past self shows real progress.
Think back:
- What confused you a year ago?
- What do you now handle without stress?
Your past self is the most honest benchmark.
Create New Friction
If everything feels too comfortable, growth slows:
- Take on slightly unfamiliar problems.
- Get involved in system design, not just implementation.
- Review other people’s code and challenge assumptions.
Growth often requires stepping into mild discomfort again.
Closing Thought
Feeling stuck after a few years is normal—it’s part of the journey.
You’re not standing still; you’re just moving in ways that are harder to see.