When Life Gives You Lemons, Run an ROI & Risk Analysis

We love talking about linear growth in this industry. Internal promotions, steady climbs through technical roles, the neat career ladder story. I was lucky. I moved into technical leadership earlier than I’d expected myself, and for a while my career felt less like stairs and more like momentum I didn’t fully choose. But no amount of professional acceleration prepares you for the moment life hands you constraints you didn’t map out, and forces you to slam the brakes.

Starting point: a crossroads

It started with a crossroads. I was recovering from a health issue while working a high-pressure corporate job and hunting for a master’s scholarship at the same time. Most major postgraduate scholarships have an age cutoff, and mine was closing in. So I made the call to take a career break in mid-2025.

The plan was simple on paper: recover, and put everything into landing a Master’s in a field I actually wanted, cybersecurity, even though my background wasn’t technical enough on paper to make that an easy sell. Life doesn’t care about your plan, though. Right as things started to stabilize, a family emergency pulled in a lot of my attention for a stretch. My days stopped being about recovery, language classes, and scholarship essays alone. They became a mix of everything at once, trying to keep an academic dream alive on the side.

Somehow, I kept moving forward with it. By the first half of 2026, I’d made real progress in the scholarship process.

The realization: shifting ground demands a shifting strategy

I was at the midpoint of that process when it hit me: the tech world looked nothing like it did when I wrote my statement of purpose. AI, LLMs, agentic systems, the whole market moving under everyone’s feet. I stopped treating grad school as an emotional milestone and started running it through a cold ROI calculation, backed by an honest risk analysis.

The real wake-up call came from actually looking at the job market. What I found wasn’t pretty. Plenty of well-educated people are out of work, and I’ve personally seen Master’s graduates end up in jobs that have nothing to do with knowledge work or white-collar roles at all. The market’s saturated, at both the Bachelor’s and Master’s level. Unless you’re aiming for academia, most industries don’t reward advanced degrees the way they used to. In software engineering especially, a credential alone doesn’t carry the weight it once did. Companies want people who can solve today’s problem, not people with the right piece of paper.

So the question became: is spending years locked into a rigid academic structure really the best way to keep up with a field that changes weekly? The data I’d gathered was leaning no. A traditional academic path probably wasn’t going to give me the return I was looking for, or at least that was starting to look like the most likely outcome.

Overcoming the sunk cost fallacy

Walking away from something you’ve bled for is hard. That’s the sunk cost fallacy doing its job: keep going because you’ve already gone this far. I’d made it to interview rounds. Quitting felt, on the surface, like tossing away a prize I’d already half-won.

But staying the course out of stubbornness, in a field built on logic, despite data telling you otherwise, is just bad strategy. Some of the decision-making literature I came across generally backs this up: data beats pride. My career wasn’t going to be the exception.

Logic doesn’t kill a long-held dream on its own, though. For months I sat with the numbers, second-guessing myself, wondering if I was being smart or just cynical. Eventually, the conviction caught up to the math, and I was able to act on what the data had been telling me for a while.

So, in mid-2026, I pivoted. I stepped away from the scholarship track. Instead of waiting for a degree to define my next chapter, I decided to shift, gradually, putting my energy into deliberate upskilling, while also experimenting with adjacent fields where my transferable skills could actually be put to work. I kept building my portfolio in software engineering, the thing I already knew, and started exploring other fields where that same skill set could carry over.

What this taught me

1. Five-year plans are hypotheses, not commandments. Real career ownership means looking at new data and being willing to pivot without flinching.

2. Walking away isn’t automatically failure. Not if you replace the thing you dropped with something more strategic. Knowing when to cut your losses matters as much as knowing when to push through.

3. The sunk cost isn’t a total loss. The scholarship interviews, the language classes, the discipline of writing essays under pressure, none of that vanished when I changed direction. It’s still there, just pointed somewhere else now. Letting go of the destination doesn’t mean the road was wasted.

4. Timing is out of your hands. Plans made in calm water rarely survive a storm. Growth tends to show up exactly when you’re forced to adapt to constraints you didn’t choose.

5. Good decisions can take longer to feel right than they take to calculate. I had the numbers months before I had the conviction. Sitting with that gap wasn’t wasted time. It was just the slower, human part of the process catching up to the fast, logical part.

6. Credentials versus capability. An advanced degree still matters in academia, and in a handful of niche technical fields too. Across most common, commercial white-collar industries, though, a working portfolio and the ability to pick up new tools fast now counts for more than a diploma. I don’t love that this is true. But from what I’ve seen among people around me, it seems to be.

Closing thoughts

I don’t have every variable figured out. This wasn’t the plan, it was how I found a way to keep moving through a period that didn’t go the way I expected, and turning down that personal goal to align with where the world actually stands right now was just another calculated bet in a field where nobody has the full blueprint anyway. Adapting on the fly is basically the whole job now, and this is just my latest attempt at it.