The Wrong Question to Ask About Tech Royalty
When news broke of the unexpected passing of former Microsoft executive Soma Somasegar, the tech press fell into its predictable, ritualistic rhythm. Obituaries painted a picture of a quintessential corporate titan: a man who spent nearly twenty-seven years inside the belly of the Redmond beast, climbing the ranks to lead the Developer Division, before pivoting to a second act in venture capital at Madrona Venture Group.
The industry shed tears for the loss of a "visionary builder" and a "pillar of the community."
They missed the point entirely.
The tech press is asking the wrong question. They are asking: How do we replicate the career of a loyal corporate titan? They should be asking: Did the very structure that empowered Soma Somasegar actually stifle the broader developer ecosystem for two decades?
We love a neat narrative. We love the story of the loyal soldier who stays at one company, ships massive products, and retires to a comfy venture seat. But if you spend twenty-seven years inside a monopoly, you aren't just building software. You are building walls. To truly understand Somasegar’s legacy—and why Silicon Valley’s collective shock reveals a deep misunderstanding of tech history—we have to look at the brutal reality of what his era actually did to the software world.
The Golden Cage of the Developer Division
Let's look at the facts. Somasegar took over Microsoft’s Developer Division (DevDiv) in the early 2000s. To the casual observer, this was the golden age of .NET, Visual Studio, and MSDN.
I was on the ground during those years, watching enterprises sink millions of dollars into licensing fees. From the outside, DevDiv was a powerhouse generating billions. From the inside, it was a massive operation designed to lock developers into a proprietary ecosystem.
+-------------------------------------------------------+
| THE EARLY DEV DIV TRAP |
+-------------------------------------------------------+
| [Proprietary Visual Studio] -> [Windows-Only .NET] |
| | |
| v |
| [High Enterprise Licensing Fees] |
| | |
| v |
| [Developer Vendor Lock-in] |
+-------------------------------------------------------+
The logic of that era was simple: if you control the tools, you control the developers. If you control the developers, you control the enterprise. Somasegar executed this strategy perfectly.
But perfection inside a monopoly is a dangerous metric.
While DevDiv was optimizing for Windows NT and enterprise desktop apps, the real world was moving somewhere else. The open-source movement wasn't just knocking at the door; it was tearing down the fence. Linux was winning the server. LAMP stacks were powering the early web. Git was changing collaboration.
Microsoft, under the leadership of Steve Ballmer and executed by executives like Somasegar, spent years treating open-source software like an existential threat. They didn't see it as an innovation engine; they saw it as a competitor to be crushed or contained.
The True Cost of Proprietary Tech
When the press praises the stability and growth of Microsoft under his tenure, they ignore the opportunity cost.
- The Web Disconnect: An entire generation of web developers grew up viewing Microsoft tools not just as irrelevant, but as actively hostile to their workflow.
- The Mobile Miss: Because DevDiv was fundamentally tethered to the Windows-first doctrine, Microsoft completely missed the foundational shifts in mobile development. iOS and Android didn't just win the hardware war; they won the developer mindshare war using tools that owed nothing to Redmond.
- The Open Source Delay: The pivot to open-sourcing .NET and making Visual Studio Code cross-platform didn't happen because of a sudden realization of goodwill. It happened because the old model had completely run out of gas.
To call this era an unmitigated success is revisionist history. It was a highly profitable, brilliantly executed holding action that delayed Microsoft's entry into the modern, open computing world by at least a decade.
The Venture Capital Pivot Fallacy
The second act of the standard tech obituary focuses on Madrona Venture Group. In 2015, Somasegar left Microsoft to become a venture capitalist. The consensus view is that this was a natural evolution—a tech heavyweight bringing deep operational expertise to the startup ecosystem.
This is another area where the industry chooses comforting narratives over cold mechanics.
Operational expertise inside a trillion-dollar monopoly does not automatically translate to early-stage venture success. In fact, it often does the exact opposite.
Imagine a scenario where an executive is used to having thousands of engineers, billions in budget, and the sheer gravity of an incumbent brand to push through a product. When that executive sits across the table from a three-person startup trying to find product-market fit with zero budget, a structural disconnect occurs.
The Institutional Bias
Monopoly executives are trained to manage risk, protect downside, and optimize existing distribution channels. Startups must do the exact opposite: they must take existential risks, embrace chaos, and build distribution from absolute scratch.
The influx of late-career corporate executives into the Pacific Northwest venture ecosystem didn't accelerate radical innovation; it institutionalized it. It created a preference for "safe," enterprise-focused B2B SaaS companies that looked like smaller versions of the products these executives used to build. It’s why Seattle, despite having the highest concentration of cloud engineering talent on earth between AWS and Azure, historically lagged behind the Bay Area in creating truly disruptive, consumer-facing or paradigm-shifting tech companies.
The money followed the familiar. The familiar was enterprise software. And the enterprise software looked a lot like the stuff shipped in Redmond fifteen years prior.
Dismantling the Premise of the "Tech Icon"
If you search for public sentiment on this era of tech leadership, you find questions like: What made the leaders of 2000s-era Microsoft so resilient?
The question itself is flawed. They weren't resilient because of superior strategic foresight; they were resilient because they were sitting on top of the most lucrative corporate monopoly in human history.
Let's look at the real mechanics behind the metrics:
| Metric | The Enterprise Narrative | The Reality Check |
|---|---|---|
| Developer Lock-In | High adoption rates of Visual Studio and .NET frameworks. | Developers had no choice if they wanted to build for the dominant OS. |
| Revenue Growth | Consistent year-over-year enterprise licensing increases. | Driven by aggressive corporate auditing and bundled enterprise agreements. |
| Ecosystem Size | Millions of registered MSDN developers. | A closed loop that largely ignored the explosive growth of the open web. |
When we praise leaders from this era for driving revenue, we are praising them for tax collection. The Windows monopoly was a tax on global computing, and DevDiv was the mechanism that ensured developers kept paying it.
The Real Lesson of the Redmond Lifers
The sudden loss of a figure like Somasegar is a human tragedy, and the shock felt by his peers is real. He was, by all accounts, a deeply respected manager and an incredibly sharp mind.
But respecting the person should not mean romanticizing the era.
The era of the twenty-five-year corporate lifer executive is dead, and we shouldn't try to revive it. The tech landscape no longer tolerates the slow, deliberate, inward-looking strategy that defined 2000s-era Microsoft.
Today's developer ecosystem moves too fast. If you build a golden cage today, developers don't buy into it; they fork it, build an open-source alternative, and render your enterprise suite obsolete before your next quarterly planning cycle.
The true legacy of that executive generation isn't the software they shipped. It is the cautionary tale of what happens when a company mistakes market dominance for technological relevance. They spent decades defending an empire, only to realize the rest of the world had moved to a different continent.
Stop looking back at the corporate lifers as the blueprint for tech leadership. They were masters of a game that is no longer being played.
