David Linthicum

The recent Microsoft cloud outage was treated as another temporary service disruption, but the bigger story is not downtime. The bigger story is dependency.

For many enterprises, Microsoft is no longer just a productivity vendor or a cloud provider. It is the identity layer, the collaboration layer, the endpoint management layer, the security layer, the developer platform, the database platform, the AI platform, and the infrastructure platform. That makes every major Microsoft incident more than a technical inconvenience.

When Azure has a major problem, it can affect much more than Azure workloads. Microsoft 365, Outlook, Teams, Azure management portals, dependent SaaS providers, identity workflows, customer-facing applications, and third-party platforms that use Microsoft infrastructure can all be exposed to the same failure domain.

In this episode, David Linthicum explains why the Microsoft outage should force enterprises to rethink vendor concentration, Microsoft monoculture, cloud dependency, and the hidden risks of platforms that run on Microsoft underneath. This is not an anti-Microsoft argument. Microsoft delivers enormous value. But value and dependency are not the same thing.

The AI industry has entered a new phase: not just better models, but a constant flood of new models, refreshed models, renamed models, specialized models, cheaper models, reasoning models, coding models, agent models, open-weight models, and gated frontier models.

Model-tracking sources show a rapid stream of October 2026 releases from companies including Google, OpenAI, Moonshot, MiniMax, DeepSeek, and others. LLM Stats listed recent releases such as Google Gemini 4 Carbon, OpenAI GPT-6.1 Terra, Moonshot Kimi K3.1 Pro, MiniMax M3.1 Flash, and DeepSeek-V4.1-Flash-1017 within a short late-October window, while LLM Gateway reported 22 new AI models released in October 2026 from 17 providers.

That competition can be good for users. It can lower prices, improve quality, expand open-weight alternatives, and force the major labs to move faster. Artificial Analysis shows meaningful differences across intelligence, cost per task, speed, latency, and context window, which means users and enterprises can increasingly match models to workloads instead of assuming one model should do everything.

But there is a downside: the market is becoming harder to understand. Benchmarks change, model names blur together, access rules vary, prices move, and yesterday's best option can become today's expensive legacy choice. The result is not always empowerment; sometimes it is decision fatigue disguised as innovation.

Amazon's latest "boomerang" recruiting push is a revealing case study in corporate overconfidence colliding with reality. After cutting more than 30,000 jobs across the company, including workers tied to cloud computing and artificial intelligence, Amazon and AWS are now reaching back out to some former employees with shortened hiring paths and carefully polished messages about exciting AI work. The pitch is obvious: the talent it discarded is suddenly useful again. The more cynical reading is that Amazon, like other companies that rushed to proclaim AI as a workforce replacement, discovered that automation cannot simply absorb institutional knowledge, judgment, troubleshooting, customer context, and technical nuance.

Klarna and Ford have already offered similar warnings, cutting human roles in favor of AI before having to rebuild human capacity when the results fell short. Amazon's rehiring effort suggests not bold innovation but damage control: a company trying to patch the hole it created while pretending this was always normal recruiting. The story is less about AI taking over the workplace than executives learning, slowly and expensively, that workers were not spare parts after all; they were the system holding everything together before management decided to test whether hype could do their jobs instead alone.

The midterm elections may become a turning point for the AI industry, not because voters suddenly became AI experts, but because AI stopped being an abstract technology story and became a kitchen-table issue involving electricity bills, water use, jobs, privacy, competition, and Big Tech power.

Recent reporting shows that Democrats are preparing to use control of Congress to scrutinize AI companies, Big Tech, and the lack of AI safety rules, while local backlash against AI data centers has become a serious political force in several states and communities. TIME reported that an NBC exit poll found 56 percent of voters said AI and data centers were a crucial or major factor in their vote for Congress, a clear signal that AI policy is no longer confined to think tanks and tech conferences.

This episode looks at what the election means for AI companies, hyperscalers, startups, investors, and enterprise buyers. The short answer is that AI will keep growing, but the easy-growth era is ending. The industry now has to explain its costs, prove its value, and deal with politics at the federal, state, and local levels.

Big Tech is still spending staggering amounts of money on AI infrastructure, but investors are beginning to ask the obvious question: where is the business payoff?

Amazon is the latest warning sign. Reuters reported that Amazon shares came under pressure after massive AI-related capital spending and cash burn overshadowed the fastest AWS cloud growth in nearly five years, showing that even strong cloud demand may not be enough to calm investors when infrastructure costs keep climbing.

This episode looks at whether the AI boom is turning into a capital expenditure arms race, where Amazon, Microsoft, Google, Meta, Oracle, and others are forced to keep spending just to avoid falling behind, even before the long-term revenue model is fully proven.

