Reading

At the AI Engineer World's Fair 2026 in San Francisco, Pamela Fox, Principal Cloud Advocate at Microsoft, conducted a workshop on model swapping. She argued that generic benchmarks often fail to reflect how large language models actually behave in specific applications, urging developers to swap and test models directly within their own scenarios.

Fox compared GPT-5.5, Kimi K2.6, DeepSeek V4 Flash, and Mistral Large 3 on the Microsoft Foundry platform. Her demonstration progressed from basic letter-counting prompts to complex tasks including Retrieval-Augmented Generation (RAG) groundedness, image input handling, multilingual pitfalls, tool calling, and building a travel agent with LangChain v1.

Beyond functional testing, she detailed evaluation methodologies such as string-check evals, LLM-as-a-judge, using Microsoft's new ASSERT tool to generate test sets from specifications, and optimizing prompts with DSPy to find instructions that even the cheapest model can satisfy. This sequence provided engineers with a practical workflow for model selection and evaluation.

Wellington Management has released a video episode featuring Christina Kopec Rooney, the firm's Head of US Wealth, alongside Sandhya Douglas, Head of Strategic Partnerships. The program focuses on rethinking investment risk, specifically exploring how Ms. Rooney's perspective on risk has evolved over time.

As an executive at a major asset management institution, Ms. Rooney discusses the strategic selection of risks taken in pursuit of investment returns. This topic offers valuable insight into how professional institutional investors balance risk and reward in complex market environments.

Published on October 19, 2026, the episode provides an opportunity for investors to understand the internal risk management perspectives at Wellington Management. While specific arguments are not detailed in the public description, the speakers' positions and the topic's relevance make it a noteworthy resource.

Morgan Stanley published a video interview on October 19, 2026, featuring Carolyn Campbell, the firm's Asset-Backed Securities (ABS) Strategist. The episode focuses on the specific impact of the current macro-financial environment on the expansion of artificial intelligence infrastructure, particularly the role played by changes in borrowing costs.

According to the official video description, Campbell explains how rising borrowing costs are currently slowing down the AI data center boom. She also analyzes which conditions or market dynamics could serve as key drivers for a potential rebound in financing activities for such projects.

For professional readers interested in the capital structure of the AI industry, debt financing channels, and the return cycles of infrastructure investments, this video offers an immediate perspective from a frontline strategist at a major investment bank. While a full transcript is not provided, the clear topic and speaker identity make it a valid resource entry point for understanding current bottlenecks and opportunities in AI financing.

According to Reuters, artificial intelligence company Anthropic recently privately pitched a draft bill to members of the US Congress aimed at regulating safety measures for frontier AI models. The core of the proposal lies in setting explicit quantitative thresholds: the government would only be permitted to block the release or use of an AI model if it poses a foreseeable and imminent risk capable of causing over $1 billion in losses, or resulting in the death or serious injury of more than 50 people.

Beyond the numerical red lines for economic loss and human casualties, the draft restricts the specific sources of such risks: they must stem from the manufacture or release of biological weapons, AI models evading developer controls, or cyberattacks. An Anthropic spokesperson stated that the bill reflects recommendations from the company's "Advanced AI Framework" published earlier this year, aiming to grant the government the "ability to stop or contain dangerous deployments of the most powerful models."

Regarding procedural mechanisms, the draft requires developers to test frontier AI models, disclose results, and undergo independent evaluation. Independent assessment bodies must register with the US Department of Commerce and periodically evaluate AI labs and their models. While AI labs may pay these bodies, compensation cannot be tied to evaluation outcomes to ensure independence. If an assessment body determines a model presents the imminent risks listed in the bill, it must notify the Department of Commerce within 72 hours of completing the evaluation.

Once the US Department of Commerce identifies a model as risky, it can petition a judge to order a suspension of the model. The draft explicitly prohibits other US government departments, agencies, or officials from ordering suspensions of development, deployment, or internal use, centralizing intervention power through judicial review. Politico reported that judges in the US District Court for the District of Columbia would hold the authority to issue such suspension orders.

US asset manager Barry Ritholtz, in a blog post dated October 19, 2026, made an observation: since World War Two, the US government's every major methodological adjustment to inflation statistics has moved almost entirely in one direction—lowering the reported inflation number.

He traces this line from 1944 to 2025. During World War Two, the Cost-of-Living Index (COLI) understated price increases by 4 percentage points from 1941 to 1944, as goods became unavailable, wages froze, and black-market pricing took over. In 1945, the US Bureau of Labor Statistics (BLS) renamed the data series the Consumer Price Index and redefined it as a fixed-basket price index.

