Many years ago, I was a mid-level developer at a consulting company. I remember staring up at the org chart and wondering how people became architects, then senior architects, then technical directors. It felt mysterious. Political. Reserved for the chosen few.

And yet, over roughly six years, I climbed that ladder:Developer → Architect → Senior Architect → Tech Director.

At the time, it felt brutal.

In hindsight, it was almost straightforward.

The uncomfortable truth? The path that worked for me may no longer be enough today.

Let me explain.

The Old Playbook

When I was a mid-level engineer, I did three things obsessively:

* I volunteered for very hard projects.

* I sought out strong mentors.

* I pushed myself into system design work.

That was it.

1. Volunteer for the Deathmarch

One of those projects was an enterprise service bus middleware component for a massive publishing company, let’s call it Big Corp.

It was a nightmare.

Months of weekend work. Endless integration problems. And on go-live night, an open-source bug nearly broke me. I remember standing in the parking lot after midnight, overwhelmed, exhausted, and crying in my car.

It was ugly.

But I shipped.

And when you survive something like that, two things happen:

* Your technical depth sharpens dramatically.

* Leadership notices.

Hard projects compress experience. They force you to grow up fast.

2. Find Mentors (Even If It Feels Awkward)

I actively sought mentorship from senior technical leaders.

At first, mentorship can feel transactional. Almost burdensome to the mentor. But over time, something shifts. If you show initiative and deliver results, many mentors start to care. They feel invested.

One of mine, let’s call him Heinz, was a seasoned tech director. He taught me small tactical things (like why knowing sed and awk gives you borderline superpowers) and big strategic things (like why system design is the real career unlock).

Mentors don’t just give advice.They give visibility.They give sponsorship.

When promotion cycles came around, some of the people advocating for me were former mentors.

That matters more than people admit.

3. Move From Coding to Designing

The biggest inflection point in my career wasn’t learning another framework.

It was system design.

System design is fundamentally different from implementing user stories. It’s about defining modules, boundaries, data flows, tradeoffs, scalability constraints, the blueprint before the building.

When you do system design:

* You sharpen architectural thinking.

* You gain cross-team visibility.

* You operate at a higher altitude.

By the time promotions came, I had:

* Credibility from delivering painful projects.

* Visibility from leading system designs.

* Advocacy from mentors invested in my growth.

That combination moved the needle. Repeatedly.

Why That Path Is Harder Now

Over the years, I’ve mentored many mid-level engineers.

And recently I’ve come to a sobering realization:

The journey I took is significantly easier than the one mid-level engineers face today.

Today’s environment looks like this:

* Saturated job markets.

* Wave after wave of layoffs.

* Leadership pressure to “do more with less.”

* AI amplifying productivity expectations.

* Constant fear of replacement.

The things that once propelled me upward: volunteering for hard work, gaining visibility, expanding scope are now table stakes just to survive.

That changes the game.

So what can a mid-career, mid-level engineer realistically do right now?

Not magical strategies. Not silver bullets.

Coping strategies.

Time-buying strategies.

Because even one or two extra years of employment can mean:

* More savings.

* More investments.

* Greater optionality.

* More leverage over your own life.

Strategy #1: Build a T-Shaped Skill Set

Specialization used to be a moat.

If you knew COBOL, banks would keep you forever.

That moat is shrinking.

AI tools can now generate competent code across obscure stacks. The defensibility of narrow expertise is eroding.

Instead, build a T-shaped profile:

* Deep expertise in one core stack (your vertical bar).

* Broad exposure to adjacent domains (your horizontal bar).

For example:

* Go full-stack instead of only front-end.

* Learn data engineering or QA.

* Understand product management.

* Gain exposure to UX and design thinking.

Small teams of versatile engineers are now building what once required multiple departments.

The disruptors are compact.

You want to be on that side of the equation.

Strategy #2: Use AI as a Force Multiplier (If You’re Mid-Level)

Here’s an interesting dynamic.

AI tools like Claude Code are not productivity-equalizers.

They disproportionately benefit experienced mid-level engineers.

Why?

* Junior engineers lack the depth to detect hallucinations, subtle bugs, security issues, or scalability flaws.

* Some senior leaders have let their hands-on skills atrophy.

Mid-level engineers who are still deeply technical, and still actively coding, are uniquely positioned to 10x their output.

This window may not last forever.

But right now? It’s leverage.

Use it.

Strategy #3: Master the Delegation Decision

AI is not a machine god.

It automates a large chunk of software work, but not all of it.

Your competitive advantage becomes knowing:

* When to fully delegate.

* When to collaborate iteratively.

* When to do it yourself.

Ask three questions:

* How long does it take me to do this manually?

* How long does it take AI?

* How likely is AI to get it right?

If AI can generate a well-documented module quickly and safely? Delegate.

If requirements are fuzzy and need iterative shaping? Collaborate.

If business context is subtle, political, or risky? Do it yourself.

Finding that boundary is a superpower.

Strategy #4: Develop Deep Domain Context

AI is strong at generalizable coding tasks.

It is weaker where domain context lives in messy, semi-analog reality:

* Tribal knowledge.

* Undocumented workflows.

* Historical business constraints.

* Political tradeoffs.

Mid-level engineers can carve out near-term defensibility by embedding themselves deeply in domain knowledge.

Become the person who understands not just the system but why it exists.

That context is not easily scraped and trained on.

Strategy #5: Learn to Tell the Story

This one hurts to admit.

In the AI era, raw information and logic are commoditizing.

For engineers, that’s a body blow.

But synthesis and storytelling remain leverage.

If you can:

* Frame tradeoffs clearly.

* Translate technical decisions into business narratives.

* Connect architecture to revenue impact.

* Turn scattered data into a coherent strategy…

You influence:

* Scope.

* Budget.

* Roadmaps.

* Headcount.

Storytelling moves resources.

Resources move careers.

The Reality

We are living through instability.

Small teams are replacing large ones.AI tools are raising expectations.Career ladders feel less predictable.

The old playbook still works, but it’s no longer sufficient on its own.

Today, mid-level engineers must:

* Be versatile.

* Be AI-literate.

* Be strategically aware.

* Be narratively strong.

It’s harder.

But not hopeless.

If you’re in the middle of your career and feeling squeezed from both sides by hungry juniors and cost-cutting leadership, you’re not imagining it.

The pressure is real.

The environment has changed.

But so have the tools at your disposal.

Use them wisely.

And buy yourself time.

Sometimes survival and compounding is the most underrated career strategy of all.

Hello world.

I’m an unemployed ex–Big Tech software engineer with 25+ years in the trenches of the software industry. I’ve ridden the dot-com bubble, offshoring waves, mobile revolutions, cloud migrations, and whatever we’re calling the post-pandemic tech reckoning.

And now? I’m watching the AI gold rush from the outside.

Depending on which headline you read this morning, artificial intelligence is either:

* An economically unsustainable hype machine

* A glorified autocomplete that can’t boost productivity

* Or the final exponential surge before Artificial General Intelligence automates every white-collar job in the next 12–18 months

So which is it?

Is AI just a “probabilistic parrot” repeating patterns from the internet? Or is something structurally different happening this time?

Let’s walk through what’s actually changed over the past five years in plain English.

Phase 1: The Giant Autocomplete

Early large language models like OpenAI’s GPT-3 were, at their core, probability machines.

You type:“Mary had a little…”

It predicts:“lamb.”

Not because it understands nursery rhymes. Not because it has memories. But because “lamb” statistically follows that phrase in its training data.

That training data? A massive scrape of publicly available internet text.

Impressive? Yes.Intelligent? Not really.

On its own, this was more a clever toy than economic earthquake.

Phase 2: Teaching the Parrot Manners

The next breakthrough was supervised fine-tuning.

Humans created tens of thousands of carefully written question-and-answer examples. The model was retrained on these, nudging it toward responses that felt helpful, structured, and safe.

This is how the first version of ChatGPT launched in 2022.

It was better. But still limited.

The bottleneck? Humans are expensive. Slow. Finite.

So AI researchers did what engineers always do when constrained by humans: they automated the humans.

Phase 3: Reinforcement Learning at Scale

Instead of having humans generate both questions and answers, the model could now generate answers while human experts simply judged them as good or bad.

Good answer? Increase the probability of similar responses.Bad answer? Penalize it.

This is reinforcement learning.

But even that eventually hits scale limits.

So researchers trained AI models to become evaluators learning from human feedback and then taking over the judging process. Now AI models could train future AI models.

And once humans are mostly out of the loop?

You can scale to absurd levels.

Millions. Billions. Trillions of generated tasks.Evaluated in weeks using massive data centers.

Still probability math.But at industrial scale.

Phase 4: Chain-of-Thought — The “Reasoning” Illusion

Then came reasoning models.

Instead of predicting a single answer to:

“If you have 8 pizza slices and eat 3, how many remain?”

The model breaks the problem into steps.

8 slices.Minus 3 eaten.Equals 5 left.

This “chain-of-thought” decomposition dramatically improves accuracy. Not because the AI understands pizza but because smaller probability jumps are easier than giant ones.

It’s still math.

Just math with better scaffolding.

Phase 5: Tools — From Talking to Doing

This is where things get serious.

Language models began calling tools.

Need the current temperature? Call a weather API.Need to write to a file? Call a document function.Need to push code to a repository? Trigger a Git action.

Models like Gemini, Claude, and modern ChatGPT versions now interact with external systems.

This transforms AI from:

Answer machine → Action machine.

And action is where jobs live.

Phase 6: Re-Act Architecture Thought, Act, Observe

Complex work isn’t one step. It’s dozens. Hundreds.

The “Reason + Act” (ReAct) pattern works like this:

* Think through a plan.

* Execute one step using a tool.

* Observe the result.

* Update context.

* Repeat until done.

This loop enables multi-step cognitive labor.

But there’s a catch: memory.

AI models have context windows, short-term memory buffers. Overload them, and they hallucinate or forget key constraints.

Enter the next hack.

Phase 7: Agentic Frameworks — The Harness Around the Brain

Agent systems wrap AI models in orchestration layers.

Think of it as:

* A planner agent

* Worker sub-agents

* A QA agent

* External databases storing long-term context

Each agent only sees what it needs.

One plans the website.Another writes code.Another tests it.

Some systems even simulate 24/7 “proactive” assistants using timed loops that periodically re-prompt the model — giving the illusion of autonomy.

Is it consciousness? No.

It’s math wrapped in for-loops.

But here’s the uncomfortable part:

It works.

Are We Near AGI?

No.

There is no understanding. No awareness. No inner life. No self.

We are not at the singularity.

But that doesn’t mean we’re safe.

The Productivity Question

Recent industry studies suggest frontier models like ChatGPT 5.2 and Claude 4.6 can sustain deep, complex cognitive work for over an hour with success rates exceeding 80%.

For context:

The average white-collar worker can maintain true deep focus for 60–90 minutes at a time.Across an entire day? Maybe 2–3 hours of real high-quality output.

If AI focus time doubles every six months, as some data suggests, we may soon see models capable of four-hour sustained cognitive blocks.

And they don’t need sleep.Or weekends.Or health insurance.

So… Will AI Replace White-Collar Jobs?

Here’s the honest answer:

Any job that consists primarily of interacting with a computer interface is at risk.

* Software engineering

* Accounting

* Legal research

* Financial analysis

* Marketing copy

* Project management

* Operations

AI models are being fine-tuned for each of these domains right now.

We are not watching a toy evolve.

We are watching a new kind of digital labor force scale geometrically.

The Paradox

AI is still “just” probability.

It doesn’t understand.

It doesn’t reason in the human sense.

And yet through scale, reinforcement learning, tool use, reasoning scaffolds, and Agentic orchestration, it can now perform long-duration cognitive work that looks remarkably similar to what many professionals do daily.

That’s the tension of this moment.

It’s not conscious.

But it’s competent.

Something Big Is Happening

As someone who’s spent 25 years in software, and who is currently unemployed, I don’t have the luxury of dismissing this as hype.

I’ve seen enough technology waves to recognize when the ground is actually shifting.

This one feels different.

Not because machines woke up.But because the scaffolding around them did.

If you’re watching this space with a mix of curiosity and existential dread, you’re not alone.

We’re all trying to figure out what comes next.

And whether we’ll be coding it…

Or competing with it.

Hello world.

After more than 25 years in the software industry, and an unexpected exit from Big Tech, I found myself in an unfamiliar situation: time. Lots of it. The kind of time engineers rarely have, the kind that invites curiosity, experimentation, and occasionally, questionable ideas.

This is the story of one such idea.

A Simple (and Slightly Dangerous) Thought Experiment

What if you could build a system that:

* Discovered profitable market niches automatically

* Generated digital wall art tailored to those niches

* Published the results directly to online marketplaces

* And quietly earned income in the background

In other words: could software design, create, and sell creative products without human involvement?

It sounded like the perfect retirement-side experiment—equal parts engineering challenge and philosophical mischief.

Designing With an AI Co-Architect

To move from idea to implementation, I worked alongside OpenAI’s ChatGPT-5, using it less like a tool and more like a collaborator.

The planning phase felt like an architectural dialogue:

* The AI proposed system designs

* I interrogated assumptions