Every few years, the technology industry falls in love with a new prediction: this time, the tools are so powerful that programmers are finished. We heard it with expert systems. We heard it with code generators. We heard it with fourth-generation languages, CASE tools, object-oriented programming, component-based development, offshore development, cloud platforms, and low-code/no-code tools. Each one was promoted as the end of software development as we knew it. And each time, the opposite happened. Developers did not disappear. They moved up a layer of abstraction, learned the new tools, and became more productive.Now we are hearing the same story about AI. Bill Gates and others are warning that AI could eliminate huge numbers of jobs, including knowledge work. I respect the concern, but I think the conclusion is wrong. AI coding tools are powerful, but they are not replacing architecture, engineering judgment, accountability, integration, or business understanding. They are removing routine work and changing the developer's role.

That matters because fear is starting to dominate the AI conversation. Instead of panic, we need logic. History tells us that better tools usually create more software, more demand, and more need for skilled people.

Microsoft is offering voluntary exits to a large group of employees while pouring enormous resources into artificial intelligence, and the strategic question is not whether AI matters — it clearly does — but whether the company is underestimating the human expertise that keeps complex enterprise platforms running.

In this episode, David Linthicum takes a skeptical look at Microsoft's AI-era workforce strategy and the risk of trading durable operational knowledge for short-term balance-sheet relief. The danger is not simply losing headcount. The danger is losing the people who know why systems behave the way they do, how enterprise customers actually use the products, where the fragile dependencies live, and which problems cannot be automated away with a Copilot prompt.

If Microsoft's most experienced and marketable employees take the exit package, rivals could inherit talent, customers could feel the support impact, remaining teams could burn out, and the company could discover that AI is powerful but not mature enough to absorb the hidden work performed by seasoned engineers, product leaders, and customer-facing experts.

This video explores why enterprise AI is about to move beyond the current obsession with large foundation models and frontier LLMs. While these systems are powerful and useful for productivity, communication, customer service, scheduling, coding, analysis, and other general business tasks, they are unlikely to remain the center of enterprise AI architecture.

The next phase will be driven by small and medium language models that are narrowly focused, business specific, and built around enterprise data. These models can operate closer to the systems, workflows, and data that matter most, giving organizations better control, lower costs, improved privacy, stronger governance, and more practical business value.

Rather than relying on one massive model to do everything, enterprises will increasingly build tiered AI architectures where frontier models support broad language and reasoning tasks, while smaller models handle the core operational work. This shift will change how CIOs, CTOs, architects, and business leaders think about AI investment, risk, data sovereignty, and long term strategy.

If your organization is putting all its AI bets on the biggest models, this video explains why the smarter move may be building focused AI systems that solve specific business problems.

Right now, the AI industry is operating like a gold rush where everyone insists they have already found the mother lode. Startup founders are stretching timelines, enterprise vendors are relabeling old automation as intelligence, executives are pretending pilots are strategies, and customers are quietly exaggerating how much AI has improved their work. The technology is real and powerful, which is exactly what makes the exaggeration so easy to sell. A good demo can look like magic, even if the production version still hallucinates, leaks context, fails audits, or needs a team of consultants to babysit it.

This is happening because the incentives are badly aligned. Investors reward massive visions. Buyers reward confident vendors. Boards reward leaders who appear ahead of the curve. Employees reward tools that make them look more productive. Nobody wants to be the person saying, "This is promising, but not ready," while competitors are shouting about transformation, disruption, and human-level intelligence.

The result is a market full of half-truths, inflated claims, and strategic optimism. AI may change everything eventually, but for now many people are selling tomorrow's breakthrough as today's finished product. That is not innovation; it is theater with a subscription contract and a confident slide deck.

What if organizations could build powerful AI together without ever sharing their private data? This video explores federated learning marketplaces, an emerging cloud computing idea that could reshape how hospitals, banks, governments, and companies collaborate on artificial intelligence. Instead of moving sensitive records into one central database, each organization trains an AI model locally on its own data. Only the model updates are shared, combined, tested, and then made available through a marketplace where buyers can license trusted AI models. The key innovation is provenance: a clear record showing who contributed, what type of data was used, how the model was trained, and how well it performed. This creates a new way to build AI that is private, auditable, and commercially valuable. We will break down how the process works, why it matters for regulated industries, what risks still exist, and why model provenance could become as important as the model itself. If cloud computing is moving from simple storage and servers to trusted AI collaboration, federated learning marketplaces may be one of the most important ideas hiding in plain sight. This is not just about better models; it is about making AI collaboration possible where data sharing was once impossible.