Between 1972 and 1975, the stagflation era gave birth to the concept of core inflation. After the 1972–73 food price spike, Fed Chair Arthur Burns had Fed staff strip out food, reasoning it was 'weather, not monetary policy'; after the embargo, energy was removed. Soon after, used cars, mobile homes, and children's toys were stripped one by one until only a fraction of the basket remained. Ritholtz coined the phrase 'Inflation Ex-Inflation' in 2005 to describe this—removing inflation itself from inflation data.

In 1983, BLS changed the housing component of CPI-U from asset price plus mortgage interest cost to owners' equivalent rent (OER). Ritholtz acknowledges this is conceptually defensible—a house is an appreciating asset while shelter is a consumer good—but he points out that the 2002–07 housing bubble did not show up in CPI because rent prices were restrained by millions of Americans stampeding into no-doc, ARM mortgage, home-ownership purchases. The 2021–23 shelter price lag similarly exposed the OER distortion.

The 1995–96 Boskin Commission is where Ritholtz's language is sharpest. He directly called its report 'pure political bullshit.' The Commission estimated CPI overstated inflation by 1.1 points a year (range 0.8–1.6); its political purpose was to reduce cost-of-living adjustments (COLA) and tax bracket creep, saving $1 trillion in deficit reduction over the next decade or so. Ritholtz asks: if inflation had been properly reported (e.g., pre-Boskin), might the Federal Reserve have picked up the distortions in the backward, real estate-driven economy?

In 2000, the Fed shifted its preferred inflation gauge from CPI to PCE; in 2004 it moved further to core PCE; since 2012 the 2% target is formally anchored to PCE. Ritholtz notes this lowered the inflation number the Fed is judged against by approximately 0.5 points per year versus CPI. In 2017, the Trump tax cut legislation adopted the chained CPI (C-CPI-U) that Obama had proposed and then withdrawn, for tax bracket indexing.

Ritholtz considers the 2025 episode qualitatively different from all prior adjustments. DOGE firings and other staffing cuts led BLS to suspend CPI collection in several metro areas, replacing it with imputation. Trump fired Commissioner McEntarfer on August 1, 2025, after a bad jobs report, and the Antoni nomination that followed did not go through. Ritholtz writes: this is not creatively re-measuring inflation downwards, but ceasing to measure it entirely.

He acknowledges that changes like OER have theoretical justification, and admits he could be wrong. But his core observation is directional: every major change since 1983 moved in the same direction, and almost always timed to a fiscal or political need.

The strongest counterargument is selection bias: the Boskin Commission's substitution bias, quality adjustment, and new goods bias are standard index-theory problems, not uniquely American; the OER asset/consumer distinction has economics consensus support. Methodological adjustments that could raise inflation readings may never have been proposed or were already rejected, so the 'all downward' pattern may not be a conspiracy but the natural direction of statistical methodology evolution—because most index-theory corrections do tend to lower reported values.

Voice AI company Deepgram processes quadrillions of audio tokens a year for more than 200,000 developers and 1,400 organizations. Its offline batch workloads—contact-center analytics, medical transcription and similar scenarios—are extremely sensitive to inference cost. In October 2026, Deepgram and the AWS Forward Deployed Engineering team published a complete engineering record of porting the Nova-3 speech-to-text model to Trainium2 chips, self-reporting that a single EC2 trn2.3xlarge instance processed 11–70% more audio per dollar.

The port was not a simple compilation swap. The team first ran Nova-3 in eager mode on Trainium2 via TorchNeuron and checked which operations fell back to the CPU, then compiled with torch.compile, producing separate static-shape graphs for the encoder and decoder. The compiled path ran every model operation on Trainium2 with no CPU fallbacks detected. Numerical accuracy was validated at two levels—layer-level output consistency against CPU and end-to-end Word Error Rate—ensuring alignment with Deepgram's reference values.

The real gains came from kernel-level optimization. The team adopted a flywheel strategy: enable an NKILib pre-built kernel, profile with Neuron Explorer, then tune or hand-write a replacement based on profiling insights. Three key findings each addressed a specific bottleneck. The reference kernel for the feed-forward network layer reloaded the full set of projection weights from off-chip memory for every token tile, making memory bandwidth the limiting factor as token count grew; the hand-tuned kernel loads each weight tile once and reuses it across multiple token tiles, achieving 2.0× lower latency at batch size 96. The experimental NKILib kernel for depthwise 1D convolution framed the operation as an implicit GEMM, leaving Tensor Engine utilization low; the team rewrote it as a broadcast multiply-accumulate loop on the Vector Engine, reaching full engine utilization for a 1.5× speedup at batch size 96. The conv2d layers hit a compilation bottleneck beyond batch size 32, preventing single-graph compilation; since NKILib had no conv2d kernel, the team wrote one from scratch in NKI, unlocking batch sizes above 32 and achieving up to 50× speedup on the convolution module at batch sizes ≤32.

