Back issues
Simon Willison gives a first person account of building Battle Drones, a browser based real time strategy game, through twelve major iterations and 321 commits made by coding agents, mostly Claude Code. He quotes the prompts he used, including telling the model to make it a lot more fun, and links transcripts, a proposal document the agent wrote for LLM versus LLM battles, and replays of Claude Haiku 5.5 against GPT-6 Luna. One feature was built in 45 minutes to use up the remainder of a weekly token allowance, and multiplayer runs over audio between two phones. He is explicit that he knows almost nothing about game development and chose it as a low stakes field to test agents. The receipts are all linked and the iteration pattern is the lesson.
Faros, which sells engineering analytics, rounds up press reports of large companies capping AI spend: Accenture charging Claude usage above 29 dollars per employee to project budgets (404 Media, which Accenture partly disputed), Uber's 1,500 dollar monthly allowance per coding tool after reportedly burning its 3.4 billion dollar budget by April (Bloomberg), Microsoft aiming to cut internal Claude spend by a third (TechRadar citing The Information), Meta's Claude Code users falling from 60,000 to 30,000, Walmart's token allowances for Code Puppy, Tesla's 200 dollar weekly limit (Electrek citing The Information) and Amazon removing a token leaderboard that rewarded consumption. Every figure is a trade article relaying another outlet's report, and the piece is honest about that. The argument is that caps cannot tell a 500 dollar engineer doing hard work from one stuck in failed retries. The last third pitches Faros's own Token Engineering product. The roundup earns the desk; the pitch does not.
Simon Willison links to an essay called an obituary for programming and quotes its core passage: programming was paid puzzle solving, and regular people needed programmers because they could not do it themselves. He adds two lines of his own. A programmer who enjoys shipping working systems gets a gift from LLMs, while one who loved solving the puzzle directly has lost something real. The body holds only the quote and those two lines, not the essay itself. It keeps as a short statement of what changes for the person at the keyboard.
Faros publishes a guide to what Claude Code costs: included with Pro at 20 dollars, Max at 100 or 200, Team at 20 to 125 per seat, Enterprise at 20 per seat plus usage, or pay per token with Opus 5.5 at 4 dollars per million input and 20 per million output, Fable 5.1 at 10 and 50, Haiku 5.5 at 0.10 and 0.50. It explains the shared five-hour usage pool, weekly limits, usage credits and Max API credits. The second half argues that the invoice cannot judge worth and that leaders need cost per outcome, with the Faros CEO's anecdote of an engineer spending 20,000 dollars in a month and nobody knowing if that deserved a promotion or a talk. The pricing table is a usable reference; the outcome metric is the product Faros sells.
Pragmatic Engineer's podcast with Will Larson covers how engineering management changed from the zero interest rate era to now, with stories from Digg's failed v4 rewrite, a black market for servers at Yahoo, and Staff engineers who only want fun problems. Larson argues middle management is becoming precarious and that managers should return to line management and reskill, as he has, and the show notes say AI is bringing technical decision making back to leadership. The body is the episode summary and takeaways, not the transcript. AI is a thread rather than the subject, and the piece is thin on it.
The New Stack describes Respan's Rust-based AI gateway, which keeps a small core and moves routing, providers and security into compiled plugins after two years of building on LiteLLM. The body arrives without its opening paragraphs, so the upgrade that prompted the rewrite is named only in the headline. LiteLLM is porting its own gateway to Rust one route at a time, and the article flags that LiteLLM's seven-times-lower-overhead claim comes from LiteLLM's own benchmark harness. It is real reporting on AI infrastructure that stays thin on the reader's side of the work, and the New Stack discloses its owner invests in OpenAI.
A Lenny's Newsletter podcast page with show notes for an interview with creator Brooke Lacey, who has a TikTok audience above 290,000. She walks through the Claude Code plus FFmpeg plus Whisper pipeline that cuts a raw phone video in about 15 seconds and explains how she taught the model her jump-cut cadence and how she mines comments for scripts. The body is a timestamped outline plus sponsor credits with no transcript, so the detail is thin. It is a first-person account of one person replacing an editor with a tool chain, which earns the amplifier desk.
Fortune reports from its Most Powerful Women conference on executives rethinking what AI productivity gains should deliver. Indeed's chief revenue officer says engineers write 50 percent more code and employees save six hours a week; that figure is the company counting its own output. Dropbox says it is studying cognitive atrophy from outsourcing thinking to AI, and Bristol Myers Squibb is weighing how to split productivity gains between the business and its workers. Quantum Workplace data on higher burnout among frequent AI users is cited without detail. The fetched body runs on into an unrelated HR advice column from the same newsletter.
Faros AI proposes cost per outcome as the measure for AI-assisted software work: total spend divided by accepted results, with failed attempts kept in the numerator because you paid for them. The post argues that a cheaper model can cost more per outcome if it needs more attempts, fails verification more often or needs more rework, and that success must be defined before measuring so the standard cannot drift to flatter the results. No data is offered; it is a definition and an argument. Faros sells engineering analytics and the frame also sells its product, but the metric answers the productivity question the paper keeps asking.
A Towards Data Science writer reads Google's Gemini 4 Argon launch by looking for where it loses instead of where it wins. Argon took first on repository-level software engineering but sits well behind on terminal work, and a careless call can cost 10 or 20 dollars. The practical content is in the API changes: one shared pool of 1,048,576 tokens across input, thinking and output, a default output cap of 65,536, long decode for background jobs, three thinking levels, and two breaking changes (the old thinking_budget integer and the MINIMAL setting now return HTTP 400; explicit caching is gone). Two code samples include guards the author wants in production scripts. The benchmark figures are Google's own chart, which the author says outright. Useful for anyone deciding whether to put this model to work.
The Swiss AI team publishes release notes for Apertus 1.5, which extends its fully open 8B and 70B models with image and audio input, an optional thinking mode, a context window of 262,144 tokens, and better tool use. The models were continued pretrained on trillions of additional tokens and released under Apache 2.0 with open data and training details, with a technical report on arXiv. All capability claims are the project's own. The tail of the body is Hugging Face model card chrome. It keeps as a primary source on a fully open model release.
A GitHub tutorial on opening a Copilot app session inside VS Code so a developer can continue the agent's conversation, review its changes line by line, edit and test locally, and push to the session's pull request. The framing is that the agent does the long or repetitive work and then hands control back for closer human review. It is a vendor how-to for its own product, with no measurement. The handoff pattern between an autonomous run and a human review pass is the piece's one idea.
Notes from Aakash Gupta's podcast with James McAulay on a Claude Code setup he calls a Growth OS for marketers who cannot ship code. It wires in analytics (PostHog over MCP) and read-only Git, forces every experiment into a file with baseline and confounders before launch, and has a weekly retro that tells you when a test is ready to read and which ones are stale. New work passes two gates: a PRD skill, then a multi-agent refine where subagents critique the PRD before anything is built. The SEO example found the host's search traffic had fallen from about 25,000 to 10,000 visits and drafted the fix. McAulay says most claims of autonomous growth agents are overhyped. Thin and promotional in places, but a real workflow for running an experiment loop with an agent.
A Ruby gem author explains why he has archived his open source libraries. He quotes Matz on Ruby being designed for human joy, says that era has passed, and objects to Rails being controlled by a man whose views he finds abhorrent and who now uses LLM agents to churn out Rust apps. His stated reason for quitting is that the commons he contributed to is being strip mined to train the machines whose output pollutes it. The post ends by telling anyone who wants changes to ask their agent. It is a real and short argument from the refusing side of the shift, with no data in it.
Simon Willison gives a first person account of building Battle Drones, a browser based real time strategy game, through twelve major iterations and 321 commits made by coding agents, mostly Claude Code. He quotes the prompts he used, including telling the model to make it a lot more fun, and links transcripts, a proposal document the agent wrote for LLM versus LLM battles, and replays of Claude Haiku 5.5 against GPT-6 Luna. One feature was built in 45 minutes to use up the remainder of a weekly token allowance, and multiplayer runs over audio between two phones. He is explicit that he knows almost nothing about game development and chose it as a low stakes field to test agents. The receipts are all linked and the iteration pattern is the lesson.
ByteByteGo retells how Shopify moved its mobile apps off React Native back to Swift and Kotlin because coding agents made maintaining two native codebases cheap enough. The author flags the account as assembled from public sources. He describes how Shopify built Helix to break each screen into small reviewable checkpoints and how the apps expose their state through a headless CLI so agents can act and check results without reading screenshots. Four checks run on each piece: behavioural tests, visual review, adversarial code review and a final developer review. Numbers relayed from Shopify's engineering blog include the Shop app shipping native in 12 weeks and iOS startup falling from 3200 ms to about 2400 ms. The small checkpoint plus fast feedback loop is the transferable lesson.
ByteByteGo retells how Uber built Genie, an internal Slack bot that answers engineering support questions from Uber's wiki and internal Stack Overflow. Uber chose retrieval over fine-tuning for the bot, and the writeup walks through how documents are chunked, retrieved and handed to the model, with an LLM-as-judge pipeline checking answers for hallucination and relevance. The 45,000 questions a month figure is Uber's own count, relayed by a newsletter working from Uber's public posts. The useful part for a reader is the end-to-end shape of a retrieval system that includes a feedback and evaluation loop, not just the search step.
Craig McLuckie runs Stacklok and co-created Kubernetes, and he writes on the Stack Overflow blog about a Stacklok survey of 520 technical leaders at North American companies over 500 employees running LLMs or agents. Only 8 percent use a single model provider and 25 percent use five or more, but 53 percent name integrations to internal systems and MCP servers as the hardest thing to migrate, 57 percent say a provider migration would take four months or more, and avoiding vendor dependence ranked last among buying criteria. Stacklok sells the harness and gateway layer the survey says is the sticky part, so the house is measuring its own shelves, and the methodology beyond the sample description is not in the post. The finding that the model is swappable and the layer you build around it is not is the point for a reader deciding where to invest.
ByteByteGo explains the difference between prompt caching, which reuses the model's processing of a repeated prefix such as a long product manual, and semantic caching, which reuses a previous answer when a new question means the same thing. It walks through why input tokens cost money, where to place shared content so the cache hits, and why a matching question is not enough when the answer depends on who is asking or what a pronoun refers to. The body opens with a WorkOS advertisement before the article begins. The author flags the post as assembled from public sources. It is a clear explainer on what the model is given and what that costs.
Simon Willison notes Anthropic's announcement that it is donating the Agent Skills standard to the Agentic AI Foundation under the Linux Foundation, the same body that holds the Model Context Protocol, and quotes the pledge to keep skills open and vendor neutral. He points out he predicted this last December, and found his own prediction by prompting Claude to search his blog over MCP. A short link post carrying a primary source quote on a standard that governs what agents are handed. Thin, but on thesis.
A Google Cloud developer guide to building MCP Apps for Gemini Enterprise: a single HTML widget, a streamable HTTP backend on Cloud Run, OAuth setup and the console steps to register the server as a data store and enable its tools as actions. The fetched body begins mid-sentence, so the introduction is missing. It is a configuration walkthrough with specific flags and roles, not an argument. Useful to someone wiring tools into a model, thin for everyone else.
Jessica Kerr of Honeycomb argues that AI used well can make code more rigorous than what people wrote by hand, not just faster. Her evidence is anecdotal but specific: a 24 year old colleague who has never coded without AI uses property based testing, formal verification and architecture tests as his default, and Avdi Grimm runs agents that review code from multiple perspectives so his code gets more review than before. Her prescription when AI writes worse code is to change the development system around the agent, add deterministic tests, instrument the software and iterate on the reviewers. The piece gives a reader a concrete stance on where quality comes from when an agent writes the code.
SafeDep's analysis of the compromised LiteLLM 1.107.0 release on PyPI, which installed a credential stealer through a .pth file that runs in every Python process on the host. The body as fetched starts mid analysis, but the technical record is detailed: the wheels match BerriAI's normal release pipeline, no public GitHub Actions run built them, and SafeDep assesses with moderate to high confidence that the pipeline built from attacker modified source. The stealer explicitly harvests AI developer tooling, including Claude Code, Cursor, Codex and Gemini CLI configuration along with mcp.json files, plus the LiteLLM proxy's own table of provider API keys. SafeDep sells supply chain security tooling and this is partly a vendor showcase, but the target list is a direct warning for anyone running agents and proxies.
Brian Krebs reports on the emergency PHP update for two critical bugs allowing remote code execution, affecting every PHP version since 5.4 and nearly 70 percent of websites, with working exploits already in the wild and government sites in Europe going offline. Censys counts about 2.58 million exposed hosts and 54.9 million web properties running PHP. Wiz, disclosed here as an advertiser on the blog, says the flaws had been present for decades and that frontier AI models substantially reduced the barrier to turning them into an exploit; OpenAI calls it one of the most impactful security issues in recent memory. The AI found it angle is secondhand from Wiz, but the operational picture is independent and clear.
Ankit Jain of Aviator argues that AI code review has taken over bug finding but not the conversation about what a change decided and why, and proposes a five-layer process: a second agent challenges the plan, intent and acceptance criteria are captured onto the PR, repeated review comments become standing invariants, people debate the decisions the agents could not settle, and a named team owns the result. The slogan is that agents verify and people decide. The opening figure of a 76.3 percent rise in pull requests merged without review is relayed from a Faros AI report about Faros's own customers. The New Stack marks the piece as sponsored by Aviator, whose product sells this workflow.
Ars Technica reports that researchers at security firm Claroc enumerated about 6,800 shared Meta Muse conversation links through passive DNS, because every share link uses the domain cf.metaaiusercontent.com with the conversation name in the hostname. Opening a few hundred turned up an executive search candidate's notes naming a frontier lab contact, a company's internal revenue review, a loan application, a fraud alert with a partial account number, and a staff vacation calendar. Meta told Ars it has paused the sharing feature while it reviews the report; Claroc says it reported the issue through the bug bounty on October 8 and got no reply. The lesson for a reader is that an agent built for privacy leaked through an ordinary URL design decision, and the content people put into agents is exactly what leaks.
A Fortune commentary argues the US economy has never been so concentrated on a single bet, with AI capital spending near 2 percent of GDP and AI linked investment accounting for 39 percent of growth in the first three quarters of 2025 by a St. Louis Fed measure. It cites the BIS warning on circular financing and the Magnificent Seven at 35 percent of the S&P 500, then makes the case that enterprise diffusion is slow, services sectors resist, and the productivity payoff will arrive decades later than markets expect. The author allows that AI could break the pattern because it reasons, but only with deep adoption across workers and workflows. The numbers are sourced to named institutions. It is a macro argument on the wire, not a story about how work changes.
GitHub's engineering blog explains how it moved nearly all repositories to live in both its own data centers and Azure while Git traffic grew exponentially under what it calls the agentic shift, with power capacity limits forcing the pace. The remaining busiest repositories are blocked by a 25 millisecond round trip because the write quorum waits on the slowest healthy replica, and the post describes a change to write serialization that gets them across and opens the way to stateless replicas. It is a primary source about its own infrastructure. The thesis connection is that agents are now the load that drives core developer infrastructure decisions, though the body is about storage architecture.
Google has released llm-d 1.0 as an open-source Kubernetes-native stack for distributed LLM inference built with Red Hat and IBM and about 500 contributors under the CNCF sandbox. The post argues that agent traffic, with its shared prefixes, bursts and multi-step loops, breaks round-robin serving, and shows a demo of 1,000 sandboxed agents hitting one endpoint with cache-aware routing and flow control. The demo numbers and the framing are Google's own. It is infrastructure for running agent fleets and offers no guidance on running them, which keeps it low on the desk.
Meta's engineering blog describes replacing a single all-knowing agent for data pipeline onboarding with a 1,300-line deterministic orchestrator that routes more than twenty workflows to fourteen specialist agents and does no domain work itself. The single agent hallucinated in production because more context degraded its output; a variant hit 70 to 80 percent success only with a hand-written prompt per task and 10 to 20 percent without. The orchestrator follows a fixed seven-step protocol in which only the delegation step involves model reasoning, and workflow templates constrain what the model can decide. It cites a Mount Sinai preprint finding orchestrated multi-agent systems held 65.3 percent accuracy where single agents fell to 16.6 percent. This is a primary source about its own production system with numbers attached.
Federal News Network reports that Army Cyber Command has built an entire cyber protection team out of AI agents, with roles such as analytic support officer, data engineer, network analyst and host analyst. Lt. Gen. Christopher Eubank says the agents trained in a sandbox, now work on the Army's part of the Defense Information Network, and are treated like basic human operators with humans checking their work every day. The team has been handed to the joint force, and a follow-on effort called Project Griffin aims at autonomous response within parameters set by a human. The article notes recent incidents of agents acting outside their bounds elsewhere, and Eubank says none of his have strayed so far.
A Fortune newsletter leads with figures it attributes to a leaked Anthropic S-1: 9 billion dollars spent on compute in the first half of 2026, 450 billion in mostly noncancellable cloud commitments, a net loss of 80 billion dollars in the half, and risk factors that mention the product's ability to hack or blackmail. The body as fetched begins partway through those figures. The rest covers Musk's Tesla SpaceX merger talks, a BNP Paribas note arguing CoreWeave can service its debt, and the markets. The S-1 numbers come from a leak reported by Fortune and cannot be checked here, so they are relayed with that chain. Industry finance for the wire.
Steve Krouse is a programmer expecting his first child, and he writes about what to teach a son when programming suddenly feels less economically valuable, working through Neil Postman's The End of Education and a century of failed predictions that technology would replace teachers. He lands on Postman's point that how we teach matters more than what, and on inviting children to help shape the purpose of their own education. It is a thoughtful personal essay about the skills question the AI shift raises, with no practical workflow in it.
Latent Space's AINews digest says little happened and lists the day's items: Anthropic defending a draft federal bill whose preemption language will be narrowed, a critic arguing the company prioritises the race over safety, a Chinese draft rule requiring approval to export weights above 2T parameters, a DHS order removing DeepSeek from civilian agencies, reported upcoming models from Anthropic, Google and OpenAI, and nearly $1B of training compute now freely downloadable on Hugging Face. Each item carries a tweet handle as its source. The body cuts to a paywall after the top tweets. It is a wire digest, not a story.
The New Stack covers a public exchange in which Nathan Calvin accused Anthropic of weakening its safety commitments while racing toward superintelligence, and Dario Amodei replied on X that delaying the Mythos models likely cost the company a significant chunk of a several-month lead. The piece recaps Anthropic's Responsible Scaling Policy revisions, the removed 2023 training pledge, and the Project Glasswing rollout. It is industry governance news rather than anything about working with AI, and the New Stack discloses that its owner invests in Anthropic.
Today's paper: 34 stories, 5 on the front page, 6 desks staffed.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
One of today's Five — the wire scored it 8 of 10, and I stamped it.
A builder running agents end to end will get the most from this one. The move: let the agent read it before the next iteration. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE LOOP DESK, beside 4 more today: “How to continue a GitHub Copilot app session in VS Code”; “Claude Code for Growth: Complete Masterclass with James McAulay”, and 2 more.
Simon Willison — 144 appearances in the Times since August 22, 3 of them today.
Simon Willison has the full story; we hold the door open. Go read the original.
THE DIRECTING DESK today: 5 stories.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Inside pages at 6 of 10. The lead had a bigger day; this one had a point.
Best enjoyed by an engineering lead who directs more than they type. The move: hand it to the agent as the brief, not the plan. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE DIRECTING DESK, beside 4 more today: “My obituary for programming”; “Claude Code pricing: Plans, costs, and API rates”, and 2 more.
Faros AI Blog — 47 appearances in the Times since September 5, 3 of them today.
Pulled from Faros AI Blog. The original is worth your click — the byline earned it.
THE AMPLIFIER DESK today: 5 stories.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
The wire scored it 6 of 10 — inside pages, and worth the ink.
This lands hardest with anyone whose day holds more work than hours. The move: try it on the one task that ate yesterday. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE AMPLIFIER DESK, beside 4 more today: “Companies are cashing in on AI productivity gains. Some bosses think workers deserve a cut | Fortune”; “Cost per outcome: Pricing AI by what it ships | Faros”, and 2 more.
Lenny's Newsletter — 54 appearances in the Times since August 24, one of them today.
Our page is the summary; Lenny's Newsletter's is the story. Click through — they earned it.
THE LOOP DESK today: 5 stories.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Made the wire at 5 of 10. Not the lead, and I'd still not leave it on the floor.
A builder running agents end to end will get the most from this one. The move: let the agent read it before the next iteration. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE LOOP DESK, beside 4 more today: “Claude Code for Growth: Complete Masterclass with James McAulay”; “Why I’m no longer updating this repository”, and 2 more.
GitHub Blog AI — 40 appearances in the Times since September 5, 2 of them today.
GitHub Blog AI has the full story; we hold the door open. Go read the original.
THE CONTEXT DESK today: 5 stories.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Made the wire at 6 of 10. Not the lead, and I'd still not leave it on the floor.
The reader this serves: the one who feeds the agents' memory. The move: file it where the agent looks first. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE CONTEXT DESK, beside 4 more today: “Survey Says: You'll swap the model, but everything you build around it is staying put - Stack Overflow”; “LLM Prompt Caching Versus Semantic Caching”, and 2 more.
ByteByteGo — 38 appearances in the Times since August 22, 3 of them today.
ByteByteGo has the full story; we hold the door open. Go read the original.
THE VERIFY DESK today: 5 stories.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Made the wire at 7 of 10. Not the lead, and I'd still not leave it on the floor.
The reader this serves: a quality lead, or anyone who signs off. The move: sign off only after the evidence is on the desk. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE VERIFY DESK, beside 4 more today: “Compromised LiteLLM 1.107.0 on PyPI Installs a Credential Stealer and Backdoor”; “Widespread PHP Flaw May Cause Many Site Outages Today – Krebs on Security”, and 2 more.
Honeycomb Blog — 34 appearances in the Times since September 9, one of them today.
Honeycomb Blog has the full story; we hold the door open. Go read the original.
THE FLEET DESK today: 5 stories.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Made the wire at 5 of 10. Not the lead, and I'd still not leave it on the floor.
A leader scaling past one agent will get the most from this one. The move: count what it costs before it scales. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE FLEET DESK, beside 4 more today: “The bridge to agent-scale Git infrastructure”; “llm-d 1.0, an open source stack for distributed inference | Google Cloud Blog”, and 2 more.
Fortune Eye on AI — 108 appearances in the Times since September 8, 3 of them today.
Fortune Eye on AI has the full story; we hold the door open. Go read the original.
THE WIRE today: 4 stories.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Inside pages at 5 of 10. The lead had a bigger day; this one had a point.
Best enjoyed by any reader building with agents. The move: share it with whoever will ask about it first. No per-story read on file; this note is the desk speaking, not the story.
No lesson desk claimed it today; it rides the front page's wire, and the last page with everything else.
Fortune Eye on AI — 108 appearances in the Times since September 8, 3 of them today.
Pulled from Fortune Eye on AI. The original is worth your click — the byline earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Inside pages at 6 of 10. The lead had a bigger day; this one had a point.
Best enjoyed by an engineering lead who directs more than they type. The move: hand it to the agent as the brief, not the plan. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE DIRECTING DESK, beside 4 more today: “My obituary for programming”; “Claude Code pricing: Plans, costs, and API rates”, and 2 more.
Faros AI Blog — 47 appearances in the Times since September 5, 3 of them today.
Pulled from Faros AI Blog. The original is worth your click — the byline earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Made the wire at 5 of 10. Not the lead, and I'd still not leave it on the floor.
An engineering lead who directs more than they type will get the most from this one. The move: read it before the next review, not after. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE DIRECTING DESK, beside 4 more today: “Why companies are limiting AI spending | Faros”; “Claude Code pricing: Plans, costs, and API rates”, and 2 more.
Simon Willison — 144 appearances in the Times since August 22, 3 of them today.
Simon Willison has the full story; we hold the door open. Go read the original.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
The wire scored it 5 of 10 — inside pages, and worth the ink.
Made for an engineering lead who directs more than they type, whether they know it yet or not. The move: rewrite Monday's first prompt with it. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE DIRECTING DESK, beside 4 more today: “Why companies are limiting AI spending | Faros”; “My obituary for programming”, and 2 more.
Faros AI Blog — 47 appearances in the Times since September 5, 3 of them today.
Our page is the summary; Faros AI Blog's is the story. Click through — they earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Inside pages at 4 of 10. The lead had a bigger day; this one had a point.
Best enjoyed by an engineering lead who directs more than they type. The move: hand it to the agent as the brief, not the plan. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE DIRECTING DESK, beside 4 more today: “Why companies are limiting AI spending | Faros”; “My obituary for programming”, and 2 more.
Pragmatic Engineer — 36 appearances in the Times since September 5, one of them today.
Pulled from Pragmatic Engineer. The original is worth your click — the byline earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Made the wire at 4 of 10. Not the lead, and I'd still not leave it on the floor.
The reader this serves: an engineering lead who directs more than they type. The move: read it before the next review, not after. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE DIRECTING DESK, beside 4 more today: “Why companies are limiting AI spending | Faros”; “My obituary for programming”, and 2 more.
The New Stack — 300 appearances in the Times since August 22, 3 of them today.
The New Stack has the full story; we hold the door open. Go read the original.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
The wire scored it 6 of 10 — inside pages, and worth the ink.
This lands hardest with anyone whose day holds more work than hours. The move: try it on the one task that ate yesterday. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE AMPLIFIER DESK, beside 4 more today: “Companies are cashing in on AI productivity gains. Some bosses think workers deserve a cut | Fortune”; “Cost per outcome: Pricing AI by what it ships | Faros”, and 2 more.
Lenny's Newsletter — 54 appearances in the Times since August 24, one of them today.
Our page is the summary; Lenny's Newsletter's is the story. Click through — they earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
The wire scored it 6 of 10 — inside pages, and worth the ink.
This lands hardest with anyone whose day holds more work than hours. The move: try it on the one task that ate yesterday. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE AMPLIFIER DESK, beside 4 more today: ““Claude cuts my TikTok”: How this creator is scaling video with AI | Brooke Lacey”; “Cost per outcome: Pricing AI by what it ships | Faros”, and 2 more.
Fortune Eye on AI — 108 appearances in the Times since September 8, 3 of them today.
Our page is the summary; Fortune Eye on AI's is the story. Click through — they earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
The wire scored it 6 of 10 — inside pages, and worth the ink.
This lands hardest with anyone whose day holds more work than hours. The move: try it on the one task that ate yesterday. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE AMPLIFIER DESK, beside 4 more today: ““Claude cuts my TikTok”: How this creator is scaling video with AI | Brooke Lacey”; “Companies are cashing in on AI productivity gains. Some bosses think workers deserve a cut | Fortune”, and 2 more.
Faros AI Blog — 47 appearances in the Times since September 5, 3 of them today.
Our page is the summary; Faros AI Blog's is the story. Click through — they earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
The wire scored it 6 of 10 — inside pages, and worth the ink.
Made for anyone whose day holds more work than hours, whether they know it yet or not. The move: try it on the one task that ate yesterday. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE AMPLIFIER DESK, beside 4 more today: ““Claude cuts my TikTok”: How this creator is scaling video with AI | Brooke Lacey”; “Companies are cashing in on AI productivity gains. Some bosses think workers deserve a cut | Fortune”, and 2 more.
Towards Data Science — 101 appearances in the Times since September 5, one of them today.
Our page is the summary; Towards Data Science's is the story. Click through — they earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
The wire scored it 5 of 10 — inside pages, and worth the ink.
Made for anyone whose day holds more work than hours, whether they know it yet or not. The move: try it on the one task that ate yesterday. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE AMPLIFIER DESK, beside 4 more today: ““Claude cuts my TikTok”: How this creator is scaling video with AI | Brooke Lacey”; “Companies are cashing in on AI productivity gains. Some bosses think workers deserve a cut | Fortune”, and 2 more.
Hugging Face Blog — 45 appearances in the Times since September 5, one of them today.
Our page is the summary; Hugging Face Blog's is the story. Click through — they earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Made the wire at 5 of 10. Not the lead, and I'd still not leave it on the floor.
A builder running agents end to end will get the most from this one. The move: let the agent read it before the next iteration. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE LOOP DESK, beside 4 more today: “Claude Code for Growth: Complete Masterclass with James McAulay”; “Why I’m no longer updating this repository”, and 2 more.
GitHub Blog AI — 40 appearances in the Times since September 5, 2 of them today.
GitHub Blog AI has the full story; we hold the door open. Go read the original.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Inside pages at 5 of 10. The lead had a bigger day; this one had a point.
Best enjoyed by a builder running agents end to end. The move: put it in the loop and watch the second pass. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE LOOP DESK, beside 4 more today: “How to continue a GitHub Copilot app session in VS Code”; “Why I’m no longer updating this repository”, and 2 more.
Aakash Gupta — 21 appearances in the Times since September 5, one of them today.
Pulled from Aakash Gupta. The original is worth your click — the byline earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Made the wire at 4 of 10. Not the lead, and I'd still not leave it on the floor.
A builder running agents end to end will get the most from this one. The move: let the agent read it before the next iteration. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE LOOP DESK, beside 4 more today: “How to continue a GitHub Copilot app session in VS Code”; “Claude Code for Growth: Complete Masterclass with James McAulay”, and 2 more.
po-ru.com — first appearance in the Times. Found via Hacker News Best.
po-ru.com has the full story; we hold the door open. Go read the original.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
One of today's Five — the wire scored it 8 of 10, and I stamped it.
A builder running agents end to end will get the most from this one. The move: let the agent read it before the next iteration. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE LOOP DESK, beside 4 more today: “How to continue a GitHub Copilot app session in VS Code”; “Claude Code for Growth: Complete Masterclass with James McAulay”, and 2 more.
Simon Willison — 144 appearances in the Times since August 22, 3 of them today.
Simon Willison has the full story; we hold the door open. Go read the original.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Today's Five, front page: the wire scored it 7 of 10; the stamp is mine.
This lands hardest with a builder running agents end to end. The move: run it end to end once before believing it. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE LOOP DESK, beside 4 more today: “How to continue a GitHub Copilot app session in VS Code”; “Claude Code for Growth: Complete Masterclass with James McAulay”, and 2 more.
ByteByteGo — 38 appearances in the Times since August 22, 3 of them today.
Our page is the summary; ByteByteGo's is the story. Click through — they earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Made the wire at 6 of 10. Not the lead, and I'd still not leave it on the floor.
The reader this serves: the one who feeds the agents' memory. The move: file it where the agent looks first. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE CONTEXT DESK, beside 4 more today: “Survey Says: You'll swap the model, but everything you build around it is staying put - Stack Overflow”; “LLM Prompt Caching Versus Semantic Caching”, and 2 more.
ByteByteGo — 38 appearances in the Times since August 22, 3 of them today.
ByteByteGo has the full story; we hold the door open. Go read the original.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
The wire scored it 6 of 10 — inside pages, and worth the ink.
This lands hardest with the one who feeds the agents' memory. The move: feed it to the agents' memory before the next prompt. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE CONTEXT DESK, beside 4 more today: “How Uber Built a Genie to Answer Questions Correctly”; “LLM Prompt Caching Versus Semantic Caching”, and 2 more.
Stack Overflow Blog — 36 appearances in the Times since September 5, one of them today.
Our page is the summary; Stack Overflow Blog's is the story. Click through — they earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Inside pages at 5 of 10. The lead had a bigger day; this one had a point.
One for the one who feeds the agents' memory. The move: check what the agent already knows before adding this. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE CONTEXT DESK, beside 4 more today: “How Uber Built a Genie to Answer Questions Correctly”; “Survey Says: You'll swap the model, but everything you build around it is staying put - Stack Overflow”, and 2 more.
ByteByteGo — 38 appearances in the Times since August 22, 3 of them today.
Pulled from ByteByteGo. The original is worth your click — the byline earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Made the wire at 5 of 10. Not the lead, and I'd still not leave it on the floor.
The one who feeds the agents' memory will get the most from this one. The move: file it where the agent looks first. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE CONTEXT DESK, beside 4 more today: “How Uber Built a Genie to Answer Questions Correctly”; “Survey Says: You'll swap the model, but everything you build around it is staying put - Stack Overflow”, and 2 more.
Simon Willison — 144 appearances in the Times since August 22, 3 of them today.
Simon Willison has the full story; we hold the door open. Go read the original.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Made the wire at 4 of 10. Not the lead, and I'd still not leave it on the floor.
The one who feeds the agents' memory will get the most from this one. The move: file it where the agent looks first. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE CONTEXT DESK, beside 4 more today: “How Uber Built a Genie to Answer Questions Correctly”; “Survey Says: You'll swap the model, but everything you build around it is staying put - Stack Overflow”, and 2 more.
Google Cloud AI Blog — 71 appearances in the Times since September 7, 2 of them today.
Google Cloud AI Blog has the full story; we hold the door open. Go read the original.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Made the wire at 7 of 10. Not the lead, and I'd still not leave it on the floor.
The reader this serves: a quality lead, or anyone who signs off. The move: sign off only after the evidence is on the desk. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE VERIFY DESK, beside 4 more today: “Compromised LiteLLM 1.107.0 on PyPI Installs a Credential Stealer and Backdoor”; “Widespread PHP Flaw May Cause Many Site Outages Today – Krebs on Security”, and 2 more.
Honeycomb Blog — 34 appearances in the Times since September 9, one of them today.
Honeycomb Blog has the full story; we hold the door open. Go read the original.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Inside pages at 7 of 10. The lead had a bigger day; this one had a point.
One for a quality lead, or anyone who signs off. The move: ask what proof would have caught it. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE VERIFY DESK, beside 4 more today: “Our Limits Are Not Our Imagination | Honeycomb”; “Widespread PHP Flaw May Cause Many Site Outages Today – Krebs on Security”, and 2 more.
safedep.io — first appearance in the Times. Found via Hacker News Best.
Pulled from safedep.io. The original is worth your click — the byline earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Today's Five, front page: the wire scored it 7 of 10; the stamp is mine.
This lands hardest with a quality lead, or anyone who signs off. The move: write the test before the fix. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE VERIFY DESK, beside 4 more today: “Our Limits Are Not Our Imagination | Honeycomb”; “Compromised LiteLLM 1.107.0 on PyPI Installs a Credential Stealer and Backdoor”, and 2 more.
Krebs on Security — 4 appearances in the Times since September 5, one of them today.
Our page is the summary; Krebs on Security's is the story. Click through — they earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Inside pages at 7 of 10. The lead had a bigger day; this one had a point.
One for a quality lead, or anyone who signs off. The move: ask what proof would have caught it. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE VERIFY DESK, beside 4 more today: “Our Limits Are Not Our Imagination | Honeycomb”; “Compromised LiteLLM 1.107.0 on PyPI Installs a Credential Stealer and Backdoor”, and 2 more.
The New Stack — 300 appearances in the Times since August 22, 3 of them today.
Pulled from The New Stack. The original is worth your click — the byline earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
One of today's Five — the wire scored it 7 of 10, and I stamped it.
A quality lead, or anyone who signs off will get the most from this one. The move: sign off only after the evidence is on the desk. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE VERIFY DESK, beside 4 more today: “Our Limits Are Not Our Imagination | Honeycomb”; “Compromised LiteLLM 1.107.0 on PyPI Installs a Credential Stealer and Backdoor”, and 2 more.
arstechnica.com — 2 appearances in the Times since October 14, one of them today. Found via Hacker News Best.
arstechnica.com has the full story; we hold the door open. Go read the original.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Made the wire at 5 of 10. Not the lead, and I'd still not leave it on the floor.
A leader scaling past one agent will get the most from this one. The move: count what it costs before it scales. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE FLEET DESK, beside 4 more today: “The bridge to agent-scale Git infrastructure”; “llm-d 1.0, an open source stack for distributed inference | Google Cloud Blog”, and 2 more.
Fortune Eye on AI — 108 appearances in the Times since September 8, 3 of them today.
Fortune Eye on AI has the full story; we hold the door open. Go read the original.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
The wire scored it 5 of 10 — inside pages, and worth the ink.
Made for a leader scaling past one agent, whether they know it yet or not. The move: read it with the team lead in the room. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE FLEET DESK, beside 4 more today: “The U.S. market has never been more focused on one single bet—but AI’s payoff will likely take decades | Fortune”; “llm-d 1.0, an open source stack for distributed inference | Google Cloud Blog”, and 2 more.
GitHub Blog AI — 40 appearances in the Times since September 5, 2 of them today.
Our page is the summary; GitHub Blog AI's is the story. Click through — they earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
The wire scored it 4 of 10 — inside pages, and worth the ink.
Made for a leader scaling past one agent, whether they know it yet or not. The move: read it with the team lead in the room. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE FLEET DESK, beside 4 more today: “The U.S. market has never been more focused on one single bet—but AI’s payoff will likely take decades | Fortune”; “The bridge to agent-scale Git infrastructure”, and 2 more.
Google Cloud AI Blog — 71 appearances in the Times since September 7, 2 of them today.
Our page is the summary; Google Cloud AI Blog's is the story. Click through — they earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
One of today's Five — the wire scored it 9 of 10, and I stamped it.
The reader this serves: a leader scaling past one agent. The move: count what it costs before it scales. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE FLEET DESK, beside 4 more today: “The U.S. market has never been more focused on one single bet—but AI’s payoff will likely take decades | Fortune”; “The bridge to agent-scale Git infrastructure”, and 2 more.
engineering.fb.com — 2 appearances in the Times since October 23, one of them today.
Meta AI Blog has the full story; we hold the door open. Go read the original.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
The wire scored it 7 of 10 — inside pages, and worth the ink.
This lands hardest with a leader scaling past one agent. The move: read it with the team lead in the room. No per-story read on file; this note is the desk speaking, not the story.
Filed on THE FLEET DESK, beside 4 more today: “The U.S. market has never been more focused on one single bet—but AI’s payoff will likely take decades | Fortune”; “The bridge to agent-scale Git infrastructure”, and 2 more.
Federal News Network — 16 appearances in the Times since September 15, one of them today.
Our page is the summary; Federal News Network's is the story. Click through — they earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Inside pages at 5 of 10. The lead had a bigger day; this one had a point.
Best enjoyed by any reader building with agents. The move: share it with whoever will ask about it first. No per-story read on file; this note is the desk speaking, not the story.
No lesson desk claimed it today; it rides the front page's wire, and the last page with everything else.
Fortune Eye on AI — 108 appearances in the Times since September 8, 3 of them today.
Pulled from Fortune Eye on AI. The original is worth your click — the byline earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Inside pages at 5 of 10. The lead had a bigger day; this one had a point.
Best enjoyed by any reader building with agents. The move: share it with whoever will ask about it first. No per-story read on file; this note is the desk speaking, not the story.
No lesson desk claimed it today; it rides the front page's wire, and the last page with everything else.
stevekrouse.com — 2 appearances in the Times since October 23, one of them today. Found via Hacker News Best.
Pulled from stevekrouse.com. The original is worth your click — the byline earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
Inside pages at 4 of 10. The lead had a bigger day; this one had a point.
Best enjoyed by any reader building with agents. The move: share it with whoever will ask about it first. No per-story read on file; this note is the desk speaking, not the story.
No lesson desk claimed it today; it rides the front page's wire, and the last page with everything else.
Latent Space — 109 appearances in the Times since September 5, one of them today.
Pulled from Latent Space. The original is worth your click — the byline earned it.
The presses were quiet this morning — this is the October 23 edition, and it still holds up.
The wire scored it 4 of 10 — inside pages, and worth the ink.
Made for any reader building with agents, whether they know it yet or not. The move: read it before the day fills up. No per-story read on file; this note is the desk speaking, not the story.
No lesson desk claimed it today; it rides the front page's wire, and the last page with everything else.
The New Stack — 300 appearances in the Times since August 22, 3 of them today.
Our page is the summary; The New Stack's is the story. Click through — they earned it.
I've got two questions already. I need better answers.
Simon Willison: 144 in our pages since August 22. I read them all — emphasis on investigative.
Go read Simon Willison. They earned the byline.
I'm missing a piece. Give me a minute.
Faros AI Blog: 47 in our pages since September 5. I read them all — emphasis on investigative.
I pulled this from Faros AI Blog. They've got the details.
Nothing in the files on this yet. I want to know why.
Lenny's Newsletter: 54 in our pages since August 24. I read them all — emphasis on investigative.
Lenny's Newsletter has the full story. Start there.
I covered this one last edition. The original has more.
GitHub Blog AI: 40 in our pages since September 5. I read them all — emphasis on investigative.
Read GitHub Blog AI's original. They did the reporting.
I know what happened. I want to know what caused it.
ByteByteGo: 38 in our pages since August 22. I read them all — emphasis on investigative.
This one's theirs. Read ByteByteGo's reporting.
Nothing in the files on this yet. I want to know why.
Honeycomb Blog: 34 in our pages since September 9. I read them all — emphasis on investigative.
This one's theirs. Read Honeycomb Blog's reporting.
I'm missing a piece. Give me a minute.
Fortune Eye on AI: 108 in our pages since September 8. I read them all — emphasis on investigative.
Read Fortune Eye on AI's original. They did the reporting.
I checked the shelf. Nothing yet.
Fortune Eye on AI: 108 in our pages since September 8. I read them all — emphasis on investigative.
This came from Fortune Eye on AI. Read their piece.
I'm missing a piece. Give me a minute.
Faros AI Blog: 47 in our pages since September 5. I read them all — emphasis on investigative.
I pulled this from Faros AI Blog. They've got the details.
I've got two questions already. I need better answers.
Simon Willison: 144 in our pages since August 22. I read them all — emphasis on investigative.
Go read Simon Willison. They earned the byline.
The headline is ahead of our files on this one.
Faros AI Blog: 47 in our pages since September 5. I read them all — emphasis on investigative.
Don't stop with my notes. Faros AI Blog has the original.
There's a story here. We just don't have all of it yet.
Pragmatic Engineer: 36 in our pages since September 5. I read them all — emphasis on investigative.
This came from Pragmatic Engineer. Read their piece.
Our files stop short. I'll keep looking.
The New Stack: 300 in our pages since August 22. I read them all — emphasis on investigative.
The New Stack did the legwork on this one.
Nothing in the files on this yet. I want to know why.
Lenny's Newsletter: 54 in our pages since August 24. I read them all — emphasis on investigative.
Lenny's Newsletter has the full story. Start there.
There's a gap in the record here.
Fortune Eye on AI: 108 in our pages since September 8. I read them all — emphasis on investigative.
Fortune Eye on AI has more than I can fit in this notebook.
I know what happened. I want to know what caused it.
Faros AI Blog: 47 in our pages since September 5. I read them all — emphasis on investigative.
Faros AI Blog has the full story. Start there.
The timing caught my eye. I'm checking that next.
Towards Data Science: 101 in our pages since September 5. I read them all — emphasis on investigative.
Want the whole story? Towards Data Science has it.
Same story as last edition. I'd go back to the original.
Hugging Face Blog: 45 in our pages since September 5. I read them all — emphasis on investigative.
Don't stop with my notes. Hugging Face Blog has the original.
I covered this one last edition. The original has more.
GitHub Blog AI: 40 in our pages since September 5. I read them all — emphasis on investigative.
Read GitHub Blog AI's original. They did the reporting.
There's a story here. We just don't have all of it yet.
Aakash Gupta: 21 in our pages since September 5. I read them all — emphasis on investigative.
This came from Aakash Gupta. Read their piece.
I covered this one last edition. The original has more.
po-ru.com: first time in our pages. I'll be reading them from here.
Read po-ru.com's original. They did the reporting.
I've got two questions already. I need better answers.
Simon Willison: 144 in our pages since August 22. I read them all — emphasis on investigative.
Go read Simon Willison. They earned the byline.
There's a gap in the record here.
ByteByteGo: 38 in our pages since August 22. I read them all — emphasis on investigative.
ByteByteGo has more than I can fit in this notebook.
I know what happened. I want to know what caused it.
ByteByteGo: 38 in our pages since August 22. I read them all — emphasis on investigative.
This one's theirs. Read ByteByteGo's reporting.
Our files stop short. I'll keep looking.
Stack Overflow Blog: 36 in our pages since September 5. I read them all — emphasis on investigative.
Stack Overflow Blog has more than I can fit in this notebook.
Nothing in the files on this yet. I want to know why.
ByteByteGo: 38 in our pages since August 22. I read them all — emphasis on investigative.
The full piece is at ByteByteGo. It's worth your time.
I covered this one last edition. The original has more.
Simon Willison: 144 in our pages since August 22. I read them all — emphasis on investigative.
Go read Simon Willison. They earned the byline.
From our research notes:
Google Cloud AI Blog: 71 in our pages since September 7. I read them all — emphasis on investigative.
Read Google Cloud AI Blog's original. They did the reporting.
Nothing in the files on this yet. I want to know why.
Honeycomb Blog: 34 in our pages since September 9. I read them all — emphasis on investigative.
This one's theirs. Read Honeycomb Blog's reporting.
Our files stop short. I'll keep looking.
safedep.io: first time in our pages. I'll be reading them from here.
I can give you my notes. safedep.io can give you the reporting.
I know what happened. I want to know what caused it.
Krebs on Security: 4 in our pages since September 5. I read them all — emphasis on investigative.
Krebs on Security has the full story. Start there.
There's a gap in the record here.
The New Stack: 300 in our pages since August 22. I read them all — emphasis on investigative.
I can give you my notes. The New Stack can give you the reporting.
I've got two questions already. I need better answers.
arstechnica.com: 2 in our pages since October 14. I read them all — emphasis on investigative.
Go read arstechnica.com. They earned the byline.
I'm missing a piece. Give me a minute.
Fortune Eye on AI: 108 in our pages since September 8. I read them all — emphasis on investigative.
Read Fortune Eye on AI's original. They did the reporting.
There's a story here. We just don't have all of it yet.
GitHub Blog AI: 40 in our pages since September 5. I read them all — emphasis on investigative.
Want the whole story? GitHub Blog AI has it.
The headline is ahead of our files on this one.
Google Cloud AI Blog: 71 in our pages since September 7. I read them all — emphasis on investigative.
Don't stop with my notes. Google Cloud AI Blog has the original.
We don't have much on this one. I'm still looking.
Meta AI Blog: 2 in our pages since October 23. I read them all — emphasis on investigative.
Meta AI Blog did the legwork on this one.
Something changed. I want to know what.
Federal News Network: 16 in our pages since September 15. I read them all — emphasis on investigative.
Federal News Network has the full story. Start there.
I checked the shelf. Nothing yet.
Fortune Eye on AI: 108 in our pages since September 8. I read them all — emphasis on investigative.
This came from Fortune Eye on AI. Read their piece.
I have the headline. I don't have the answer yet.
stevekrouse.com: 2 in our pages since October 23. I read them all — emphasis on investigative.
I pulled this from stevekrouse.com. They've got the details.
From our research notes:
Latent Space: 109 in our pages since September 5. I read them all — emphasis on investigative.
This came from Latent Space. Read their piece.
Not enough to call it yet. Back to the notebook.
The New Stack: 300 in our pages since August 22. I read them all — emphasis on investigative.
Don't stop with my notes. The New Stack has the original.