Hello Reader,A few years ago, I was working with an engineer who had spent eight years building network automation tools. He was exceptional at it. His systems were elegant, his code was clean, and his team respected him. But when I asked him what he wanted to be doing in five years, he went quiet. "Honestly? Not this. But I've invested so much time. It would be wasteful to walk away now." He was protecting the past at the cost of the future. Six months later, he was still there. Not because the work excited him, but because leaving would mean admitting that the past version of himself had made choices that no longer fit. Why engineers drift instead of decidingMost engineers don't ruin their careers with one bad decision—they drift. They stay in roles, specializations, and career paths that aren't quite wrong, but aren't quite right either. Things work well enough. The compensation is solid. The work looks impressive on LinkedIn. And that's exactly what makes it dangerous—because nothing is broken enough to force a change. Research on career transitions shows that most people don't change direction because they feel clear. They change because something breaks: a reorganization, a health scare, a moment that removes the illusion of time. Until then, they tolerate and tell themselves they're being responsible, rational, and patient. The sunk cost trap engineers fall intoFrom a psychological perspective, this behavior makes sense. Once you've invested enough time, effort, and identity into something, walking away starts to feel like failure. Not logically, but emotionally. Behavioral economist Daniel Kahneman's research on sunk cost fallacy shows that humans are wired to protect past investments, even when those investments no longer serve them. In engineering contexts, this manifests as:
The result is a career that looks successful from the outside while feeling increasingly hollow from the inside. What waiting for a crisis costs youMany engineers think career change requires external validation. A reorganization that eliminates their role. A manager who explicitly tells them they're on the wrong path. A dramatic moment that makes the decision feel justified. The uncomfortable truth? Clarity was always available. It just didn't feel permissible without a crisis to point to. I've seen this pattern repeatedly: an engineer knows for months that their current specialization no longer excites them, but they wait. They wait for a layoff to make the decision for them. They wait for a reorg to create an opening. They wait for something external to justify what they already know internally. The cost isn't just time. It's momentum. Careers that only get attention during crises start from a defensive position—reacting to circumstances instead of designing direction. By the time the crisis forces the decision, you're choosing from limited options under pressure rather than building toward something deliberately. How to separate past investment from future directionCareer alignment only gets built when you stop asking "Is this broken?" and start asking "Does this make me come alive?" Not constantly or perfectly—but enough that you feel engaged instead of merely compliant. The work doesn't focus on whether your current path is defensible. It becomes visible when you ask what you would choose if you weren't defending old decisions. Engineers who succeed here stop treating career direction as something you commit to once. They frame it as something you design, decision by decision, year by year. Four questions that break the sunk cost patternInstead of waiting for permission from pain, anchor your decisions to patterns that make alignment easier: Replace "I've invested too much to leave" with "What would I choose if I were starting today with everything I know now?" Replace "This works well enough" with "Does this energize me enough that I want to get better at it, or am I just good at tolerating it?" Replace "I should finish what I started" with "Is staying here serving the person I'm becoming, or protecting the person I used to be?" Replace "Leaving would waste my experience" with "How much of my experience transfers to work that actually excites me?" When career decisions are tied to future alignment instead of past investment, they stop sounding like abandonment. They become strategic repositioning—and that's a language engineers understand. Sunk costs aren't going away. But engineers who learn how to separate past investment from future direction stop wasting decades on paths that no longer fit. Their careers build momentum instead of inertia. Their technical depth serves work they care about. And they burn out less. Career drift doesn't happen because engineers lack discipline. It happens because they're very good at finishing things that no longer deserve to be finished. You're not here to preserve the version of yourself that made past choices. You're here to design what comes next. That's all for this week. |
Join 1k+ other forward-thinking professionals who receive the weekly newsletter, where I provide actionable strategies, insights and tools to escape the grind and build influential, future-proof careers. Sign up to get a FREE copy of my 5-Stage playbook to multiply your impact and build a career that AI can't replace.
Hello Reader, Some years ago, I watched a senior engineer named David present the most technically flawless migration plan I had ever seen. He had spent six weeks mapping every dependency across four microservices, documenting rollback scenarios for each phase, and building a custom monitoring dashboard to track the cutover in real time. His architecture review deck was twenty slides of precision. When he finished presenting to the leadership team, the room went quiet. The kind where twelve...
Hello Reader, Three years ago, I watched a senior engineer named David lose a promotion he had earned six times over. He was the kind of developer every engineering organization depends on but rarely celebrates. His code reviews were surgical. His incident response times were the fastest on a team of fourteen. In the third quarter alone, he resolved more production incidents than any other engineer in the department, including two high severity outages that if left unaddressed for another...
Hello Reader, It's Kayode Three years ago, I watched a senior engineer named Priya present a migration plan that should have been a career-defining moment. She had benchmarks from three cloud providers. She had architecture diagrams showing the current state and the proposed state, layered with annotations. She had a detailed rollback procedure for every phase of the transition. The savings were real: $2.3 million annually, backed by six weeks of analysis. Any questions? she asked the room....