* We refined constraints together

* Repeat… until the structure made sense

It didn’t feel like architecting. It felt like conducting an orchestra, one where every musician already knew every instrument ever invented.

At times, it was like whispering into the ear of a sleeping leviathan.

The Architecture: Automation All the Way Down

The final system ran as an automated workflow in n8n, orchestrating a sequence of Node.js tasks:

* Identify promising keywords

* Analyze successful products

* Generate new creative concepts

* Produce artwork using generative models

* Build marketing assets

* Syndicate listings through Printify

For the initial MVP, distribution targeted Etsy and Amazon.

From there, I generated a full Product Requirements Document using AI and handed implementation to a coding agent powered by Anthropic’s Claude Haiku model.

Then I did something that would have been unthinkable earlier in my career.

I went for coffee.

When I came back, most of the system was written.

The Surreal New Development Loop

My role shifted dramatically:

* Review AI-generated code

* Run integration tests

* Fix edge cases

* Deploy

No sprint planning.No backlog grooming.No weeks of incremental implementation.

By the end of Day One, the pipeline was live in my home cloud.

Naturally, I assumed I had built a fully automated passive-income machine.

Naturally, I was wrong.

Reality: The Humans Are Still Needed

The very first production run exposed the messy parts of the real world.

1. AI Image Imperfections

Roughly 1 in 15 generated images contained subtle visual defects, things only a human eye could catch. There is still no reliable automated test for “this looks weird.”

2. Intellectual Property Landmines

Some outputs drifted dangerously close to recognizable styles or copyrighted material. Text can be screened. Visual similarity? Much harder.

3. Marketplace Integration Chaos

The Print-on-Demand pipeline was far from seamless:

* Listings failed unpredictably

* Variants split into separate products

* Metadata required manual correction

Instead of passive income, I found myself babysitting automation.

After a full day of supervision, I had published about 100 products.

Automation, it turns out, still needs adult supervision.

The Moment of Existential Debugging

By Day Two, I stepped back and asked a different kind of question:

Was this even a good idea?

If perfectly automated, the system could flood marketplaces with thousands of derivative works. But that doesn’t create new value, it just redistributes attention within an existing market.

In economic terms, it wasn’t innovation.It was acceleration without direction.

And that led to one of the great luxuries of early retirement:

If you’re working on something pointless, you can just stop.

So I walked away.

The Twist: It Made Money Anyway

A month later, curiosity got the better of me. I checked the accounts.

Those ~200 listings I had published before quitting?

They had quietly generated revenue:

* About $600 on Etsy

* Around $70 on Amazon

After costs, fees, and fulfillment, the profit was roughly $200.

Not life-changing.But not zero either.

An abandoned experiment had paid for a nice dinner and perhaps a bottle of soju.

What This Experiment Really Taught Me

This project wasn’t about wall art. It was about understanding how AI is reshaping the act of building.

We are entering a phase where:

* Designing systems may matter more than coding them

* Iteration happens conversationally, not procedurally

* Engineers supervise intelligence rather than implement logic

* The bottleneck is no longer syntax, it’s judgment

AI can build astonishing things quickly.

But deciding what is worth building remains stubbornly human.

What’s Next?

There are far more interesting problems to explore than teaching machines to sell wall décor. So I’ve moved on to projects that feel less like automation experiments and more like genuine discovery.

Still, this strange little system remains one of the most educational things I’ve built.

Not because it succeeded.

But because it showed me where the real questions now live.

If you enjoy thoughtful experiments at the intersection of software, AI, and life after Big Tech, feel free to follow along. There’s plenty more tinkering ahead.

Hello world.

After more than twenty-five years in the software industry, I now find myself in an unfamiliar position: an ex–Big Tech engineer with time to think. And when you suddenly have time, real, unstructured time, you start asking questions that never quite fit into sprint planning or quarterly OKRs. Questions about where all of this is going. About what kind of civilization we may be constructing, almost accidentally, through code, platforms, and incentives.

One possible answer is something historians would recognize immediately, even if we insist on calling it innovation: techno-feudalism.

A System That Refuses to Stay in the Past

To understand the idea, it helps to revisit classical feudalism—not as a medieval curiosity, but as one of the most stable socioeconomic systems humanity has ever produced. For centuries across Eurasia, feudal societies organized themselves around a simple structure:

* A vast majority, over 90%, were serfs, bound to land they did not own.

* A narrow middle layer, perhaps 5–10%, were specialists, tradespeople, clergy, or small landholders.

* At the very top sat the lords, fewer than 1%, who owned nearly everything.

Serfs possessed little beyond their labor. Land, tools, housing, and even access to basic resources were controlled by their lords and leased back in exchange for rent, often paid through work rather than money. Social mobility was rare, ownership rarer still.

The system was extractive, unequal, and often brutal. Yet it was astonishingly resilient. Feudalism endured not because it was just, but because it was economically self-reinforcing.

How Feudal Systems Sustained Themselves

When productivity plateaued or populations grew too large, lords adapted through three recurring strategies:

* Expansion – acquiring new land or resources to maintain surplus value.

* Monetization – leasing labor elsewhere, converting obligation into currency.

* Control of Dependency – ensuring those at the bottom remained structurally tied to the system.

Feudalism did not collapse on its own. It weakened only when demographic shocks, wars, and new frontiers shifted bargaining power back toward labor. Scarcity of workers forced change.

In other words, feudalism ended when people once again became economically valuable.

The Digital Echo of an Old Order

Now consider the present.

Today, ownership of infrastructure, platforms, and capital is increasingly concentrated. Many people do not own their homes outright, their transportation, or even the software tools required to function professionally. Instead, they subscribe. Monthly payments replace property. Access replaces ownership.

Housing is rented. Software is licensed. Entertainment is streamed. Mobility is leased. Even productivity increasingly depends on platforms we do not control.

This is not medieval agriculture. But structurally, it rhymes.

A small group builds and owns the digital “land.” A technical middle class maintains it. The majority participates through continuous payment for access.

The Accelerant: Automation of Cognitive Labor

Artificial intelligence introduces a new dynamic. Unlike past mechanization, which primarily displaced physical labor, modern systems can perform economically useful cognitive tasks, analysis, generation, coordination at dramatically lower cost.

If large segments of human work lose scarcity, the historical mechanism that dismantled feudal systems, valuable labor, may not reappear this time.

Without surplus income, fewer people accumulate capital. Without capital, ownership concentrates further. Dependency deepens, even if living standards remain materially adequate.

A society can become comfortable and constrained at the same time.

A Narrow Path Forward

This trajectory is not inevitable. History never repeats exactly. But it often presents familiar shapes under new names.

We may be approaching a fork between two futures:

* One leads toward a highly centralized, subscription-mediated existence: efficient, stable, and quietly stratified.

* The other toward a world where technological abundance broadens ownership rather than concentrates it.

The difference will not be determined by technology alone, but by how societies choose to distribute its gains.

Somewhere between dystopia and utopia lies a narrow path. Whether we recognize it and choose to walk it remains an open question.

For now, with time to think, it is a question worth asking.

Hello, World.

I’m an unemployed, ex–Big Tech software engineer with 25 years in the industry.

That sentence would have terrified me a decade ago. Today, it feels strangely calm.

We’re living through another brutal cycle of tech layoffs. Thousands of engineers: smart, capable people are refreshing LinkedIn feeds and grinding through interviews that feel increasingly like Squid Game with better lighting. Many are hurting. Some are in real financial distress.

By a combination of discipline, luck, and a few painful lessons, I’m not.

I’m financially independent, though not in the glamorous influencer sense. It’s more like involuntary early retirement. I’m not drawing a paycheck, but our living expenses are covered by returns from a pool of investments built slowly over time. It is an enormous privilege, and I don’t take it lightly.

What follows is not advice. I’m not a financial advisor. I’m simply a middle-aged engineer showing his work, the wins, the mistakes, the weird detours and how they compounded into stability.

Index Funds: The Boring Backbone

In 2008, during the wreckage of the financial crisis, I fell down a personal finance rabbit hole. Your Money or Your Life shifted my thinking. John Bogle’s The Little Book of Common Sense Investing sealed it.

The idea was simple: buy low-cost index funds that mirror the broader market, like the S&P 500, and let time do the heavy lifting. Most active managers fail to beat the market long term. If professionals with teams of analysts struggle, what chance did I have after a day of debugging Java?

So in early 2009, while markets were still bruised, I began investing heavily in S&P 500 index funds with a smaller allocation to total market bond funds, roughly 90/10.

Funding came from:

* 401(k) contributions (eventually raised to 8%)

* Employer matching (free money, always take it)

* Post-tax brokerage investments, which ramped up after we paid off student loans

I also funneled nearly every cash bonus into index funds.

Starting in 2009 was luck. The S&P 500 was near historic lows. Over 17 years, those funds averaged roughly 13% annually. Exponential compounding quietly made index funds our largest asset class. Today, the dividends from our taxable accounts form a meaningful portion of our income.

Boring worked.

Real Estate: Tangible Wealth

My father never trusted fiat currency. He believed real wealth is something you can touch.

So we bought it.

We own our primary residence and two rental properties, all mortgage free. We purchased during the softer post-crisis 2010s and paid them off through aggressive saving.

Some argue a primary home isn’t an investment. I see it as capital that appreciates and reduces our housing cost dramatically compared to renting. The rentals, modest homes within commuting distance of major cities, produce consistent income.

Property values have grown around 7% annually. Rental yields run 7–8% per year for us. Combined, real estate is our second-largest asset class and a powerful stabilizer.

The Side Hustle That Should Have Been Sold

In 2010, I built Android apps to pay off debt. It was the Wild West. Multiple app stores. Low competition. In 2011, I cleared over $100,000.

Then the gold rush ended.

Competition intensified. Earnings halved in 2012. A buyer offered $53,000 for the entire business. I declined, insulted.

I should have taken it.

By 2013, new apps earned less and less. Eventually I stopped building. The old apps trickled income for a decade until Google deprecated the SDK and delisted them in 2023.

Over ten years, the passive income didn’t even reach half the buyout offer.

Lesson: Know when the peak is behind you.

HYSA: Sleep Insurance

A high-yield savings account isn’t exciting. It’s insurance.

We built it from three months of expenses to one year as layoffs at work intensified. After my lay off, the severance added another year. At 3.75%, FDIC-insured, it’s less about growth and more about peace.

Peace compounds too.

Big Tech Stock: Concentration Risk

Joining Big Tech 7 years ago brought RSUs and an ESPP program with a 15% discount, effectively instant upside.

When shares vested in 2020, pandemic growth sent the stock soaring. I held. From 2020–2024, it averaged roughly 22% annual growth for me.

But concentrated positions make me nervous. I’ve been gradually converting shares into diversified index funds to manage capital gains taxes.

Concentration builds wealth. Diversification keeps it.

Precious Metals: Hedge or Warning Sign?

A doomer friend convinced me in 2009 to buy silver. I did, modestly, consistently, every Christmas.

Silver averaged roughly 12% annual growth over that period.

Precious metals produce no cash flow. They simply sit there, shiny and indifferent. Whether that performance represents savvy hedging or currency erosion is an uncomfortable question.

FOMO Stocks: Tuition Paid

In 2014, I invested $20,000 into hype-driven “visionary” tech stocks.

Two years later: $7,000 gone. Roughly –17% annually.

That was my tuition for ignoring fundamentals.

Soviet Ammo: The Accidental Asset

As a teenager, I bought surplus Cold War ammunition for pennies per round.

It sat in a basement for decades.

Two years ago, I sold one can for $700.

Roughly 10% annualized growth. The market is strange.

Crypto: The Best Return I Don’t Understand

In 2017, skeptical but curious, I mined a small amount of Monero on an old laptop. It earned $17 and destroyed a CPU fan.

I converted it to Bitcoin and forgot about it.

Today, it’s worth around $200, about 27% annualized growth.

It’s my best-performing asset.

I still don’t understand it.

The Big Picture

We made mistakes. Missed peaks. Held too long. Sold too soon. Chased hype. Ignored offers. Got lucky.

But over 17 years, consistent investing in productive assets, especially low-cost index funds and real estate, did most of the heavy lifting.

Financial independence wasn’t achieved through genius. It was built through:

* High savings rate

* Boring diversification

* Employer benefits

* Controlled lifestyle inflation

* And a lot of time

In uncertain times, stability is a gift.

If you’re navigating layoffs, know this: markets move in cycles. Careers do too. The key isn’t predicting the future, it’s surviving long enough for compounding to matter.

If you’re curious to follow this ongoing experiment in middle-aged reinvention, engineering, investing, existential reflection, I write monthly and share updates.

Thanks for reading.

Until next time.

Hello world.

I’m an unemployed, ex–Big Tech engineer with twenty-five years in the software and technology industry. That sentence alone would have felt impossible not long ago. And yet here we are, living through another wave of mass layoffs across American tech an era where résumés pile up, inboxes stay silent, and explanations are reduced to slogans.

One of the most common refrains I hear is simple: it’s offshoring.

Now that I have time, an abundance of it, I’ve been sitting with that claim, turning it over carefully instead of reacting to it emotionally. What follows isn’t a hot take. It’s a reflection shaped by decades inside the system.

