Why Your Developer Expertise Is Not Your Leverage

I watched one of the best software architects I've ever worked with get made redundant last year. Fifteen years of building platforms. Complex, high-stakes systems for large enterprise clients. Business-critical systems that entire organizations depended on. All gone in one day. And the ironic part? When it was over, he had almost nothing to show for it. Not because he hadn't done exceptional work — he had. But NDAs, client ownership clauses, and the nature of enterprise IT services meant he couldn't publicly reference most of it. No portfolio. No public proof. No artifacts that said "I built this." He had knowledge in his head and a résumé full of vague descriptions of projects he couldn't name. The Builder's Paradox If you've been a developer for more than a few years, you've probably felt this tension even if you haven't named it. The more specialized and impactful your work becomes inside an organization, the less portable it is outside of it. I've started calling this singularity: