Berkshire’s New CEO Labels Four Forever | Analysis by Brian Moineau

Why Berkshire’s new boss just named four “forever” stocks — and quietly shrugged at two others

When a company built by Warren Buffett hands the reins to Greg Abel, investors listen. In his first shareholder letter as Berkshire Hathaway’s CEO (published in early March 2026), Abel did more than salute the past — he clarified which holdings he views as “forever” and which ones didn’t make that inner circle. The choices are equal parts reassurance and subtle signal about what matters when stewardship changes but the mandate to preserve value doesn’t.

This matters because Berkshire’s portfolio is enormous, concentrated, and iconic. What the company says about its biggest positions matters for markets and for anyone trying to think long term about durable businesses.

What Abel called “forever” — and why it matters

Abel described four holdings as core, long-term positions Berkshire expects to own for decades:

  • Apple
  • American Express
  • Coca-Cola
  • Moody’s

Why those four? The common thread is clarity: strong brand moats, predictable cash flow, management teams Berkshire trusts, and business models that have shown resilience across cycles. Abel’s naming of these companies signals continuity with Buffett’s playbook: identify exceptional businesses, buy sizeable stakes at attractive prices, and hold through time.

A few quick context points:

  • These four companies make up a large portion of Berkshire’s equity portfolio — together they’re a center of gravity for the firm’s public-equity bets.
  • Apple in particular is massive for Berkshire by market value; Coke and AmEx are classic Buffett examples of consumer and financial moats; Moody’s offers a high-margin, durable niche in credit-rating services.

The two notable omissions

Two of Berkshire’s other very large holdings were notably absent from Abel’s “forever” roster:

  • Bank of America
  • Chevron

That doesn’t mean they’re being sold tomorrow. But omission is itself information. In Bank of America’s case, Berkshire has already trimmed its position significantly in recent quarters, and Buffett historically points to stakes he truly intends to “maintain indefinitely” — the omission hints at reduced conviction or simply a pragmatic reweighting. Chevron remains a huge position but is more exposed to commodity cycles and capital allocation debates than the four Abel singled out.

Why this distinction matters for investors

  • Signaling vs. action: Naming a stock as “forever” is not a trade order, but it is a governance signal. It tells shareholders what management views as reliable anchors of capital allocation.
  • Style clarity: The four “forever” names reinforce Buffett-era core principles — brands, margins, predictability — while the omitted names underscore that portfolio composition can shift even at a company famous for buy-and-hold.
  • Succession risk and continuity: Abel’s list reassures those worried that Berkshire might abandon Buffett’s temperament. It also highlights the open question of who will make day-to-day portfolio choices; Abel inherited stewardship responsibilities but doesn’t have the same public track record as Buffett.

How to think about “forever” stocks for your own portfolio

  • “Forever” for Berkshire ≠ forever for every investor. Berkshire’s stake sizes, tax position, and horizon are unique.
  • Look for durable cash flows and pricing power, not just nostalgia. Coca-Cola’s brand vs. Chevron’s commodity exposure illustrates the difference.
  • Be honest about concentration: Berkshire’s approach is concentrated bets. Most individual investors should balance conviction with diversification.
  • Reassess when the business changes, not when the stock price does. Holding forever means monitoring the business — management quality, competitive edge, and capital allocation — not checking charts daily.

A few concrete investor takeaways

  • If you admire Buffett-style investing, study why Apple, AmEx, Coke, and Moody’s fit that mold rather than simply copy the tickers.
  • Treat the omission of Bank of America and Chevron as a reminder that even blue-chip holdings can be downgraded in conviction.
  • For long-term investors, focus on business durability and management incentives; for traders, these signals may matter more for short-term flows than long-term fundamentals.

What this moment reveals about Berkshire itself

  • Continuity with adaptation: Abel’s letter emphasizes sticking to durable businesses while acknowledging an evolving portfolio and new capital-allocation dynamics.
  • Cash pile and patience: Berkshire still holds massive cash reserves — a tactical advantage if valuations wobble and buying opportunities appear.
  • Uncertainty in day-to-day management: With the portfolio’s traditional stewards reshuffled, the market is watching how Berkshire will source new big ideas and allocate capital at scale.

My take