The final source of gain was the runtime language. Nova-3 performs a sequence of small decoder calls for each audio chunk, making host-side dispatch the bottleneck at low batch sizes. Deepgram's production serving stack is itself written in Rust, so the team built a lightweight Rust runtime: Rust coordinates eight model replicas through a shared work-stealing queue, while a C layer loads and executes ahead-of-time-compiled NEFF files directly through the Neuron Runtime API, entirely bypassing the Python interpreter. Compared with a multiprocessing Python baseline, the Rust runtime eliminates interpreter overhead; compared with a multithreaded baseline, it further alleviates GIL serialization. At the throughput-maximizing batch size, the Rust runtime delivered a 7.5% throughput gain over the multiprocessing Python baseline.

It should be emphasized that all the above figures are self-reported measurements by Deepgram and AWS. The baseline is the compute options Deepgram had previously been running, whose specific configurations are not disclosed. The wide 11–70% range covers different workloads and batch sizes; readers evaluating their own scenarios should not directly extrapolate from this range.

According to WIRED, privacy company Redact discovered that approximately 80 help and FAQ pages on WhatsApp’s website inadvertently exposed hidden instructions designed for Meta’s own large language model within their underlying code. These instructions, intended to guide the behavior of an AI chatbot, included sections explicitly titled “WHAT NOT TO SAY.”

The leaked directives revealed that when users asked about account deletion or mentioned legal action, the AI was instructed not to recommend contacting data protection authorities, regulators, or supervisory bodies. It was also forbidden from citing, quoting, or interpreting WhatsApp’s Terms of Service, Privacy Policy, or data protection regulations such as GDPR and CCPA, nor could it make statements regarding WhatsApp’s liability.

Dan Saltman, CEO and founder of Redact.dev, noted that the incident highlights a gap between what users are told and what LLMs are actually instructed to do. While many of the found instructions simply directed users to official support channels, some restrictions clearly were not meant for public exposure.

After WIRED contacted Meta, the text was removed from all affected pages. WhatsApp spokesperson Joshua Breckman stated that the exposure was due to a bug that has now been fixed. He emphasized that these were instructions for the chatbot, not direct messages to users, intended to ensure accurate responses while preventing the AI from offering legal advice. It remains unclear if third-party chatbots accessed the text or how long it had been visible.

An international research team comprising the University of Washington, Oxford University, and NVIDIA published the detailed design scheme for the generative artificial intelligence system RFdiffusion3 in the journal Science on October 16 local time. The core breakthrough of this system lies in its ability to design proteins and nucleic acids based on individual atomic combinations, with the functionality of the designed proteins verified through real chemical reactions.

The corresponding author of this study is David Baker, who won the 2024 Nobel Prize in Chemistry for his contributions to predicting protein structures using computers. His landmark achievements include developing the RosettaFold protein structure prediction system. While previous versions RFdiffusion1 and 2 relied primarily on RosettaFold's structure prediction network, RFdiffusion3 references the network architecture of AlphaFold3. It can represent a single amino acid with up to 14 atoms, designing novel protein structures by directly adjusting the three-dimensional coordinates of each atom.

Researchers compared design effectiveness across 41 active sites of existing enzymes. Results showed that RFdiffusion3 outperformed RFdiffusion2 in 37 of these tests, with generation speed approximately ten times faster. Crucially, the paraoxon-degrading enzyme and peptide-cleaving enzyme designed by RFdiffusion3 successfully completed their expected chemical reactions in real experiments. This result marks a progression in AI-based protein research from 'predicting existing structures' to 'designing new molecules with target structures and functions,' confirmed at the experimental level.

Brooke Lacey has more than 290,000 followers on TikTok. Her current video editing workflow goes like this: she finishes recording on her phone, drops the file into a terminal, and about 15 seconds later a finished vertical short with captions, jump cuts, and zooms comes out. No uploading footage, no opening any traditional editing software. Driving this process are three tools—FFmpeg handles audio and video, Whisper does speech-to-text, Python acts as glue—all orchestrated by Claude Code.

