In our (Jeff Kodad) most recent episode of "This Week in Za" we were joined by Bianca Jefferson. The episode is a lot of fun, and I learned about a new type of breakfast meat! What on YouTube or https://t.co/4eO8jcUhqH
https://t.co/XgGDWxQ7HP
I got to hang out with @carlfranklin and @richcampbell on .NET Rocks!
We discussed the change to our user interfaces that is coming because of AI/LLMs. I really like the name of this episode, “Beside, Inside, and Outside AI”, as it describes a great way to think about integrating into our software systems.
Check it out at
https://t.co/tiPur58mrm
Back at Build 2023, Steven Batiche suggested AI would move from sitting beside applications to living inside them, and eventually beyond them.
Chad Michel digs into how that prediction is playing out today on .NET Rocks!
🎧 https://t.co/le5CXqLrRo
#LLM#Agents#AIApps #DotNetRocks
Do you enjoy fun? If so, I am confident you always love listening to @richcampbell , and lucky for you, he is our guest on This Week in Za.
https://t.co/rWQgirW2xH
Microsoft cut 15,000 people in 2025 and ended the year with roughly the same headcount it started with.
That's not a workforce reduction. It's a talent pipeline flush.
There’s a major gap between how companies describe their layoffs and what's actually driving them.
https://t.co/7dWQ1Z98SW
In this episode, Howard Huffman of Huffman Engineering joins us to discuss manufacturing, engineering, power lifting, and pizza.
https://t.co/afK44W13Qk
Claude knows! —>
The Lump of Labor Fallacy and Why AGI Unemployment Panic Is Economically Illiterate
Let me lay this out with full rigor, because this argument deserves to be prosecuted completely rather than waved away with a sound bite.
I. What the Lump of Labor Fallacy Actually Is
The lump of labor fallacy is the assumption that there exists a fixed, finite quantity of work in an economy — a lump — such that if a machine (or an immigrant, or a woman entering the workforce) does some of it, there is necessarily less left for human workers to do. It treats employment as a zero-sum pie.
The fallacy was named and formalized in the early 20th century but the error it describes is far older. It animated the Luddite riots of 1811–1816, where English textile workers destroyed power looms convinced that the machines would steal their jobs permanently. It drove opposition to the spinning jenny, the cotton gin, the mechanical reaper, the steam engine, the telegraph, the railroad, the automobile assembly line, the personal computer, and every other major labor-displacing technology in the history of industrial civilization.
Every single time, the catastrophists were wrong. Not partially wrong. Structurally, fundamentally, categorically wrong — because they misunderstood the nature of economic production itself.
The reason the fixed-pie assumption fails is this: demand is not fixed. Work generates income. Income generates demand for goods and services. Demand for goods and services generates new categories of work. This is an engine, not a reservoir. When you drain some of the reservoir with a machine, the engine speeds up and refills it — and often refills it past its previous level.
II. The Classical Economic Mechanism That Destroys the Fallacy
To understand why the lump-of-labor assumption is wrong about AGI, you need to understand the precise mechanism by which technological unemployment resolves itself. There are four distinct channels, all operating simultaneously:
Channel 1: The Productivity-Demand Feedback Loop (Say’s Law, Modified)
When a technology increases the productivity of labor or replaces labor entirely in a given task, it lowers the cost of producing whatever that task was part of. Lower production costs mean either:
∙Lower prices for consumers (real purchasing power rises), or
∙Higher profits for producers (which get reinvested, distributed as dividends, or spent as wages for other workers), or
∙Both.
Either way, aggregate real income in the economy rises. That additional real income does not evaporate. It gets spent on something — including goods and services that didn’t previously exist or were previously too expensive to consume at scale. That spending creates demand. That demand creates jobs.
This is not a theoretical conjecture. The average American in 1900 spent roughly 43% of their income on food. Today it’s around 10%. Agricultural mechanization didn’t produce a nation of starving unemployed farm laborers — it freed up 33% of household income to be spent on automobiles, television sets, air conditioning, healthcare, education, travel, smartphones, and streaming services, most of which didn’t exist as industries in 1900. The workers who left farms went to factories, then to offices, then to service industries, then to information industries. The economy didn’t run out of work. It metamorphosed.
I like this quote from @mcuban,
What I tell every entrepreneur, and it’s more crucial today. “ when you run with the elephants there are the quick and the dead. Adopt tech quickly , you can out maneuver big companies. “
My similar refrain, "Don't Panic, Adapt."
Last week, a viral AI-generated job exposure visualization surfaced—showing software developers, writers, analysts, and similar roles scoring high (7–10+) on potential AI impact—and sparked widespread panic that "AI is wiping out all white-collar jobs." The creator even pulled it down due to the extreme doom interpretations it triggered.
But this Microsoft paper paints a calmer picture. AI is shaking up a ton of fields, especially software development—it'll never be what it was even 5 years ago. Back then, just knowing a language was gold, but really, structuring solid code and solving problems mattered way more. Now AI knocks out a huge chunk of the rote code-writing, but devs are still the ones guiding it—distilling requirements, architecting, validating outputs, debugging the weird edge cases. The real value just shifted upward, from typing to thinking.
Still, it's mostly augmentation, not wipeout. AI handles tasks or assists, and humans stay in the loop. Job/wage outcomes depend on how companies actually use it, not some inevitable robot takeover.
|High exposure doesn't mean extinction.
AI changes work—Don't Panic, adapt.
@antigravity, I tried to get Claude to fix a UI issue multiple times and failed. I tried to get Copilot to fix a UI issue multiple times and failed. @antigravity fixed it first try :)