Abel’s naming of four “forever” stocks reads like a careful bridge: it comforts investors who feared a wholesale departure from Buffett’s philosophy, while also hinting that practical decisions — trimming, adding, and pivoting — will continue. For most individual investors, the lesson isn’t to buy these exact names blindly; it’s to adopt Berkshire’s discipline: buy strong businesses with durable advantages and hold them until the story truly changes.

Sources




Related update: We recently published an article that expands on this topic: read the latest post.


Related update: We recently published an article that expands on this topic: read the latest post.

Cloud Fragility: Azure Outage Wake-Up Call | Analysis by Brian Moineau

The day the cloud hiccupped: why the Azure outage matters for everyone who trusts “the cloud”Introduction — a quick hook
On October 29, 2025, Microsoft Azure — the backbone for everything from enterprise apps to Xbox and Minecraft — suffered a major outage that knocked services offline for hours. It wasn’t just an isolated blip: coming less than two weeks after a large AWS disruption, it’s a reminder that the modern internet depends on a handful of cloud giants, and when they stumble, the effects ripple far and wide.

What happened (context and background)

  • The outage: Microsoft traced the disruption to an “inadvertent configuration change” in Azure’s Front Door (its global content and application delivery network). That change produced widespread errors, latency and downtime across Azure-hosted services and Microsoft’s own consumer offerings. Microsoft described rolling back recent configurations to find a “last known good” state and reported recovery beginning in the afternoon of October 29, 2025. (wired.com)
  • Scope and impact: Downdetector and media reports showed spikes of tens of thousands of user reports; enterprises, airlines, telcos and gaming platforms all reported interruptions. For many organizations, critical workflows — check-ins at airports, corporate email, payment flows, game servers — were affected for hours. (reuters.com)
  • The bigger pattern: This failure came on the heels of a major AWS outage just days earlier. Two large outages in short order highlighted that cloud “hyperscalers” (AWS, Azure, Google Cloud) do a lot of heavy lifting for the internet — and that concentration creates systemic risk. Security and infrastructure experts called the incidents evidence of a brittle, over-dependent digital ecosystem. (wired.com)

Why this matters

— beyond the headlines

  • Centralization of critical infrastructure: A small number of providers run a large share of the world’s cloud workloads. That reduces redundancy at the infrastructure layer even when individual customers use multiple cloud services.
  • Cascading dependencies: A single provider outage can cascade through supply chains, third-party services, and customer systems that assume those cloud primitives are always available.
  • Configuration risk: The Azure incident reportedly began with a configuration change. Human or automation errors in configuration management remain one of the most common single points of failure in complex cloud systems.
  • Rising stakes with AI and real-time services: As businesses put more of their mission-critical systems, real-time APIs, and AI stacks in the cloud, outages have bigger economic and safety implications.

Key takeaways

  • Cloud concentration is convenience — and systemic risk. Relying on a handful of hyperscalers reduces costs and friction but increases the chance of widespread disruption.
  • Redundancy needs to be multi-dimensional. Multi-cloud isn’t a silver bullet; true resilience requires diversity of providers, regions, CDNs, and careful architecture to avoid single points of failure.
  • Operational practices matter: flawless configuration management, rigorous change control, and staged rollbacks are essential — but not infallible.
  • Prepare for the long tail: even after “mitigation,” some customers may face lingering issues. Incident recovery can be messy and incomplete for hours or days.
  • Transparency and post-incident analysis help everyone learn. Clear post-mortems, timelines, and fixes improve trust and enable better preventive design.

Practical resilience tips for teams (brief)

  • Identify critical dependencies (auth, payment, CDN, DNS, messaging) and map which cloud services they use.
  • Design graceful degradation paths: cached content, offline modes, and fallback providers for non-critical features.
  • Test failover regularly and run chaos engineering experiments to validate real-world responses.
  • Keep a communications plan: customers and internal teams need timely, actionable updates during incidents.

Concluding reflection
Cloud platforms have done enormous good — they let small teams build global services, accelerate innovation, and lower costs. But the October 29, 2025 Azure outage is a sober reminder: outsourcing infrastructure doesn’t outsource systemic risk. As we continue to push more of the world into the cloud (and into AI systems that depend on it), resilience must be an engineering and business priority, not an afterthought. The question for companies and policymakers alike isn’t whether the cloud will fail again — it’s how we design systems, contracts and regulations so those failures cause the least possible harm.

Sources



Related update: We recently published an article that expands on this topic: read the latest post.


Related update: We recently published an article that expands on this topic: read the latest post.