Offshoring Comes in Waves

Offshoring in tech doesn’t happen all at once. It arrives in waves, each with a peak of enthusiasm and a valley of regret.

I entered my career during one such peak in the early 2000s, when companies aggressively shifted software development to lower-cost countries. In my experience, that almost always meant India. The logic was straightforward: software was expensive to build in the U.S., talent was plentiful elsewhere, and code was code. Or so we told ourselves.

As a consultant in the years that followed, I found myself working inside the aftermath of that decision. The codebases left behind were often catastrophic, vast jungles of copy-and-paste spaghetti code, barely documented, impossible to extend, and riddled with bugs. Many applications limped along, more fragile than functional.

Worse, when issues arose, it often felt as though the offshore teams supporting the systems didn’t truly understand the code they were maintaining or perhaps had never been given the space or incentive to care deeply about it.

By the mid-to-late 2000s, the pendulum swung back. Companies slowed or halted offshoring efforts and brought work onshore again, quietly acknowledging that cheap code can become very expensive over time.

Why Was the Code So Bad?

This question haunted me early in my career. Mathematics doesn’t change by country. Engineers don’t become less intelligent when they cross borders. In theory, software quality should be roughly equivalent everywhere.

Over time, I realized the issue wasn’t intelligence. It was friction.

Time Zones

Teams separated by half a world rarely overlap meaningfully. Collaboration collapses into tickets and emails. Context gets lost. Nuance disappears. Projects devolve into a “throw it over the fence” workflow with each side doing its piece in isolation, hoping the other can make sense of it later.

Language

Even when offshore engineers speak excellent English, subtlety often doesn’t survive translation. Requirements lose precision. Assumptions go unchallenged. And sometimes, asking the right question feels harder than simply saying yes.

Culture

In more hierarchical cultures, junior engineers may be discouraged, explicitly or implicitly, from speaking up. Problems get noticed but not surfaced. Uncertainty is masked as confidence. Work proceeds anyway, and the consequences appear downstream, where they are far more expensive.

None of this reflects a lack of talent. It reflects systems that punish curiosity and reward silence.

The Pendulum Swings Again

By the mid-2010s, offshoring returned, this time with more sophistication.

In 2015, I worked on a large enterprise re-platforming project for an automotive client. There, I met an offshore architect, let’s call him Abby, based in Gurugram, outside Delhi.

I was wary at first. Experience had trained me to be. But Abby quickly dismantled my assumptions.

He was brilliant. Deeply knowledgeable. Tireless. He understood the platform better than I did, despite technically reporting to me. To maximize overlap with U.S. teams, he worked until 10 or 11 p.m. his time, every weekday. Eventually, U.S. management began to expect this level of sacrifice from everyone offshore.

Abby was paid roughly one-sixth of my salary.

And yet, his cost of living was nowhere near as low as I had imagined. Cars, utilities, food, nearly U.S. prices. Housing near the office was so unaffordable that his family lived hours away. During the week, he shared a tiny apartment with coworkers. He saw his wife and child only on weekends.

He worked weekends too.

He told me about suffocating smog, brutal heat waves, floods, wild dogs, and constant environmental stress. I didn’t fully believe him, until years later, when I visited the same area myself and saw it firsthand.

Once, during a dengue fever outbreak, I watched fear consume him as he worried about his child’s safety.

And yet, he considered himself lucky.

Unequal Terms

Abby and I were men of equal worth. Of comparable skill. Of shared pride in our craft.

But we competed on profoundly unequal terms.

Over my career, I’ve worked with offshore engineers across India, Latin America, China, and Eastern Europe. Many are my friends. All are trying to provide for their families, no differently than American engineers.

In the last decade, many of the old barriers have fallen. Collaboration tools improved. Companies built parallel offices abroad. Offshore engineering quality rose dramatically. Today, many offshore engineers are true peers to their U.S. counterparts.

Which brings us to the uncomfortable truth.

The Real Incentive

Offshoring was never about quality.

It was and remains about cost.

Offshore engineers are still significantly cheaper than U.S. engineers. Unless something drastic changes, offshoring will continue and likely accelerate.

I’ve thought hard about what could stop it.

Regulation can protect certain sectors, but it raises costs and slows innovation. Poaching elite offshore talent strengthens companies but worsens competition for domestic workers. Tariffs invite retaliation and risk splintering global tech ecosystems. Waiting for work to return via automation may succeed but as manufacturing taught us, automation brings work back without bringing jobs.

Each solution carries a heavy price.

Who Wins?

I don’t see a magic button. I don’t see a clean fix waiting just beyond the horizon.

What I see are capable engineers, onshore and offshore, competing desperately for scraps.

In a more just world, they wouldn’t be rivals. They would be brothers, building together instead of being measured against one another.

The true winners are easy to identify.

Capital wins.

If you own it, the line goes up. Stock prices rise. Human cost fades into abstraction. As long as the graph climbs, everything is considered fine.

Maybe that’s all that matters now.

Thanks for reading. If you’re morbidly curious enough to walk this path with me, I write and talk about these topics regularly. And if you choose to support the work, thank you. Truly.

We’ll chat later.

Hello world.

I’m an unemployed, ex–Big Tech software engineer with 25 years in the technology industry. And like many of you, over the past week I’ve been watching yet another wave of mass layoffs sweep across tech, tens of thousands of engineers, designers, and product leaders suddenly finding themselves on the outside.

Every layoff cycle brings back a memory I can’t quite shake: my first.

My First Layoff, 2008

In 2008, during the Great Recession, I was a mid-level developer at a digital consulting agency. I’d been there just under two years, still learning, still finding my footing. I had a mentor, let’s call her Dana, an exceptional software architect who patiently taught me concepts I still carry today. She explained the differences between dynamically typed languages like PHP and the strongly typed Java systems I was used to, never making me feel small for not knowing.

Then one afternoon, building security appeared on the floor.

An emergency town hall invite hit our calendars. We gathered in the atrium, where our CEO, Rob, stood in front of us looking exhausted. He explained that unexpected economic conditions had caused the loss of major clients. Hard cuts had to be made for the company to survive.

What struck me most wasn’t the announcement, it was his demeanor. There was shame in his face. Sadness in his eyes. He took full responsibility for the layoffs, repeatedly emphasizing that none of the affected employees were at fault. It felt almost ancient, like watching a leader fall on his sword.

When the town hall ended and we returned to our desks, nearly half the floor was empty. Dana’s cube was stripped bare.

I felt fear, anxiety, self-doubt, and an overwhelming sense of survivor’s guilt.