The entire editing decision lives in a single TSV text file. Each row defines the start time, end time, shot size, and label for a cut. Once Claude generates this file based on her talking-head content, the same command can produce 15-second, 30-second, and 60-second versions plus a landscape crop from one raw take.

But the truly hard part isn't the toolchain—it's teaching Claude to understand her comedic timing. Not simply cutting silences, but learning the cadence of her voice, the length of the pause before a punchline, the ideal cut point after a word, and which repeated take has the best rhythm. Lacey says encoding this style required deliberate instruction and iteration, not one clever prompt.

She also turned her comment section into an ongoing content brief. After each video, she has Claude Code connect the video with its comments, identify what viewers questioned, debated, or wanted to see next, and generate a list of new ideas grounded in signals from her actual audience.

Lacey calls this system "lane OS"—inside Claude Code, she maintains separate memory, permissions, and status files for each product (lane). When the system makes a mistake, she traces it back to the relevant instructions and records the correction globally so the same error doesn't recur.

Her core lesson: creators must understand the craft before they can delegate it to AI. She was able to teach Claude to edit in her style because she already knew what a good cut sounds like, where a zoom should land, and why the timing matters. AI amplifies that judgment, but it does not replace the experience required to develop it.

This boundary is worth noting. Lacey's 15-second turnaround applies to her own talking-head-plus-jump-cut format; for more complex narrative structures, multi-person dialogue, or videos requiring fine visual effects, the automation level of the toolchain drops significantly. And "lane OS" itself is a personal infrastructure that requires continuous maintenance—every system error is an opportunity for human intervention and rule updates, not a fully automated process.

The Linux kernel's Error Detection And Correction (EDAC) subsystem plans to remove four legacy hardware drivers—i82975x, x38, xgene, and i3200—in version 7.4. Borislav Petkov, an AMD engineer and EDAC maintainer, explained in a merge request that while these drivers correspond to hardware rarely used in production anymore, they have recently received a surge of bug reports and "fixes" generated by AI/LLMs.

Petkov noted that without real users to test these old code paths, the AI-generated patches create significant maintenance noise. To combat this "frenzy," maintainers decided to orphan and subsequently delete the drivers. This move highlights a new challenge for open-source communities facing the proliferation of automated code generation tools: technical debt is not always caused by functional defects, but sometimes by the administrative burden of managing low-quality automated contributions.

In the 2010 letter to shareholders, Warren Buffett detailed Berkshire Hathaway's performance measurement standards and major capital decisions. Facing market volatility, he did not pursue short-term stock price performance but emphasized establishing a mechanism for long-term intrinsic value growth. This letter not only recorded the financial results of that year but also revealed the management philosophy behind them.

First, Buffett clarified the benchmark for performance evaluation. He stated: "To eliminate subjectivity, we therefore use an understated proxy for intrinsic-value – book value – when measuring our performance." This approach aims to eliminate biases caused by subjective judgment. Although the market value of some businesses is far higher than their book value, using conservative book value as a proxy indicator can more objectively reflect whether management has truly created returns for shareholders that exceed the index.

Second, the letter focused on analyzing the logic behind the acquisition of Burlington Northern Santa Fe (BNSF) railroad company. Buffett believed that railroads have significant cost and environmental advantages over trucking: "That’s three times more fuel-efficient than trucking is, which means our railroad owns an important advantage in operating costs." This structural advantage made BNSF a core asset for enhancing Berkshire's "normal" earnings power, with pre-tax income expected to increase by nearly 40%.

Additionally, Buffett emphasized managing uncertainty from a long-term perspective. He mentioned: "Money will always flow toward opportunity, and there is an abundance of that in America." Even during economic downturns or market chaos, Berkshire continued to make large-scale capital expenditures within the United States. This persistent pursuit of opportunities, rather than reactions to macro noise, constitutes the core characteristic of its capital allocation.

For contemporary readers, understanding this mechanism helps reflect on performance attribution issues in investing. For example, if a fund manager claims their strategy outperforms the market, but their performance relies on non-replicable market timing rather than verifiable improvements in operational efficiency, sustainability is difficult to ensure. Buffett's method suggests that we should focus on decisions that can translate into stable cash flows through specific operational advantages (such as cost structures), rather than merely looking at final investment return figures.

The Berkshire Hathaway Shareholder Letter 2010 was written by Warren Buffett and published in 2010. It is suitable for investors who wish to deeply understand performance measurement standards in value investing and the logic behind large M&A decisions. It is recommended to start reading from the "Performance" section, combined with the BNSF acquisition case study.