Why I Finally Stopped Optimizing Everything Except My Bank Account

I spent three years chasing the perfect tech stack. React or Vue? PostgreSQL or MongoDB? Should I learn Rust, Go, Kubernetes? I'd optimize deployment pipelines, refactor legacy code at midnight, and read every blog post about the latest JavaScript framework. But somehow, I never applied that same rigor to money.

Last year, a friend asked me a simple question: "You spent weeks optimizing a database query to save 200ms. How much time did you spend thinking about your finances this month?" I didn't have an answer. That's when I realized I was doing something absurd—treating optimization as a sacred practice in my career while treating personal finance like a system I could deploy without understanding its fundamentals.

This disconnect is everywhere in tech. We're good at making money. We're terrible at keeping it.

The Illusion of the Big Salary

Here's what I've learned working with developers across Islamabad's tech scene: the highest paid engineers aren't always the wealthiest. I know a senior developer pulling in more than most CTOs, yet he's perpetually broke. New car. New apartment in an overpriced area. Designer everything. Each bump in salary just raised his burn rate proportionally.

The real insight isn't revolutionary—it's almost boring. Wealth is built through the gap between what you earn and what you spend. It compounds over time. But that's exactly why most people ignore it. There's no glamor in a spreadsheet. There's no dopamine hit in not buying something.

What changed for me was reframing the problem. I stopped thinking about salary as my final metric and started thinking about freedom. What does your money actually buy? In tech, it should buy you optionality. The ability to say no to a bad project. To take sabbaticals. To work on something that matters instead of something that pays.

Compounding Works the Same Way as Your Skills

As engineers, we understand compounding intuitively—we just call it something else. When I learn a new framework today, that knowledge compounds into faster development tomorrow, which compounds into better projects, which compounds into reputation. Each layer builds on the previous one.

I realized I was actively using compounding in my career while actively ignoring it in my finances. A junior developer I mentor asked me why I was telling her to start investing at 23, before she'd "made real money." I said: "Because 23-year-old you needs to beat 30-year-old you in a race. And compound interest makes that possible."

The math is stupid simple. Start with 10,000 PKR. Invest it consistently. In 20 years, even with modest returns, you've got something meaningful. Miss those first five years? Now you're catching up forever.

Consistency Over Optimization

Here's where most developers (including me) get it wrong. We want to optimize the investment strategy. What's the perfect allocation? Should I use this tool or that one? We're asking the wrong question.

The real variable isn't the 2% difference between strategy A and strategy B. It's whether you show up for 20 years. Can you maintain consistency when the market drops 30%? Can you resist touching that fund when a friend tells you about their "guaranteed returns"?

I've watched people chase perfect optimization and abandon ship when things got boring. I've watched others with mediocre strategies succeed because they just... didn't stop.

My Take: The Framework Matters More Than the Numbers

I agree with the core thesis—engineers need financial literacy. But I'd push further. We need to stop thinking about money in isolation. This isn't separate from our career; it's the continuation of it.

One thing I'd challenge though: the book (and the original article) focuses heavily on savings and compounding. That works if you're already earning well. But the real edge for developers is understanding value creation. How do you build things people pay for? How do you go from earning 200k to making 200k? That's a different skill than budgeting.

For me, the bigger realization was recognizing that financial planning and technical planning should use the same frameworks. Version control your finances. Have a CI/CD pipeline for your spending. Monitor your metrics. Set alerts. Use the tools we already know.

What's Your Freedom Worth?

Before you read another framework tutorial or chase another certification, ask yourself: what are you optimizing for? More salary? A better title? Or actual freedom—the ability to spend time on things that matter?

That changed how I approach learning. I'm pickier now. Not every new technology is worth my time.

What would change in your career if you started thinking about time as your scarcest resource?

Source: This post was inspired by "Why Every Software Engineer Should Read "The Psychology of Money"" by Dev.to. Read the original article