At a nearby café, I found Dana. She told me she’d been laid off. She said mentoring me had been a pleasure. Her voice broke. She looked older than I’d ever seen her. At the time, she was younger than I am now, but loss has a way of aging you instantly.

That was my introduction to mass layoffs.

Three Eras of Tech Layoffs

Over 25 years, I’ve survived countless layoffs across three distinct eras.

The Great Recession Era was marked by reluctant leadership. Layoffs were painful, shameful, and avoided until there was no other option.

The M&A Era of the late 2010s brought quiet, discreet layoffs: fast, clinical, and rarely discussed.

The Post-COVID Big Tech Era, beginning around 2023, is something else entirely. Layoffs are framed as efficiency. As optimization. As something to be proud of. Strong engineers are cut not because they failed, but because markets demand higher valuations.

In my view, this era is the most brutal and unpredictable of all.

When my own Big Tech layoff finally came, I’d lost count of how many rounds I’d survived.

How I Stayed Employed for 25 Years

I can’t offer guarantees, but I can share what helped me last as long as I did.

Build a reputation for dependability.Be known as someone who gets things done well. That requires initiative, optimism, and solution-oriented thinking.

Make your value visible.Speak up strategically. Share accomplishments. Ensure your manager—and their manager—knows what you contribute.

Continuously learn in-demand skills.From bare metal servers to cloud platforms to SaaS, I was always learning what the market needed next. In-demand skills act like a parachute when you fall.

Work on revenue-critical projects.Projects that directly make money are the least likely to be cut.

Network relentlessly.Inside your team. Across departments. Outside your company. Your network is a safety net.

Be versatile.Take on varied roles. Learn flexibility. Remember: the highly specialized T-Rex didn’t survive, but the adaptable mammal did.

Final Thoughts

We’re living in an age of seemingly unending layoffs in tech. These strategies are coping mechanisms, not guarantees. But applied consistently, they can move the needle.

If you’re navigating this uncertainty, you’re not alone. I’m sharing this journey openly, part reflection, part therapy, part survival guide.

If you’d like to follow along, join the newsletter, or simply grab a coffee with me along the way.

Until next time.

Lamb Saag, Layoffs, and the Bug That Broke Me

Hello, world.

I’m an unemployed ex–Big Tech software engineer with 25 years of experience, which in today’s economy apparently qualifies me for involuntary early retirement. One unexpected perk of this phase of life is that I now do a lot more cooking for my family. Today’s menu: Indian lamb saag. Slow, deliberate, and unforgiving if you miss a step, much like enterprise software.

As the lamb simmers, let me tell you a story from a darker, stranger time.

2009: The Corporate Hunger Games

The year was 2009. Layoffs were everywhere. Entire floors disappeared overnight. Companies weren’t trimming fat; they were amputating limbs.

I worked at a digital consulting agency that had already survived several rounds of bloodletting. By all logic, I should have been gone. Yet somehow, like a cockroach surviving a nuclear blast, I remained employed.

Most of our major clients had vanished. One of the few whales still alive was a massive publishing conglomerate. Let’s call them Big Corp.

Big Corp had just experienced a revelation that felt revolutionary at the time: What if people bought our newspapers and magazines… on the internet?

Unfortunately, they had no e-commerce platform, almost no technical capability, and about 90% of their internal IT staff had already been laid off. In their place stood a shimmering mosaic of offshore and onshore H-1B contractors from a massive IT services firm. We’ll call them Outsourced Consultancy Services, or OCS.

Naturally, my company won the pitch to build Big Corp’s e-commerce platform. And just like that, we dove headfirst into a corporate dumpster fire armed only with PowerPoint decks and unearned confidence.

An Org Chart Designed by a Madman

The project team was… unusual. Nearly half the people involved were VPs, directors, account executives, or some flavor of Extremely Important Person. There were almost more chiefs than Indians, which statistically should not be possible.

Leadership had clustered around this project like penguins in a blizzard, hoping proximity to billable hours might keep them alive.

I joined as a senior developer, and for the first time in my career, I became the tech lead of my own squad. It included Eddie, a brilliant engineer from New Jersey; Sam, an Australian project manager; Ravi, an OCS build master stuck in green card purgatory; and several junior developers.

On paper, I reported to Bharath, an enterprise architect from OCS who had never written a line of code. Bharath reported to Heinz, an East German tech director from my company, and Mega, an OCS director. They reported to Fred, the client-side chief architect, and finally to Mr. Burns, a senior VP who looked exactly like a South Asian version of the Simpsons character. Same stare. Same energy. Same ability to drop a room’s temperature by ten degrees.

If this sounds confusing, don’t worry. It was worse in real life.

Building the Beast

We were tasked with building a web-based e-commerce system that allowed customers to order custom bundles of newspapers and magazines. Today, this would be a two-day Shopify project. Back then, it took five months, tens of millions of dollars, and what felt like several ritual sacrifices.

Orders flowed through an enterprise service bus, were chopped into pieces, and fed into a horrifying backend fulfillment ecosystem composed of overlapping legacy systems, orphaned applications, and entire platforms built around employees who had been laid off years earlier.

These systems were maintained by offshore sysadmins who treated them like ancient temples: don’t touch, don’t ask questions, and pray.

There was exactly one client-side IT veteran who understood how it all worked. His name was Davey. He was gray-haired, exhausted, and spiritually done.

My team owned the middleware layer. “Simple,” they said.

PowerPoint Architects and Sausage Making

It quickly became clear that Bharath’s tools were PowerPoint, Word, and criticism. I did the actual design. I wrote the specs. I drew the diagrams. Bharath reviewed them and offered feedback like:

* “The font lacks authority.”

* “This box should feel more visionary.”

* “The verbiage needs architectural gravitas.”

Then he presented my work to leadership.

I smiled, nodded, and stroked his ego, because for the first time in my career, I had full ownership of an application. No micromanagement. No interference. Pure sausage-making freedom. Worth every ounce of frustration.

We worked late. We bonded. Eddie, despite a stutter that caused management to underestimate him, was a phenomenal engineer. Ravi worked endlessly, supporting his family while trapped in immigration limbo. Sam dreamed of retiring as a landlord back in Australia.

We ate together constantly, mostly Indian food. It’s strange how easy it is to form deep friendships when you’re young and suffering together.

The Open Source Mistake

At some point, a client executive who had never touched middleware decided that open source was better. Requirements be damned.

They chose an open source ESB product. Let’s call it Crazy Boss.

Consultants from the company behind Crazy Boss, Silly Hat, arrived. They gave a dazzling demo, proclaimed that open source meant fewer bugs, charged an ungodly amount of money, and vanished.

Here’s the lesson I learned too late:Open source does not mean bug-free. Sometimes it means you get to discover the bugs personally.

