Skip to content

root / tags / diff

#diff

2 fiches

Architecture & Construction Machine translation

Projects in Buzz

Product announcement post from **Block Engineering** signed by **Thomas Petersen** (*Principal Designer & Builder*), published on **August 18, 2026**, ~1,800 words across thirteen short sections, introducing **Buzz Projects** — a **software forge hosted on its own relay**: Git repositories, branches, pull requests, issues, review and merge, multi-repo projects, an activity feed, all linked to conversation channels. The post's standfirst and thesis: *« Coding agents are the terminal for your computer. Buzz is the terminal for your network. »* Three contributions. **(A) A trust doctrine grounded in *ex post* proof rather than *ex ante* authorization**: on one side *« No forced guardrails, no limitations on what your agents are allowed to help you with »*, on the other *« Every push, review, approval, and merge is a signed Nostr event. If an agent authors a patch, you can see which agent produced it and which human authorized that agent to act »*; the section closes on a stated direction — *« we are already exploring ideas around agent trust protocols informed by past behavior »*. **(B) Git interoperability without proprietary tooling**: *« These are standard git repositories… You can fetch, clone, pull, and push over plain Smart HTTP, with no custom tooling or wrapper CLI required »*, with the clé Nostr serving as a single identity — *« The same npub that signs your messages signs your pushes. »* **(C) A distinction between execution surface and network presence**: *« A terminal gives an agent somewhere to execute commands and change files, but it does not give it a persistent place in the network. Buzz does. »* The post produces no figures and contains no outbound links; it qualifies itself as preliminary six times (*« still very basic »*, *« fairly elementary »*, *« still under experiments »*), and Projects lives under the **Experiments** tab of Buzz Desktop.

#Buzz#Buzz Projects#Block

**Thomas Petersen** — *« Principal Designer & Builder »* chez **Block** · auteur unique et signataire du billet ; première apparition dans le corpus. Publié le **18 août 2026** sur le blog **Block Engineering**. Troisième signature Block sur Buzz en un mois · après Tyler Longwell (21 juillet) et Atish Patel (6 août) · et la première non-ingénieur.

Quality & Security Auto-verified translation

What are code reviews even for?

Issue of the **Engineering Enablement** newsletter from **DX** signed by **Brian Houck**, published on **August 5, 2026**, approximately **13,000 characters**. The text opens with a quantified observation: at **Meta**, significant lines per diff merged by a human increased by **106%** in one year and diffs per developer per month by **51%**, with more than **80%** of this growth coming from agentic AI, while the share of diffs reviewed within 24 hours declines; DX's analysis for its part measures a median pull request size up **64%**, while developers want to devote about **7%** of their time to review. (A) Before handing review over to AI, Houck reframes the usage question: *"What problem was code review solving before AI arrived?"* If the answer is defect detection, full automation becomes inevitable; the **Bacchelli & Bird** study (*Modern Code Review*, ICSE 2013) shows that defect-related comments account for only **14%** of comments actually written. (B) Part of the burden is *self-inflicted*: the 2016 Microsoft study of **911 developers** already identified turnaround time, review size, and understanding the motivation for the change as the top three obstacles, and only **26%** still wrote a detailed description. (1) **RADAR** at Meta serves as the reference deployment for risk stratification. (2) Three ordered moves: fix the fundamentals, design AI around human judgment, protect what review invisibly produces. The corpus already includes [[monperrus-end-of-code-review-agents-supersede-2026-06-11]], which pushes automation to the point of replacement, and [[laycock-thoughtworks-reviewing-all-this-code-2026-09-02]], the direct response to this text.

#code review#code review#review queue

Brian Houck · signataire de l'édition · sur la newsletter Engineering Enablement de DX ; fonction non affichée par la page.