Stay Relevant as a Developer: Behavioural Science Tips

As a software developer, staying relevant is non-negotiable. The tools you learned three years ago might already be legacy. The framework that was cutting-edge is now considered “the old way.”

But here’s the thing: the change required isn’t just technical. It’s soft skills, management skills, knowing when to learn deeply versus when to skim.

Katy Milkman’s book How To Change: The Science of Getting from Where You Are to Where You Want to Be offers research-backed strategies for building lasting change. Let’s apply them to the developer context.

🚀 Obstacle 1: Not Getting Started

The science: Fresh starts create psychological momentum. New beginnings — a new job, a new year, even a Monday — give us permission to become someone different.

💡 For developers: This is why coding bootcamps work for career changers. It’s not that the curriculum is superior — it’s that the fresh start creates energy. Sometimes you need to create that fresh start deliberately: a new project, a new stack, even a new desk setup.

Sometimes what we need is a fresh start — even one as dramatic as moving countries.

🔭 Obstacle 2: Short-Term Thinking

The science: We underestimate how easily new behaviours fade when we stop paying attention.

For developers: You implemented that fancy new framework at work. Great. But if you stop there, the knowledge decays. Use personal projects to explore the depths. Treat learning as continuous, not a one-time event.

⚡ Obstacle 3: Impulsivity

The science: Long-term rewards are hard to appreciate when instant gratification is everywhere.

The fix: Temptation bundling.

📚 Too lazy to read technical books? Listen to audiobooks while stretching
☕ Want to stay fit and have your morning coffee? Run 5km before that first sip

Pair something you should do with something you want to do.

⏳ Obstacle 4: Procrastination

The science: Worthy goals that take time to achieve are easy to postpone forever.

The fix: Commitment devices.

Example: You want that AWS certification to level up your career options. It’s not easy, and it’s not cheap. What do you do?

Book the exam 6 weeks out. Pay upfront.
Now you have to study.
Your chance of recouping that investment just jumped to near-certain.

Pre-commitment turns vague intentions into unavoidable deadlines.

🧠 Obstacle 5: Forgetfulness

The science: Change is hard when you keep forgetting what you’re supposed to be doing.

The fix: “When ___ happens, do ___” (implementation intentions)

If you’re a Java dev, think of this as a switch statement for your life:

🔄 During daily standup → listen while doing a plank
💪 Before each meeting → 30 pushups
📖 After lunch → 10 minutes reviewing documentation

Linking new behaviours to existing triggers makes them automatic.

😴 Obstacle 6: Laziness

The science: Ambitious goals feel overwhelming. Overwhelming things get avoided.

The fix: The 90/10 rule. Instead of “exercise 3 hours daily,” try finding 10 minutes. Start small, identify what works, then expand.

Allow yourself flexibility when building habits. Rigid rules break; adaptable systems persist.

💪 Obstacle 7: Confidence

The science: Learning constantly can be disorienting. Imposter syndrome is real.

The fix: Teach what you learn.

The best way to consolidate understanding is to explain it to someone else. This is why the best bootcamp instructors are often recent graduates — they understand the journey because they just walked it.

Teaching builds your confidence and helps others.

🐑 Obstacle 8: Conformity

The science: Humans excel at mimicking. If your environment hasn’t changed, your behaviour won’t either.

The fix: Copy and paste from your future self.

Find people who’ve achieved what you want. Study their paths. Join communities where the behaviour you want is normal.

Your environment shapes you more than your willpower does.

🏁 The Bottom Line

Change isn’t easy. You might be asking yourself: Should I leave this job for something better? What skills should I prioritise?

There’s no formula. But Milkman’s research gives us tools:

✨ Create fresh starts
🎯 Bundle temptations
🔒 Set commitment devices
📝 Build implementation intentions
🌱 Start small and stay flexible
🎓 Teach to learn
🌍 Choose your environment deliberately

Fear and uncertainty are part of the process. The goal isn’t to eliminate them — it’s to work with them.

Once you accept that, you can actually start moving toward the developer you want to become.

More book reviews: