Analytical tech-watch notes on AI, coding agents and the evolution of the software development lifecycle (SDLC) — a public, agent-readable knowledge base.
Essay published on **Gates Notes** on **August 26, 2026** by **Bill Gates**, co-founder of **Microsoft** and chairman of the **Gates Foundation**, ~4,500 words, announced as the first in a series. The text poses an alternative — AI will be the greatest equalizer ever invented, or the worst source of injustice — and a finding: no plan exists for entering this period. **(A) Three risks**: the lasting disappearance of entry- and mid-career jobs, white-collar as much as blue-collar, within a decade rather than several generations, because this time the substitution targets **cognition**; the weaponization of malicious actors (cyberattacks, bioterrorism, fraud, deepfakes), coupled with a concentration of power among those who already hold it; the effect of compagnons IA on children's development and on critical thinking. **(B) The benefits**, located in five domains — research, health, agriculture in low-income countries (the impact the author calls the fastest), public services, education — with a reservation carried on the verb: *"the operative word is 'can'"*. **(C) Three proposals** open the series: building an unprecedented national and international institutional framework, borrowing from the nuclear inspection regime, aviation regulation, and ozone agreements; reserving certain occupations for humans, a domain named **Human Reserved**; **taxing AI tokens and robots** to rebalance the taxation of labor and capital. Gates discloses his financial ties to the industry and the transfer of his profits to the foundation. The text extends executive essays on the distribution of AI's value — [[nadella-frontier-ecosystem-human-token-capital-2026-06-12]], [[zuckerberg-meta-future-is-for-everyone-superintelligence-2026-08-10]] — by focusing on public power rather than the firm.
#AI and equity#transition to the AI era#cognition substitution#job disappearance#entry-level jobs
Bill Gates — cofondateur de Microsoft · président du conseil de la Gates Foundation. Blog personnel Gates Notes. Page non capturable par `curl | lynx` (403 Akamai) : extraction navigateur.
Guest post by **Andy Warfield**, an engineer on the **S3** team at **AWS**, published on **August 26, 2026** on *All Things Distributed*, **Werner Vogels**'s blog, who introduces it in a few lines signed "--W": **3,554 words** per the page. The text serves as the vehicle for the announcement that **DuckLabs**, the team behind **DuckDB**, is joining **AWS**. (A) The thesis: systems computing is about seeking the elegant trade-off against a moving "physics" — the ratios between memory speed, network, and compute — and that physics has changed. Warfield quantifies the gap: an **m1.xlarge** from 2007 offered **15 GB of RAM**, **4 virtual cores**, and **~1 Gb/s** of network; an **m8g.48xlarge** today offers roughly **50×** more of each of the three. Dataset growth, meanwhile, follows a distribution whose tail consists of very large volumes. (B) The consequence: distributed processing — **MapReduce**, **Spark**'s **RDDs** — was designed under the I/O constraints of the early 2000s, and much of the work assigned to it no longer needs to leave the application. Hence the embedded, in-process library engine, running in the application's address space, of which **DuckDB** is the example. Warfield anchors this in the *Scalability! But at what COST?* paper (2015) and **Paul Barham**'s epigraph: "You can have a second computer once you've shown you know how to use the first one." He states an explicit caveat: "When a job genuinely needs a thousand machines, it needs a thousand machines." The corpus already holds [[vogels-tech-predictions-2026-allthingsdistributed-2025-11-25]] from the same blog and [[anthropic-self-service-data-analytics-claude-agentic-stack-2026-06-03]] on self-service analytics.
#DuckDB#DuckLabs#AWS acquisition
Andy Warfield · ingénieur du service S3 chez AWS · en billet invité sur *All Things Distributed* ; introduction de Werner Vogels · CTO d'Amazon.
Essay by **Bill Staples**, CEO of **GitLab**, published on **August 24, 2026** on the about.gitlab.com blog: an announced **31-minute** read, roughly **39,000 characters**, presented as the sequel to a memo written to the board of directors in January 2026 and partially published in May under the title *GitLab Act 2*. The text presents itself as a response to **Anthropic**'s AI-native SDLC playbook, published three days earlier, from which it borrows the opening line — "Code is no longer the bottleneck" — to pose the question that drives it: what becomes scarce when code becomes abundant. (A) The economic diagnosis: the useful unit is not cost per line but **cost per accepted change**, which aggregates generation, environment, context, verification, review, remediation, and governance; AI collapses the generation term alone, which makes the others proportionally heavier — an organization ten times faster at generating "will simply move the queue." (B) The architectural response: four capabilities — agent platform, machine-scale execution, durable context, governance — forming an enterprise layer that outlives the model, "The model should be replaceable. The agent should belong to the customer." (1) Three modes coexist durably, from human-driven legacy to autonomous development, against the idea of a single maturity curve. (2) The CI/CD pipeline becomes the place where the inner loop runs, instead of being an end-of-line gate. The figures cited are Stripe's, Spotify's, and Amplitude's; GitLab produces only one, about its own source control. The corpus already holds [[claxton-anthropic-ai-native-sdlc-playbook-2026-08-21]], the source this text responds to, and [[sfeir-sdlc-pdlc-articulation-2026-07-22]] on the SDLC/PDLC articulation that Staples adopts as his own.
#code abundance#cost per accepted change#theory of constraints
Bill Staples · directeur général de GitLab (fonction non affichée par la page) · sur le blog about.gitlab.com.
Long-form guide from **Anthropic** by **Louis Claxton** (Applied AI team), published on **August 21, 2026** on the claude.com blog: a stated **40-minute** read, roughly **64,000 characters**, presented as a collection of *plays* drawn from the team's work with its clients. (A) The diagnosis: with code no longer the bottleneck, it shifts to the stages on either side of the build (plan, review/test, deploy), line-by-line controls stop holding once the agent writes most of the diff, and governance cost rises as exceptions still route through periodic committees. (B) The response: six stages (Plan, Design, Build, Test, Deploy, Maintain) organized as a **loop** rather than a chain, each ending with a **committed artifact** that the next stage reads — `intent.md`, `spec.md`, `plan.md`, the diff and its tests, the PR and its findings, the incident record. (1) Institutional knowledge becomes versioned files: `CLAUDE.md`, skills, `REVIEW.md`, `bands.yaml`. (2) Governance splits into two layers, with the skill positioned as an advisory control and the hook as the deterministic layer behind it. Separation of duties is set as an invariant — the agent that writes the code cannot approve it — and the piece closes on *"The loop keeps running. Human judgement stays above it."* The corpus already holds [[clinton-anthropic-secure-ai-native-sdlc-2026-07-21]] on the security side of the same cycle, and [[hingel-augment-how-ai-changes-sdlc-six-stages-2026-06-08]] on the same six-stage breakdown as seen by a competitor.
#AI-native SDLC#software development lifecycle#plays
Louis Claxton (Anthropic, équipe Applied AI) · sur le blog claude.com ; contributions créditées à Jim Blackhurst · Will Steuk et Jamal Arif.
Guide signed by **Michael Segner**, published on **August 20, 2026** on the claude.com blog in the *Claude Code* category: a **5-minute** read announced for approximately **31,500 characters** of body text, also offered as a PDF. Stated material: interviews with **more than a dozen** startups, fifteen named — **Artemis Security**, **Cainex**, **Clay**, **ClickHouse**, **Cognition**, **Commure**, **Crosby**, **Emergent**, **Harvey**, **Heidi**, **Higgsfield**, **Omni**, **Parahelp**, **Translucent**, **Zingage**. (A) Five operating rules: *everyone ships*, *automate the tedium*, *trust, but verify*, *build for rebuilding*, *prototype, dogfood, productionize*, each closed with product tips and gathered into a final checklist. (B) A body made of attributed quotes, each rule illustrated by named executives rather than by an aggregated metric. The four figures highlighted are those of the interviewed companies: **+30%** more features shipped (ClickHouse), **2 to 3×** engineering productivity (Omni), **100%** of bug triage automated (Clay), **more than 6,000 PRs per week** (Artemis Security). Two passages depart from the testimonial register: **Cainex**'s self-correction loop on medical coding, described step by step, and the internal use of **Claude Tag** at **Anthropic** as first responder for CI/CD on-call. The question posed at the opening — *"what would it look like if an organization built their product development lifecycle with Claude Code from the ground up?"* — connects with [[claxton-anthropic-ai-native-sdlc-playbook-2026-08-21]], published the next day by the same publisher, and extends [[cherny-wu-reflecting-year-claude-code-2026-07-17]].
#Claude Code#startups#everyone ships
Michael Segner · auteur du guide sur le blog claude.com (fonction non affichée par la page) ; entretiens avec les dirigeants de quinze entreprises nommées.
Corporate blog post from **Block** (`block.xyz/inside`), unsigned — the displayed author is **"Block"** —, published on **August 18, 2026**, ~930 words, announcing **the open-sourcing of Berd**, Block's internal desktop application for working with agents, and laying out the design thesis that guided it: giving agents character *"not only through roles, instructions, skills, and tools, but through distinctive visual identities"* — hence the in-house animated characters, the *"Gloopies"*. The post starts from an observation of fragmentation (*"The technology was powerful, but the experience around it was fragmented"*) and a precisely named interface problem: *"the product gives people little sense of how the agent is configured, which context and tools are available to it, and how it differs from another agent"*. Two structuring contributions. **(A) A three-tier articulation**: **goose** remains the framework and *runtime* that holds the agent loop; **Berd** is the desktop client (projects, context, sessions, agents, configuration); the two communicate via the **Agent Client Protocol**. **Buzz** is designated as the follow-up, for when solo work becomes collaborative (*"Start alone, then go multiplayer"*). **(B) Six requirements handed off to Buzz**, stated as a takeaway: *"private space, durable context, recognizable agent identities, reusable skills, visible configuration, and clearer visibility into an agent's configured context, tools, and capabilities"* — a grid directly reusable for evaluating an agent client. The text itself distinguishes identity from capability: *"The avatars make the agent recognizable. Its role, skills, and tools make it useful."* No usage figures are produced and no license is named for the open-sourcing.
#Berd#Block#open source
**Aucun auteur nommé** : le billet est signé **« Block »** — le champ *Author* de la page porte le nom de l'entreprise. Publié le **18 août 2026** sur `block.xyz/inside` · le blog **corporate** · et non sur `engineering.block.xyz`.
Blog post from **Sonatype** by **Aaron Linskens** (*technical writer*), published on **August 18, 2026**, ~1,300 words: it recounts a **Sonatype Research Labs** study spanning **49 months** (June 2022 — June 2026) and a **fixed cohort** of enterprise applications, a methodological choice asserted to isolate the evolution of the application fleet rather than that of the customer portfolio. The result is presented as a contradiction: remediation is faster, yet risk accumulates further. (A) **The stock is rising** — *Critical* and *High* vulnerabilities per application **×4.31** (from **14.14** in June 2022 to **54.3** in 2026, still **×3.91** excluding legacy applications newly brought under management), newly affected component versions at **46×** the pre-AI rate, monthly application creation **×4.84**. (B) **Remediation is improving** — more than half of resolved violations are resolved in under a day, the median age of unresolved *Critical/High* vulnerabilities drops from **228** to **126 days**, then to **103** in May 2026; among cohorts that had twelve months, **52.6%** are resolved, **44.3%** open, **3.1%** under waiver. (C) **The proposed lever is component selection**: at the moment a vulnerable dependency was chosen, a substantially less risky version already existed in **62.2%** of cases on **Maven**, **46.9%** on **npm**, **34.3%** on **PyPI** — a gap the text attributes to an information gap rather than developer fault. The post itself states that AI is not the sole cause of the acceleration, and concludes on **Sonatype Guide**, which brings this intelligence to the point of selection. On the supply-chain side, it extends what [[fiches/2026-08/staples-gitlab-when-code-is-abundant-2026-08-24]] frames in economic terms and [[fiches/2026-07/clinton-anthropic-secure-ai-native-sdlc-2026-07-21]] in secure-cycle terms.
#software supply chain#software supply chain#Sonatype Research Labs
Aaron Linskens · *technical writer* chez Sonatype · sur le blog de l'éditeur ; les chiffres sont produits par Sonatype Research Labs · non par l'auteur.