Daily Digest — July 15, 2026
Must read today: Ben Thompson’s Stratechery Update — “IBM Misses, IBM’s Mainframe Moat, IBM’s Many AI Problems.” Goes far beyond the earnings miss to explain why IBM’s highest-margin business — selling customers hardware they’re trapped on plus software that runs only on that hardware — is threatened even if no customer has actually migrated yet. The United Airlines anecdote (hundreds of millions to port 1960s Fortran off mainframes) makes the abstract concrete: AI makes that migration feasible for companies that could never have justified the cost before.
[PULSE] Markets — July 15
Sources: Yahoo Finance · Bloomberg · r/wallstreetbets · WSJ Tech News Briefing
What moved: Nasdaq up 0.90%, S&P +0.38%, Dow flat. CPI came in cooler than expected — prices down 0.4% MoM, core CPI flat at 0.0% monthly, 2.6% YoY. Bank earnings crushed: the big five (JPMorgan, BofA, Goldman, Wells Fargo, Citi) combined for $49B in Q2 profits, driven by SpaceX IPO fees, Hormuz-driven trading volatility, and M&A advisory. Goldman CEO Solomon called it an “AI capex super cycle.” ASML hiked its sales forecast for the second time this year on strong AI chip demand — Europe’s most valuable tech company validating the infrastructure thesis from the equipment layer. IBM still reverberating at -25% (worst day since 1968). Oil holding at $79-80 as Trump walked back the 20% Hormuz toll but pledged to escalate strikes until Iran relents. SpaceX fizzling to $1 above IPO price.
What’s driving it: Two forces that should be contradictory but aren’t. CPI cooling and bank earnings beating gives the market the “soft landing plus strong corporate performance” narrative it wants. But oil above $79 on Hormuz and Trump pledging escalation threatens to undo the inflation progress within weeks. Fed Chair Warsh told Congress “mission accomplished is not my view” on inflation — the cooler CPI number isn’t enough to take rate hikes off the table while the Middle East remains unstable.
ASML is the validation story worth naming. People think of Nvidia and Samsung as the primary AI winners, but the AI infrastructure buildout is an entire manufacturing assembly line, and each cog in that line is printing money right now — driven by demand upstream. ASML makes the lithography machines that make the chips. When ASML raises guidance twice in a year, it’s not forecasting — it’s reporting order books from TSMC, Samsung, and Intel. Memory (SK Hynix IPO), GPUs (Nvidia), equipment (ASML) — the thesis is being confirmed at every layer of the stack. IBM is the mirror image: the company whose customers are redirecting spend toward exactly what ASML’s customers are buying.
Retail signal: WSB’s top post is a $200K SpaceX loss in a Roth IRA. SpaceX at $1 above IPO price means the early retail buyers who got in on the hype are all underwater or barely even. “Imagine bag holding space x” has become the thread’s running joke. The IBM crater is being processed as comedy: “IBM should change their ticker to ICBM.” ASML barely registers on WSB — too European, too boring, too correct.
[BUSINESS] IBM’s Mainframe Moat — Thompson Explains Why the Escape Route Changes Everything
Source: Stratechery · Ben Thompson · Morning Brew · Bloomberg
The story: IBM’s preliminary Q2 miss was its worst trading day since at least 1968 — shares down 25%. CEO Arvind Krishna attributed the shortfall to customers redirecting capex from mainframe upgrades to AI infrastructure (servers, storage, memory). The z17 mainframe launch, which had the strongest start in IBM’s history, saw demand drop sharply in the final weeks of June. Transaction Processing software revenue also fell. Thompson’s analysis: IBM’s mainframe business extracts value both on capex (the hardware) and opex (the software that only runs on that hardware). Customers have been trapped for decades because migrating away was prohibitively expensive. AI changes that equation.
My take: Thompson catches the thing the market priced in but didn’t name: it’s not the capex crowdout that should worry IBM. It’s the awareness that an exit exists.
IBM’s mainframe business is one of the most elegant traps in enterprise technology. You pay capex for the hardware. You pay opex for the software that only runs on that hardware. You can’t leave because your transaction processing systems — the ones that process every airline reservation, every bank transfer, every retail purchase — are written in languages and frameworks that only run on IBM iron. Moving them would cost hundreds of millions and take years. So you stay and you pay.
But here’s the thing: why do you need a wagyu steak when a filet from the grocery store would do? These legacy COBOL applications that have been running on mainframes for decades are overclocked — consuming far more CPU and power than the modernized versions of those same applications would require on commodity cloud infrastructure. The mainframe isn’t selling performance anymore. It’s selling lock-in.
United Airlines actually did it. Scott Kirby told Thompson they spent “several hundred million dollars” rewriting code off a Fortran-based system from the 1960s. It took years. It’s still not fully done. But it unlocked everything United has built since — the best tech stack in the airline industry. The end of the rainbow looks good. Most companies just couldn’t justify the cost of the journey.
AI breaks the math. Code porting — translating working software from one language or platform to another — is exactly the kind of task AI handles well. No creativity required. A working reference to compare against. Deterministic success criteria (does it produce the same output?). The Bun rewrite from Monday’s digest is the proof point at a smaller scale: 535K lines of Zig to Rust in 11 days. The same pattern applied to mainframe COBOL or Fortran, with the same prerequisites (test suite, engineer with context, deterministic verification), makes a multi-year migration into a multi-month project.
The advice I’d give a CIO considering the move: do it piecemeal. Application by application. Test before deploying. Don’t try to boil the ocean — pick the application with the best test coverage and the clearest success criteria, port it, validate it, then move to the next one. That way you stop double-dipping on IBM’s capex-plus-opex model incrementally, rather than betting the whole infrastructure on a single cutover. IBM has had a monopoly on these mainframes for decades. You don’t break out of a monopoly in one sprint.
Thompson’s sharpest observation: even if zero customers have actually migrated, the awareness that they could changes IBM’s business right now. A customer who believes they might move off mainframes in two years doesn’t buy a new z17 today. They limp along on existing hardware. They don’t expand their Transaction Processing contracts. They redirect the capex they would have spent on a mainframe upgrade toward the AI infrastructure they’ll need for the migration itself. IBM’s Q2 miss isn’t a one-quarter anomaly. It’s the early signal of a structural shift in how trapped customers think about their options.
Krishna’s letter had a tell that Thompson caught. In Q3 2025, IBM blamed strong z17 sales for lower Transaction Processing software revenue — customers were focused on hardware, software would follow. In Q2 2026, IBM blamed weak z17 sales for lower Transaction Processing software revenue — customers redirected spend, software fell with it. The z17 gets blamed regardless of whether it sells or doesn’t. That’s not analysis. That’s a business trying to explain why the tide is going out.
[AI] OpenAI’s First Device — A Screenless Speaker Betting on Personality Over Display
The story: OpenAI’s first consumer device will be a mobile, screen-free smart speaker designed as a “humanlike AI companion.” It will control smart-home devices, play media, answer questions, respond to messages, and tap into ChatGPT’s capabilities. The defining feature: personality and the ability to connect on a “humanlike level.” OpenAI envisions it anticipating needs and surfacing information proactively. The device is being built in partnership with io Products (Jony Ive’s company) and led by Tang Tan — the former Apple VP at the center of Apple’s trade secret lawsuit filed last week. Separately, Apple is in talks with PrismML to shrink AI models to run directly on iPhones, reducing Alibaba’s Qwen model from 54GB to under 4GB.
My take: This is the device Apple is suing to stop, and the description explains why Apple is worried.
A screenless smart speaker doesn’t compete with the iPhone on the iPhone’s terms. It competes on the terms the iPhone is worst at: ambient, always-on, conversational AI that lives in your home and knows your context without requiring you to pick up a device and look at a screen. The iPhone is a visual computing device. This is an auditory computing device. Different modality, different use case, different relationship with the user.
It feels like the newest iteration of Alexa at first glance. But where OpenAI can differentiate is if this thing actually learns you — builds a profile over time, understands your tendencies, remembers years of your history. That’s a Jarvis from Iron Man for the everyday consumer. Alexa is a stateless voice-activated answer machine. You ask, it responds, it forgets. A personalized AI companion that knows how you think, what you care about, and what you’re likely to need next is a fundamentally different product. The difference isn’t the speaker hardware. It’s the model underneath and whether OpenAI lets it accumulate context over months and years rather than resetting every session.
Amazon tried the companion angle and it never worked because Alexa was a rules engine dressed up as a voice assistant. ChatGPT is an actual language model that can hold a conversation, remember context, and adapt tone. Whether that’s enough to make a home speaker feel like a companion rather than a gadget is an open question. But it’s the right question to ask, because the failure mode of every previous smart speaker was that people used them for timers and weather and then stopped.
The Apple-PrismML talks are the defensive move. Apple’s strategy has always been on-device intelligence — privacy as the differentiator, no cloud dependency. But running frontier models on a phone requires compression that degrades capability. PrismML taking a 54GB model to under 4GB is impressive engineering, but the compressed model is not the same model. The trade-off is capability for privacy and latency. OpenAI’s device makes the opposite trade: cloud-first, full model capability, no pretense of on-device processing. The question for consumers is whether they care more about privacy or capability. Apple is betting privacy. OpenAI is betting capability. Both could be right for different segments.
The Ive/Tan connection makes this personal. Ive defined Apple’s design language for two decades. Tan led iPhone hardware. Both are now building a device that deliberately isn’t a phone, for a company that Apple is suing. The lawsuit isn’t just about trade secrets. It’s about the people who built the iPhone deciding the next thing isn’t a phone.
[ENG] The Great Flattening — When Building Is Cheap, Choosing What to Build Is the Job
Source: TLDR · “The Great Flattening” · “The Tower Keeps Rising”
The story: Two pieces making the same argument from different angles. “The Great Flattening”: as intelligence costs drop, the backlog stops being a capacity problem. Founders can now execute a hundred ideas for the cost of one, so the constraint shifts from “can we build it” to “can we identify what to build, and can we sell it.” Companies seeing this are already flat by design: fewer engineers, larger token spend, faster shipping, direct line from customer sentence to merged code. “The Tower Keeps Rising”: AI removes the friction of understanding a project’s shared language — what concepts mean, where boundaries are, which invariants matter. This produces code that “looks strange but works” while removing the human understanding that used to be required to navigate the codebase.
My take: Both pieces are describing the same structural shift, and neither fully reckons with what it means for engineering organizations.
“The Great Flattening” gets the economics right. If building is cheap, the bottleneck moves upstream to problem selection and downstream to distribution. The company with three engineers and a large token budget ships faster than the company with thirty engineers and a Jira backlog. The backlog itself becomes an artifact of a world where implementation was expensive. When implementation is cheap, you don’t prioritize a backlog — you build everything and see what sticks.
“The Tower Keeps Rising” gets the knowledge problem right. The shared language of a software project — the concepts, the boundaries, the invariants, the ownership — used to live in human heads and get transmitted through code review, arguments, and hallway conversations. AI can now absorb and reproduce that context without any human having internalized it. Code that “looks strange but works” is code that was written without human understanding of the project’s conventions, but with the AI’s statistical model of what those conventions probably are.
Put them together and you get the organizational question that matters: if building is cheap and understanding the codebase is no longer required, what’s left for the engineering team to do? The answer is the thing both pieces gesture at but don’t name explicitly: judgment about what to build, how it should behave at the edges, and what happens when it fails. That’s the SE/architect role. The person who talks to the customer, understands the problem, defines the constraints, and evaluates whether the output actually solves it. What took weeks for one software engineer to code and a week to review is now getting written by AI, reviewed by AI, and pushed by AI in a fraction of the time. Backlogs disappear like a rabbit in a magician’s hat.
Goldman’s CFO said yesterday: “It’s not a moment for structural rework of our human capital footprint.” JPMorgan’s Dimon said AI cut jobs 30-40% in certain areas. There’s a cynical read worth naming: companies can use AI spend as an understandable excuse to cut non-profit business sections that were eating costs — without the PR nightmare of saying “we’re downsizing because the unit wasn’t performing.” AI makes the layoff palatable. And the non-looping agents that work great for personal projects don’t yet work for enterprise-grade software with SLAs. You still need human eyes and ears when making changes to production systems. The flat companies described in “The Great Flattening” are already doing what Dimon describes. The question is whether Goldman’s position — augment, don’t restructure — holds as the cost of building continues to fall.