The Bug That Shouldn’t Exist

As go-live approached, late nights became routine. Then weekends. Then time stopped mattering altogether.

During system integration testing, an order entered the system and vanished. Not failed. Not errored. Gone.

I checked everything. Logs. Queues. Dead letter Queues. Every line of middleware code. The bug should not have been possible.

We couldn’t reproduce it.

Leadership shrugged. “Probably a fluke. Let’s go live.”

I did not shrug.

I spiraled.

I rebuilt environments. Simulated load. Obsessed. The stress followed me everywhere. When my girlfriend, now my wife, visited me before go-live, I was so anxious I couldn’t even be intimate.

Nothing kills romance like a missing async message.

Go Live Night

Orders flooded in. Systems broke. We fixed them. By 3 a.m., things stabilized.

Then the calls came.

Missing receipt emails. Missing orders.

The bug was real. My middleware was eating them.

Mr. Burns stared at me and said, “Someone really effed this up.”

Something inside me snapped.

I walked out to the parking lot and cried. Full breakdown. Full impostor syndrome. My career was over. I was a fraud.

Then Sam and Heinz followed me out.

“Be kinder to yourself,” Sam said.Heinz added, with peak East German nihilism: “It never gets better. It only gets worse. Then we die. So why worry?”

We went back inside.

The Fix

Davey saved the day.

He noticed the bug only happened after Crazy Boss ran for days under load. The solution?

A cron job that restarted the instances in a round-robin fashion.

No downtime. Just reboot and pray.

It worked. The launch was declared a success.

Months later, we learned the truth: a memory leak in Crazy Boss that only occurred under high concurrency on Citrix VMs.

Of course.

Aftermath and Curry Nightmares

That morning, I found Ravi sitting quietly. He told me his daughter’s daycare was teaching kids to throw away food, a grave sin in his culture. During go-live night, he decided to quit OCS and return to India.

“God will find a place for me,” he said.

Weeks later, Eddie suggested Indian food to celebrate surviving. At Curry Dreams, a local Indian buffet, I saw a cockroach the size of my thumb crawl up the wall… and fall directly into a vat of curry.

We left immediately.

From that day on, Curry Dreams became Curry Nightmares.

Epilogue

Now, years later, I’m stirring lamb saag in a quiet kitchen, unemployed but oddly at peace. That bug didn’t end my career. That breakdown didn’t define me. It was just another chapter in a long, messy story.

If you have a morbid curiosity to follow along on this strange life journey, you know where to find me.

Thanks for listening.Talk soon.

Hello, world.

A few months ago, I became what feels like a new tech archetype: an unemployed ex–Big Tech engineer with over 25 years in the industry. In today’s climate, that sentence alone is enough to spike blood pressure. Yet, strangely, my recent layoff hasn’t felt like a crisis. It’s felt more like a quiet pause, a semi–early retirement, or at least a transition into the next chapter of life.

That perspective didn’t come from optimism or denial. It came from math.

For more than a decade, my family has maintained a savings rate north of 50% of our gross income. It wasn’t flashy. It wasn’t Instagram-worthy. But it fundamentally changed how we experience uncertainty. A high savings rate builds a large emergency fund, and that buffer softens the sharpest edges of job loss. More importantly, sustained saving allows those dollars to compound into income-producing investments, eventually buying you something far more valuable than luxury goods: optionality.

If you do it long enough, financial independence becomes less of a dream and more of a boring, inevitable outcome.

Debt Is a Black Hole (I Know Because I Fell In)

Let’s start with the most important lesson: debt is financial gravity.

Educational and consumer debt behave like a black hole attached to your wallet—relentlessly sucking money away while giving nothing in return but anxiety and regret. Whatever you bought with that debt is long gone, but the payments linger, quietly preventing you from building emergency savings or investing in your future.

I know this intimately. Early in my marriage, my wife and I sat down for an honest look at our finances and realized we owed over $150,000 in student loans. This revelation landed just days after she told me she was pregnant. It was shortly after the financial crisis, my job felt unstable, and the debt alone was costing us more than $1,000 a month in interest.

We were trapped.

So we declared war on debt.

We slashed our spending to the bone. Aside from rent, we lived on about $100 a week: groceries, toiletries, everything. We lived like monks with Wi-Fi. During the day, I worked my consulting job. At night, I built Android apps, fast, ugly, practical apps, anything that could generate revenue.

This was around 2010, when Android was the Wild West. Apps that did almost nothing were making real money. I churned out about 50 simple apps: timers, flashlights, bird guides, concrete calculators. I priced them at one or two dollars, and somehow… they sold.

I worked 80–90 hours a week for years. When my son was an infant, his crib sat beside my bed. At 1 a.m., after another night of coding, I’d hold his tiny hand for a few quiet minutes before falling asleep. That was the time I had with him back then. It was brutal, but it worked.

Within two years, we were debt-free.

We used a psychological “snowball” strategy, paying off the smallest loans first. Was it mathematically optimal? No. Was it emotionally powerful? Absolutely. Watching balances disappear kept us moving forward.

Freedom tastes better than efficiency.

Housing: Ignore Realtors, Embrace Math

Housing is usually the largest expense in a household, which means it’s also the biggest lever.

Whether renting or buying makes sense depends on location, but once you decide to buy, ignore the advice to “get as much house as you can afford.” That mindset quietly sabotages long-term wealth.

Instead, I used the 80/20 rule. If you’re willing to compromise 20% on size, finishes, commute, or neighborhood, you can often cut the price dramatically.

That’s exactly what we did. We bought a modest home with a large backyard, decent schools, and a longer commute. It was a short sale, and the total monthly payment—including taxes and insurance was around $2,000. That was a fraction of what many of my coworkers were paying.

The result? Massive monthly savings that went straight toward paying off the mortgage early.

Today, our housing costs are down to about $900 a month in property taxes and insurance. That’s it.

Transportation Is a Toaster Oven, Not a Personality

Cars are utilities, not status symbols.

If you live in a dense metro area, public transportation may be the cheapest solution. If you need a car, buy one that maximizes reliability and minimizes lifetime cost. For me, that meant used Toyotas and Hondas, three to five years old.

This is the sweet spot: you get 80–90% of a car’s usable lifespan for half (or less) of the original price. These vehicles are mass-produced, boring, and extremely durable. They’re also cheap to insure and repair.

I currently own two fully paid-off Honda CR-Vs. Each costs about $150 per month in total lifecycle expenses: gas, insurance, maintenance, everything. That’s a tiny fraction of the cost of a new luxury vehicle.

Boring wins again.

Food: Brown Bags, Crock Pots, and Quiet Wealth

