Five years in and honestly, the thing I didn't expect to fight against is comfort.
You get to a point where things just... work. You know the patterns. You've seen the bugs. You can set up a project without thinking. That's great until you realize you haven't actually been challenged in months.
Here's what's been working for me.
Build something you don't understand yet
Not at work. On the side. Pick something that's slightly outside your zone and just start poking at it. I've been messing around with VoIP and SIP stuff lately, nowhere near my usual React Native and Node.js world. It's uncomfortable. That's kind of the whole point.
You don't have to finish it. Just stay curious.
Read more code than you write
Not tutorials. Actual source code of libraries you use every day. Open it up and read it like a book. You'll find things that surprise you, and occasionally things that make you go "wait, why did they do it like that?" Both are useful.
Explain things regularly
Write a post. Walk a junior through something. Do a quick internal talk. It doesn't matter. The moment you try to explain something clearly, you find out fast where your understanding actually has holes. Happens to me every time.
Ship the ugly version first
This one took me a while. Senior devs tend to want to get it right from the start. But sometimes the right move is to ship something rough, see how it actually gets used, then fix it. Real usage teaches you things no amount of upfront thinking will.
Switch contexts when you can
New domain, new stack, new team, whatever you can manage. Every time I've moved into a new space (fintech, crypto, AI products) I've hit problems I wasn't ready for. That friction is where most of my actual growth has happened.
Staying sharp isn't really about doing more. It's about not going numb. The best senior devs I know aren't the ones working the hardest, they're the ones who are still genuinely interested after years of doing this.
That's what I'm chasing anyway.
Top comments (0)