We rarely eat out, maybe once a month for special occasions. For over 15 years, my wife and I brown-bagged our lunches. By my rough estimate, that habit alone saved us a few hundred thousand dollars.

Cooking isn’t hard. With basic skills, you can make food that’s 80–90% as good as restaurant meals at a fraction of the cost. And if you want a true engineering marvel in your kitchen, allow me to introduce the crock pot.

For about 15 minutes of prep time and pennies of electricity, it produces massive quantities of cheap, delicious, nutritious food. Chili, curry, soup, set it and forget it.

We buy mostly unprocessed foods, often organic, from reasonably priced stores like Aldi. For a family of four, our monthly food budget runs around $700–$800.

Managing Consumerism in a Family

Minimalism is easy when you’re single. Add a spouse and kids, and things get… complicated.

The solution isn’t deprivation, it’s containment.

We set monthly spending ceilings. We teach our kids to think about value, not just desire. (This lesson is working better on my son than my daughter, but progress is progress.)

I also noticed that most consumer goods lose their appeal shockingly fast, sometimes within days. So I built a small “distribution center” in my basement where unused items are inventoried and resold on eBay, Facebook Marketplace, or Mercari. Unsold items are donated for tax deductions.

That system recovers about 10–20% of what we spend on consumer goods, which quietly adds up.

The Boring Path to Freedom

With these strategies, we saved more than 50% of our income for many years. None of this is revolutionary. Outside the tech bubble, this is how many people already live.

But in an industry facing endless layoffs, these habits can turn a terrifying event into a manageable transition.

My layoff didn’t feel like falling off a cliff. It felt like stepping onto a different trail.

If you’re morbidly curious to follow along on this life journey, you know where to find me. And if you found this useful, welcome to the quiet, unsexy, deeply satisfying world of financial independence.

See you next time.

Hello world.

Until recently, I was a senior engineer at a Big Tech company, with 25 years in the technology industry behind me. Today, I’m unemployed, watching the industry I grew up in sprint headlong into what feels like the largest speculative bet of its lifetime.

Not long before I was laid off, my former employer held a company-wide AI hackathon. By that point, the company had already invested billions of dollars into training frontier models and building out the infrastructure to support them. Massive data centers. Enormous training runs. A portfolio of large language models that needed, urgently, to justify their existence.

The goal of the hackathon was simple, at least on paper: come up with bold, transformative, responsible AI ideas that could, somehow, turn all of this spending into revenue.

In other words: please make the AI pay for itself.

The A-Team (and a Reality Check)

I joined a hackathon team led by a senior engineering leader—let’s call him Danny. On paper, it was the A-Team.

There was Jimmy, the Canadian tech lead who could brute-force his way through any codebase. Subash, an H-1B architect who was frighteningly sharp. Alex, a junior engineer who had survived our brutal internship program. And Lionel, a support team lead with an effortlessly charming British accent which, by the way, is an unfairly powerful asset when pitching business ideas in tech.

We brainstormed and quickly landed on what seemed like an obvious win: an AI-powered customer support agent.

The idea was straightforward. Most customer support cases are repetitive. With a large language model enhanced by Retrieval-Augmented Generation (RAG)—essentially giving the model access to proprietary internal knowledge, we believed the agent could autonomously resolve roughly 90% of incoming cases.

Within a day, we had a working proof of concept running inside a Docker container.

Feeling confident, we presented the idea to a business leader in our product line, let’s call him Leo.

Leo listened patiently. Then he dismantled the idea.

Yes, he acknowledged, the agent might handle 90% of cases. But the remaining 10%—the hard, messy, ambiguous ones were what consumed over 90% of the support team’s time. Those were the cases customers escalated. Those were the cases that mattered.

What we had built, he argued, was essentially a glorified FAQ page.

Then came the line that stuck with me: “This feels like a shiny solution in search of a problem.”

A Microcosm of the AI Industry

That moment crystallized something uncomfortable.

Despite the massive investments and the relentless internal pressure to “AI-ify” everything, it was genuinely difficult to extract real, defensible business value from AI in many domains. Outside of narrow niches with abundant training data, returns were murky at best.

That small hackathon experience now feels like a perfect microcosm of the broader AI industry.

Hundreds of billions, possibly trillions, of dollars are being poured into AI. Yet most AI initiatives today are losing money. In some cases, a lot of money. Each API call to a large language model can cost several times more to serve than it generates in revenue.

Meanwhile, the hype machine roars on.

World models. Humanoid robots. Confident proclamations that AGI is just around the corner.

Some of these efforts are legitimate research. Others feel like science fiction being aggressively monetized. If this reminds you of the dot-com bubble, you’re not wrong, except this time, the scale is orders of magnitude larger.

Financial Alchemy and Corporate Optics

The problem is that the money has already been spent. And investors want returns now.

To maintain the appearance of growth, companies resort to financial gymnastics: buying AI services from each other to simulate demand, reclassifying existing product revenue as “AI revenue” after adding superficial features, and framing mass layoffs as “AI efficiency gains” while quietly shifting work offshore.

The result is a market that looks strong on the surface but increasingly fragile underneath.

Big Tech now accounts for roughly 40–50% of the S&P 500’s total valuation. If confidence cracks, if investors realize these investments won’t pay off on the promised timelines, the unwind could be violent.

If the Bubble Bursts

If an AI collapse happens, it likely won’t be a single dramatic moment. A weaker, AI-only company could fall first. A large investor could panic. Political backlash against data centers and energy costs could accelerate sentiment shifts.

The downstream effects would be severe: an AI winter where funding dries up, market caps shrink, RSUs evaporate, and layoffs spread not just across AI teams, but across entire platforms and ecosystems.

Beyond tech, the impact would ripple outward: data centers halted, semiconductor orders canceled, real estate markets strained, financial institutions exposed. In a worst-case scenario, cascading failures could spill into the broader economy.

This isn’t a prediction. It’s a plausible risk path.

How to Cope (Not Panic)

So what can individuals, especially software engineers, do?

At work: double down on core problem-solving skills. Learn to wield AI as a tool, not fear it. Build T-shaped expertise that spans engineering, product, and business.

Outside of work: build a much larger emergency fund than traditional advice suggests. Reduce fixed expenses. Create alternative income streams: side projects, businesses, anything that isn’t tied to a single employer.

None of this is easy. And none of it is guaranteed to be necessary.

This may all amount to nothing more than the late-night musings of a laid-off engineer with too much time to think. The AI boom could continue. Stocks could soar. Everyone could get rich.

But history suggests that when investment, hype, and financial reality drift too far apart, gravity eventually reasserts itself.

For now, all we can do is stay alert, stay flexible, and remember that technological revolutions are rarely as smooth or as profitable as they look at the peak.