Post from the **Dropbox Tech blog** (*culture* section), published on **May 28, 2026** by **Kazuaki Okumura** (Dropbox, role unspecified in the article), recapping a talk at the **DX Annual 2026** conference (developer productivity). **Pivot thesis**: engineering productivity must move beyond *code generation*. *« Accelerating code generation simply shifted some bottlenecks downstream »* — AI has massively increased code throughput, but *« the faster code moves, the more pressure it puts on review queues, CI systems, validation workflows, release coordination, and production operations »*. The real challenge is no longer writing code faster, but enabling the entire SDLC to **absorb, validate, and ship safely** a much larger volume. **From copilot to agent**: the first wave (code explanation, snippets, Q&A) operated *« as copilots alongside the engineer »*; the agent, by contrast, *« can take a scoped task, inspect the codebase, edit files, run tests, iterate on failures, and return an artifact for human review »* — with the engineer remaining *« accountable for intent, architecture, quality, and release decisions »* (more parallel work, more options, offloading repetitive execution). **Nova** = Dropbox's **internal** coding-agent platform: describe a task in natural language, execution in a controlled environment with codebase context. Canonical datapoint: ***« Nova's value comes less from the model itself than the systems surrounding it »*** (codebase context, internal practices, safe execution, workflow integration, human review); Nova accounts for **~1 in 12 PRs at Dropbox** today (adoption growing), and extends beyond features to **migrations, flaky-test remediation, bug investigation, dependency updates** (high-toil work). **Measuring product velocity, not code output**: *PR throughput*, a useful signal when coding velocity was the constraint, *« was no longer sufficient »*. A **4-stage** measurement model: ***Fuel*** (are AI tools being used?) → ***Adoption*** (how workflows are changing across teams) → ***Output*** (is AI contributing to production work?) → ***Impact*** (*« improving product velocity and reducing the time it takes to move from idea to customer value »*). Quality signals tracked: **code review turnaround time, first-run test pass rate, defect ratio, rework rate**. *« Quality and trust matter as much as speed »* — the core of the shift: *« moving from local activity metrics toward broader system outcomes »*. **Workflows have to evolve too**: this is *« not just a tooling shift »* but a change of **operating model** — the engineer's role shifts toward *« defining intent, mapping problems, reviewing generated changes, and making higher-context architectural and quality decisions »*. **Enablement** is as crucial as the tool itself (hands-on learning, hackathons, workflow spotlights, bootcamps, peer-led examples); adoption proceeds at varying speeds across teams; *« The goal is not to force every workflow through an agent »* — the goal is to make it *« useful, safe, measurable, and repeatable where it creates meaningful leverage »*. **What we learned**: ***« AI doesn't eliminate bottlenecks in software development, but it does move them »*** (downstream: review, validation, testing, release, prod ops) → optimizing the old bottleneck no longer creates the same leverage. *« The advantage will not come from access to the same foundation models everyone else can use. It will come from the systems built around those models: context, internal tooling, quality controls, and the workflows that connect them together. »* Pressure also builds **upstream** (product & design): structured specs, design clarity, sharper problem framing. Closing: ***« The future of engineering productivity will not be defined solely by who has the best models. It will be defined by who builds the best systems around them »***; *« The real challenge is no longer just generating more code, but building engineering systems that can reliably turn AI-assisted output into valuable experiences for our customers »*. Direct convergence with **Salesforce/Tallapragada** (Effective Output: measuring value, not volume; no speed/quality tradeoff), **Gupta** (token-to-outcome attribution, cost of a completed outcome), **DORA** (beyond throughput), and the shift of the KPI toward **system outcome** (idea→customer value).
**Kazuaki Okumura** — Dropbox (rôle non précisé dans l'article ; le billet reprend une intervention présentée à la conférence **DX Annual 2026** sur la productivité développeur, ce qui suggère un profil engineering leadership / platform, sans confirmation). Publié sur le **Dropbox Tech blog** (dropbox.tech) · rubrique *culture* · le **28 mai 2026**.
Viral X thread (**230.5K views**, May 28, 2026, 1:51 AM) by **Jaya Gupta** (@JayaGup10, investor — likely Foundation Capital, author of the *Context Graphs* framework) titled ***"Token Budget Wars"***. **Pivot thesis**: ***"Enterprise AI has moved from adoption to allocation"*** — phase 1 of enterprise AI proved that models can work; phase 2 will decide **how much of that work is worth it**. The new currency at the top of the enterprise is the **ability to quantify AI ROI**: *"show me the value"*. Canonical concept: ***marginal token utility*** = *"the business value created by each additional dollar of inference"* — the number that matters at scale, and that **most companies cannot see**. Timeline: **Claude shipped November 2025**, after the 2026 annual budgets were locked → as early as **Q1**, companies *"running multiples ahead of plan"* → inference stops being an experimentation line item and becomes a **recurring operating cost**. Shift from **experimentation (a few $100K) → infrastructure (seven figures, $1M+)**: at infrastructure scale, **technical variance produces material P&L swings — two runs of the same workflow on the same input can differ by 5-10× in token cost** with nothing visibly broken, *"a number the CFO has to explain to the CEO"*. **AI competes with labor**: 3 types of budget requests (replace outsourced work / replace internal work / generate revenue) → shift toward the ***cost of a completed outcome*** (cost per resolved ticket, processed claim, reviewed contract, completed invoice, avoided hire, retained customer, dollar of revenue moved). **BPO = the easiest baseline to benchmark against** (already priced in completed units); internal work is much harder (multi-skilled employees, diffuse gains, HR resistance to headcount reduction). **Why it's different from SaaS**: SaaS learned to treat usage as a proxy for value; AI breaks that proxy — *"the signal and the noise share the same unit"* (the token), *"SaaS usage told you the software had been adopted. AI usage tells you the meter is running. It doesn't tell you whether your company is cooking."* **Three causes of marginal token utility's invisibility**: (1) ***retry tails*** — tokens per resolved workflow ≈ **T/p**; going from 90% to 70% completion increases effective cost by ~**28%**, not 20%, because failures compound; (2) ***context inflation*** — inference cost ≈ **O(n²)** in context length (attention), doubling the context **quadruples** reasoning cost (over-retrieval: 50 docs when 5 would do); (3) ***routing*** — by default the most powerful model is used (basic classification run on a complex reasoning model); across millions of calls, the difference between routing easy tasks to a small model and sending everything to the frontier model = *"the difference between a manageable bill and a board-level problem."* **Sector split**: **software** companies = a **productivity measurement** problem (already instrumented: PRs, commits, deploys, incidents, cycle time, MTTR — tracks *"AI layoffs"*); **non-software** companies = a **transformation** problem (operational work: claims, underwriting, support, compliance reviews, supply chain exceptions, payment disputes — *right under audit, not just right on average*). **The missing layer = token-to-outcome attribution**: a conversion layer linking inference spend → work performed → business outcome, answering 3 questions (real cost including retries/corrections; which parts of the trace mattered vs. thrashing; did the work change the operating model). ***Measurement becomes memory***: linking a token to an outcome requires capturing **decision traces** (what the agent saw, retrieved, called, ignored, where it retried, when a human overrode it) — *"decision rationale is one of the most perishable assets in a company"* (lives in Slack, emails, escalation calls, people's heads). Agents **create** these traces; captured first to justify the spend, they become *"more valuable than the cost report"* → a **context graph** (*"although I am so tired of that word these days"*). **The allocation layer is the prize**: whoever owns token-to-outcome attribution makes the **allocation calls** (which workflows deserve more compute, which are capped, which move to cheaper models, which stay human, which replace BPO). Companies won't do this on their own — they'll **buy it as a transformation** (Fortune 500 playbook: McKinsey + Palantir alumni + top-down CEO, in the manner of ERP/BI/digital transformation, a *"program"* with an executive sponsor and infrastructure that becomes the **new source of truth**). Framed by **Charlie Munger**: *"show me the incentive and I will show you the outcome."* Organizational sub-thesis: the decades-old executive instinct that *big teams = big jobs/scope/power* → once intelligence becomes the **scarce resource**, the new marker is *"how much of it you're orchestrating."* Direct relevance to the **Cost Optimization / agentic FinOps positioning**: empirically confirms the levers (model routing, prompt caching, context hygiene, sub-agents) and shifts the KPI toward **cost per completed outcome**. Strong convergence with Bain's *cross-system labor* (execution data moat, Cursor), Ng's *No AI jobpocalypse* (pricing anchored on the replaced employee's salary), DORA ROI (cost per feature), Mensch/Mistral (electron→token), Ensarguet (economics of computation), Foundation Capital's *Context Graphs* (decision traces, same author), Wescale's *Token Burning*, BFM/Girard (token = value fuel).
**Jaya Gupta** (@JayaGup10) — investisseuse / VC. Très probablement **Foundation Capital** (le thread s'auto-réfère au cadre ***Context Graphs*** — *« ahem, context graph, although I am so tired of that word these days »* — concept porté par Foundation Capital, cf. fiche `bain-100b-saas-opportunity` qui cite *Foundation Capital — Context Graphs trillion-dollar opportunity, 2025-12-22*). Thread publié sur X le **28 mai 2026 à 1h51** · **230 · 5K vues** · format essai long en un seul post. Une réponse notable de **@tuning_engines** (*« DevSecFinOps for the Agentic Era »*) : *« Tokens will basically have to be managed like headcount […] model hierarchies too »*.
Official **Salesforce News** blog post (*Agentic Enterprise* section, *"Pioneering the Agentic Shift Within Salesforce Engineering"* series), published on **May 27, 2026** (6-minute read) by **Srinivas "Srini" Tallapragada**, *President and Chief Engineering and Customer Success Officer* at Salesforce. Direct follow-up to an earlier post (*"How we got our engineers to use AI — without breaking everything"*) which recounted crossing **>90% adoption**. **Pivot thesis**: Salesforce Engineering moved from a world where AI was a useful *copilot* to one where **agentic tools drive the software development lifecycle (SDLC) itself** — writing code, reviewing PRs, generating tests, updating documentation, managing deployments, coordinating work once handled through human handoffs. **Canonical signal decision**: org-wide standardization on **Claude Code** + ***"we removed all token limits"*** — *"remove every last piece of friction between our engineers and the tools that make them faster and more effective"*. **Major empirical result** (April 2026 vs April 2025): work items completed per developer **+50.8%**, PRs merged per developer **+79%**, and above all **Effective Output score** (an ML measure of the **real value of delivered code**, not volume) **+151.3% year over year**. **Flagship use case**: migration of **33 API endpoints** to a cloud-native architecture, estimated at **~231 person-days** (7 per API) the traditional way, completed in **13 days — 18× faster** — via a **rule-based framework built in Claude** (markdown files + reference implementations), with PR feedback continuously fed back into the rule set, **autonomous LLM loops (build, fix, validate)** with no manual intervention, parallelized across isolated environments → **5 PRs**, the largest delivering **21 endpoints with 100% test coverage**. **No speed↔quality tradeoff**: through the **Engineering 360** platform (centralizing engineering data from hundreds of systems), **total incidents drop by 5%** despite the rise in PRs (*"quality doesn't suffer from speed. It benefits from it"*), thanks to **security guardrails and quality standards structurally embedded** in the agentic workflow (Trust as the #1 value). **SDLC overhaul**: once AI is adopted, engineers **tear down and rebuild** workflows (which processes to eliminate? which handoffs are now unnecessary? where does a human still do work an agent could own?). **New engineering craft**: **Claude Code skills** (packaged, reusable capabilities encoding team context, naming conventions, patterns) become a shared, composable **engineering artifact**; **AI Expert Suite** + **Salesforce Foundation Plugins** = an institutionalized, curated skills library (internal benchmark: **higher accuracy and reliability, reduced unnecessary cost**); **subagents & agent teams** parallelize workstreams (*"They describe the outcome, and a set of coordinated agents figures out the steps"*). **What remains hard**: (1) **context management** in long sessions — **CLAUDE.md file quality** varies widely and weighs heavily on output quality; (2) **agentic security** = a fundamentally different model (agents that *act*, not just *suggest* → increased blast radius); (3) **evolving roles** (how do juniors become seniors if AI absorbs entry-level work? role of the designer/PM? the execution unit = scrum team → experiments with 1- or 3-person units). Conclusion: *"It changed what was economically possible"*; the stated ambition is **"the most automated, agentic SDLC in the industry"**. Directly intersects with Gupta (*cost of a completed outcome*, marginal token utility), Greenwald/Sierra (outcome-based pricing), DORA (ROI / cost per feature) and the BFM/Girard debate (token as a value fuel, not a cost to cut).
#Agentic SDLC#agentic SDLC#Claude Code
**Srinivas « Srini » Tallapragada** — *President and Chief Engineering and Customer Success Officer* de **Salesforce**. Plus d'une décennie chez Salesforce · dirige l'ingénierie mondiale de la plateforme unifiée. Auteur de la série *Agentic Enterprise* sur le blog Salesforce News ; ce billet (27 mai 2026) est la **suite** d'un premier opus consacré à l'adoption de l'IA par les milliers d'ingénieurs Salesforce (*« How we got our engineers to use AI — without breaking everything »*). Position d'autorité = **dirigeant exécutif** parlant en son nom et au nom d'une organisation d'ingénierie à grande échelle (donnée terrain à l'échelle d'un hyperscaler SaaS) · avec accès aux métriques internes (Engineering 360, Effective Output).
Pivotal essay by **Dan Shipper** (CEO Every) published on **May 21, 2026** on every.to, *"After Automation"* — an argued response to the thesis of AI-driven collapse of knowledge work. **Pivot thesis**: AI progress creates **more work for humans, not less**. Looping mechanics (***"the commodification cycle"***): (1) AI commoditizes yesterday's human skill; (2) that cheap skill is widely adopted → abundance; (3) abundance produces *sameness* (the *"slop"*); (4) humans demand difference → renewed demand for experts; (5) experts use AI to address today's problems → loop. **Canonical quote**: ***"There's more work to do than ever"***; ***"AI commoditizes the residue of human expertise, creating demand for what's different"***. **Central conceptual framework — Frame vs. Framer**: benchmarks measure performance ***"within frames"*** (specific problem framings); once saturated, *changing the frame resets the counter* — models **escalate within frames but do not replace the framers**. Pivot formula: ***"the frame is not the framer"***. Even at AGI, humans must **specify goals and interpret results** — *"the frame problem regenerates one level up"*. **The "Human Sandwich"**: Human sets frame → AI executes → Human judges and extends. **Two modes of working with agents**: (a) ***agent employees*** — asynchronous delegation (coworker / embedded — Claudie, Andy, Viktor, Fin); (b) ***human-AI collaboration*** synchronous (Claude Code and equivalents). **Every data**: 95% of CEO emails processed by AI; **Fin (Intercom) resolves 65% of support conversations**. **The Zeno's paradox of AI**: AI continuously closes the gap, but humans remain "the turtle ahead" because they are ***"alive to a specific moment"*** — *"running wants, running concerns"* — while models operate on historical training data. **Detailed benchmarks**: **GPT-5.5 = 62/100 on Senior Engineer codebase rewrite** (vs human 80-90s); **GDPval**: 40-49% of expert human level, **but with extensive human framing**. **OpenClaw 44,469 PRs** in May 2026 (vs Kubernetes 5,200 in 2022) — proof that agentic work creates *"more work"*, not *"less human work"*. **AGI implications**: even at AGI, the **human framer** remains structurally ahead — addressing *"current, situated"* problems while the model operates on *"historical training data"*. **Anti-tipping-point pivot conclusion**: this is not a tipping-point event, it is ***a persistent pattern*** that defines the future of work. **Major relevance**: an explicit counter-narrative to *Amodei white-collar bloodbath* / *Sun permanent underclass* / *Anthropic Economic Index* — Shipper, **CEO of a company that lives with agents daily**, offers the theoretical framework that reconciles the two empirical observations (AI does more + humans remain indispensable). Strong convergence with **Ng "No AI jobpocalypse"** (2026-05-08), **Mollick × roon ASI / FDE** (2026-05-10), **Tatsyi/Raiffeisen "AI made engineers different"** (2026-05-05), **Curran/Intercom 3× R&D** (2026-04-16) — all describing humans as *redeployed toward framing* rather than *replaced*. Productive tension with **Sun NYT permanent underclass** (2026-04-30), **Wallace-Wells AI populism** (2026-05-08), **Osmani Cognitive Surrender** (2026-05-05 — the human framer must remain active). To be leveraged for COMEX / DG / boards: strategic vocabulary for 2026 — *"frame vs framer"* becomes the canonical grid for AI governance.
#Dan Shipper#Every#after automation
**Dan Shipper** — CEO et co-fondateur de **Every** (média / studio AI-native, créateur de la newsletter *Every*, propriétaire du framework et plugin *Compound Engineering* — cf. fiche `shipper-klaassen-compound-engineering-every-agents-2025-12-11.md`). Profil rare : **opérateur-théoricien** · dirige une organisation entièrement augmentée par l'IA (95 % emails CEO automatisés, agents Claudie/Andy/Viktor en production, Fin pour le support) tout en publiant régulièrement des essais conceptuels sur every.to. Voix éditoriale anglo-saxonne de référence dans le corpus 2025-2026 sur les **modes de travail humain-IA**. Article publié sur **every.to/p/after-automation** le **21 mai 2026**.
Engineering article published on **Uber**'s blog by six engineers (Matt Mathew, Prasad Borole, Meng Huang, Sergey Burykin, Gaurav Goel, Bayard Walsh) on **May 21, 2026**, laying out the **AI agent identity and access-control doctrine** deployed in production at Uber for several thousand internal agents. **Pivotal thesis**: existing identity models (human + workload) do not describe **agency** — *« an agent is best defined as an entity that is authorized to act for or in the place of another »* — and lose **provenance** across the hops of an agentic workflow. **Two operational problems identified**: (1) ***« Current Identity Model Doesn't Describe Agency »*** — delegation is the default mode, workflows are compositional (agents calling agents calling tools), behavior is dynamic (plans evolve based on intermediate results); (2) ***« Original Provenance Isn't Effectively Carried Forward Across Agents to Systems »*** — *« Execution context (originating user, intermediate agents) is dropped across agent hops. »* **Proposed architecture** as an extension of Uber's Zero Trust Architecture: **Agent Registry** (source of truth for agent↔workload mappings) + **AI Agent Mesh** (inter-agent data plane) + **STS (Security Token Service)** (issuance of short scoped JWTs) + **MCP Gateway** (policy enforcement point for tool invocation) + **AI Gateway** (mediation of external LLM calls with guardrails) + **SPIRE** (workload credential provider). **Cryptographic mechanics**: workloads fetch cryptographically signed **SVIDs (SPIFFE Verifiable IDs)** from SPIRE → the SDK requests a JWT from the STS via the workload identity → the STS verifies the agent's authorization against the Agent Registry → a short token (TTL on the order of minutes) is issued for a **specific single-hop destination** (targeted `Audience` claim). **Pivotal doctrine**: ***« Single-hop, short-lived tokens. Every JWT minted by the STS is intended for a single hop, with a specific Audience claim and a short time-to-live in the order of minutes. »*** **Actor-chain preservation**: multi-hop example with on-call engineer `user1` → Oncall Agent (Workload-1) → Investigation Agent (Workload-2) → MCP Gateway; the final JWT carries a verifiable **actor chain `[user1, oncall-agent, investigation-agent]`**, enabling tool-level access decisions based on the **full request history**. **Standardization**: a **Standardized A2A (Agent-to-Agent) Client** that automates STS exchanges and actor-chain propagation — *« the secure path is also the easiest path for developers to implement A2A calls »* — phased migration of legacy agents. **Production metrics**: ***« P99 latency for the STS Token Exchange API is consistently below 40 milliseconds »***, thousands of internal agents onboarded, a real-time observability dashboard tracing multi-agent sessions. **Long-term vision — three-layer framework**: (1) Identity & Trust Foundation (verifiable agent identity + delegation chains), (2) Dynamic Access Control (context-based permissions + human-in-the-loop), (3) Unified Enforcement Plane (centralized, observable policy). **Standards alignment**: the IETF **WIMSE** working group + draft `draft-klrc-aiagent-auth-01` *AI Agent Authentication and Authorization*, conceptually grounded in **OAuth 2.0 Token Exchange (RFC 8693)** and **SPIFFE/SPIRE** (CNCF graduated). The first reference publication from a non-AI-lab hyperscaler (logistics/mobility) that industrializes agent security at the infrastructure level, bridging the doctrinal gap between skills/harness frameworks (Vincent, Lattice, PROJ-AI) and enterprise-grade identity questions.
Pivot article **Ivan Chepurin & Travis Turner** (Evil Martians Chronicles, **May 19, 2026**) — ***« AI-assisted engineers are burning out, is this fine? »*** — **structured diagnosis of burnout among AI-assisted developers** and a **5-axis intervention toolkit**. **Pivot thesis**: AI-accelerated productivity hides a **hidden cost — developer exhaustion**. *« Higher productivity doesn't translate to sustainable work practices or job satisfaction. »* Shunryu Suzuki epigraph on mental agitation. **TL;DR — 3 essential remedies**: (1) restore enjoyment of the process, (2) rebuild accomplishment / ownership / pride, (3) remove the pressure of continuous productivity maximization. **Central narrative frame — Ben vs Alice**: Ben (traditional coding) = 4 h of steady work, distributed cognitive load, satisfaction at completion; Alice (AI-assisted) = 2 h of cognitively high-intensity work, continuous task-switching, **no satisfaction** + fills the freed-up time with more tasks → **exponential escalation of load** despite accelerated output. **Canonical formula**: ***« We compensate for a lack of satisfaction with work quantity. »*** **Structural disruption of the craft cycle**: (planning → crafting → result) compressed into (planning → result), removal of the meditative craft phase replaced by **cognitively demanding code review**. Direct convergence with **HBR study 2026** (cited): *« cognitive exhaustion from intensive oversight of AI agents is both real and significant »* + **UC Berkeley research 2026**: workers fill natural breaks with AI tasks. **Quiet career change** — pivot concept: developers hired to code now do **different work without a conscious career transition**. 4 possible paths: (1) find enjoyment in the new structure (prioritized), (2) ignore AI, (3) work without enjoyment (unsustainable), (4) change careers. **5 daily burnout factors identified**: (1) ***Losing context*** — the agent carries project understanding externally, cognitive-debt shift from code to people, loss of system intuition; (2) ***No time for passive thinking*** — *« The model fills the silence before your own thinking has a chance to connect dots »* (showers, walks eliminated as moments of unconscious problem-solving); (3) ***False expectations*** — initial speed = unrealistic baseline, subsequent slowdowns experienced as failure; (4) ***Review bottlenecks*** — *« the more code is generated, the more code needs to be reviewed »*, disproportionate cognitive load on seniors, diffusion of responsibility; (5) ***Endless possibilities*** — low prompting friction encourages constant pivots, absence of natural scoping. **5-intervention toolkit**: (a) **Acknowledge your wins** (win-log, team demos, hours tracker); (b) **Rethink AI workflow** (planning > review, **3-4 iterations max**, no parallel task-switching, separate AI-heavy tasks with breaks, decompose); (c) **Keep exercising your craft** (protected AI-free craft hours, *« ask » mode > generation mode*, agents off on passion projects); (d) **Discipline + work-life balance** (fixed hours, real breaks, daily intentions, stop when done); (e) **Find new areas of interest** (user research, soft skills, analytics, agent fine-tuning + guardrails, perf optimization). **Conclusion**: *« AI can be helpful. Problems appear only if you misuse it. »* Industry evolution = inevitable; individual well-being = controllable. Major convergence with **Osmani Cognitive Surrender** (2026-05-05), **Frizzo "Year With Claude Code"** (2026-05-05 — *« writing muscle atrophy »*, *« deep flow rare »*), **Bedard BCG/HBR Brain Fry** (2026-03-05 — 1,488 employees, peak of 3 tools, +39% errors, +39% intent to leave). Major relevance for **CTO / VP Engineering / IT HR** dealing with the retention of AI-augmented engineers in 2026.
#Ivan Chepurin#Travis Turner#Evil Martians
**Ivan Chepurin** & **Travis Turner** — auteurs Evil Martians (cabinet de conseil ingénierie indépendant, Berkeley/global, ~150 ingénieurs, spécialiste Ruby on Rails / React / produits SaaS depuis 2010 ; éditeurs du blog *Evil Martians Chronicles* — référence dans la communauté Rails et JS). Article publié dans la catégorie **AI / Developer Community** sur evilmartians.com le **19 mai 2026**. Profil Evil Martians : voix éditoriale **opérateur-praticien** · articles longs ancrés dans le terrain produit · registre **soin du craft + lucidité business** · public habituellement développeurs / CTO / fondateurs early-stage.
Internal teardown report on the open-source release **`xai-org/x-algorithm`** (May 15, 2026) — the **For You feed** algorithm of **X (formerly Twitter)** in 2026, with four audience-tuned growth recommendation tracks (personal/founder, brand/company, generalized framework, client/consulting deliverable). **Pivot thesis**: ***« The famous 2023 weight table — replies count more than likes by a big multiplier — describes a system that no longer exists in this form. »*** The 2026 algorithm is a **transformer (Phoenix, Grok-1-derived)** that learns weights from your engagement history, scored against a **19-dimension multi-action surface**, gated by an offline content-understanding service (**Grox**). **The shape of scoring now matters far more than the numbers — and the numbers themselves are not in the public release**. **4-component architecture**: (1) **Home Mixer** (Rust, request-time orchestrator, hydrate → source → filter → score → select → filter); (2) **Thunder** (Rust, Kafka-fed in-memory store of recent posts, sub-ms lookups for in-network candidates); (3) **Phoenix** (JAX ML, two-tower retrieval + ranking transformer, ~Grok-1-derived); (4) **Grox** (offline, spam/safety/PTOS/banger classifiers + multimodal v5 embedder). **The 19 actions predicted by Phoenix** (key change vs. 2023): favorite, reply, repost, photo_expand, click, profile_click, vqv (video quality view gated by min duration), share, share_via_dm, share_via_copy_link, dwell, quote, quoted_click, follow_author, not_interested, block_author, mute_author, report, dwell_time (continuous). **Final score** = `Σ (weight × P(action))` modified by **3 structural multipliers**: (a) **OON_WEIGHT_FACTOR < 1** (out-of-network penalty), (b) **author diversity decay** `(1-floor) × decay_factor^position + floor` (exponential attenuation of repeated posts from the same author within a single render), (c) **video duration gate** (vqv only contributes if `video_duration_ms > MIN_VIDEO_DURATION_MS`). **Key caveat**: **no numeric weight value** (`FAVORITE_WEIGHT`, `OON_WEIGHT_FACTOR`, `AUTHOR_DIVERSITY_DECAY`, `MIN_VIDEO_DURATION_MS`...) is in the release — everything is `crate::params::*`, managed by an internal X feature-switch service for A/B testing. ***« Anyone telling you 'replies are worth N.N× more than likes in 2026' is fabricating a number that is not derivable from the OSS release. »*** **Key differences vs. 2023**: (1) removal of every hand-engineered feature (*« We have eliminated every single hand-engineered feature and most heuristics from the system »*); (2) a single model predicting 19 actions vs. multiple single-action models; (3) Grox separates content understanding from ranking; (4) new first-class signals (continuous dwell, gated vqv, follow_author, 3 share variants); (5) two-tower OON retrieval (vs. SimClusters+heuristics) with multimodal text+image+ASR-video embeddings. **Three layers of reach** (generalized framework): Eligibility (binary, Grox+filters) → Retrieval (probabilistic, two-tower ANN) → Ranking (continuous, weighted-sum + multipliers). **Two laws of mechanical growth**: (1) In-network is multiplicative, OON is additive; (2) The model's job is to predict you, not reward you. **Deliberate honesty boundary**: released Phoenix checkpoint = mini (2 layers, 4 heads, 256-dim, 537K sports-post corpus), not the production model; Thrift integrations stubbed (`panic!("Not implemented")` in `candidate_features.rs`); brand-safety lists, topic ID mappings, language penalties, ad-blending rules absent from the public release.
#X algorithm 2026#xai-org/x-algorithm#For You feed
Rapport interne **non signé** (typique des deliverables d'analyse interne / brouillon de livrable client). Sources primaires citées : (a) le repo public **`xai-org/x-algorithm`** (release 15 mai 2026) · (b) les `README.md` du repo et de ses sous-modules (`home-mixer/`, `phoenix/`, `thunder/`, `grox/`) · (c) le code source Rust (Home Mixer, Thunder) et Python/JAX (Phoenix, Grox) inspecté directement avec citations file:line. Le rapport est explicitement écrit en posture *"what we observe in the public source release · and what it implies for measurable growth interventions"* — registre de teardown analytique avec discipline d'honnêteté épistémique (section A.3 *"Honesty boundary"* listant exhaustivement ce qui n'est pas dérivable de l'OSS).
First social encyclical of **Pope Léon XIV** (Robert Francis Prevost), dated **15 May 2026** (Rome, near St. Peter's, 2nd year of the Pontificate), published for the **135th anniversary of *Rerum Novarum*** (Léon XIII, 15 May 1891) and explicitly presented as a **continuation of the Church's Social Doctrine into the AI era**. Canonical subtitle: *"on the protection of the human person in the age of artificial intelligence"*. **245 paragraphs**, structured as **Introduction + 5 chapters + Conclusion**. **Pivotal thesis** organized around two **biblical icons**: the **Tower of Babel** (Gen 11) — technological uniformity without God, *"absolutization of the human"* — versus **Nehemiah's reconstruction of the walls of Jerusalem** (Neh 2-6) — shared responsibility stone by stone, listening, coordination among families. *"The first choice is not between a 'yes' or a 'no' to technology, but between building Babel or rebuilding Jerusalem"* (n. 9). **Canonical concepts**: (1) **AI "cultivated" rather than "constructed"** — *"developers do not directly design every detail, but create an architecture on which the AI develops"* (n. 98), a remarkable theological formulation that echoes recent ML-research vocabulary; (2) ***"Disarming AI"*** (n. 110) — *"removing it from the logic of armed competition, which today is no longer only military but also economic and cognitive"*, making AI *"habitable, by restoring it to the plurality of human cultures"*; (3) **Radical critique of "alignment"** — *"We cannot content ourselves with invoking the moralization of the machine, what is called the 'alignment' of AI with human values, without having the courage to add a further condition: the possibility of debating the ethical code to be used"* (n. 107). ***"A more moral AI is useless if that morality is decided by a handful of people."*** (4) **Epistemic asymmetry** and **new AI monopolies** (n. 109) — *"in a world where a few actors concentrate data, computing resources and regulatory power"*; (5) **Invisible labor** of data labelers/moderators/rare-earth extractors (n. 109, 173) — *"bodies marked, mutilated, used so that the flow of computation never stops"*; (6) **Data colonialism** (n. 178) — *"it dominates not only bodies, but appropriates data"*, *"new rare earths of power"*; (7) **AI and war** (n. 197-200) — *"No algorithm capable of making war morally acceptable"* (n. 198), three criteria: traceable personal responsibility, refusal to shorten the time for moral judgment, protection of civilians; (8) **Critique of transhumanism/posthumanism** (n. 115-117) as *"an archipelago of conceptual islands linked by the same ocean of assumptions: the centrality of technique and the dream of surpassing the limits of the human condition"*; (9) **Work in the transition** (n. 150-156) — *"contrary to the advertised benefits of AI, current approaches to technology can paradoxically deskill workers, subject them to automated surveillance"*, access to work as a public priority, anticipation of the transformation, setting social criteria for innovation; (10) **Canonical question drawn from John Paul II** (Redemptor hominis 1979): ***"does AI make human life on earth 'more human' in every respect? Does it make it more 'worthy of man'?"*** (n. 129); (11) **Authentic "more than human"**: not transhumanism, but grace — *"we manage to be fully human when we are more than human, when we allow God to lead us beyond ourselves"* (n. 128, citing Francis, *Evangelii gaudium*); (12) **Disarming words** (n. 214) — *"Let us disarm words and we will help disarm the Earth"*. **Addressees**: *"To all Catholic faithful, to all Christians, to all men and women of good will"* (n. 16) — a **universal** register in line with *Pacem in terris* (John XXIII 1963), *Laudato si'* (Francis 2015) and *Fratelli tutti* (Francis 2020). **Special appeal to AI developers** (n. 111): *"every design choice expresses a vision of humanity"*. Key **magisterial source** cited: *Antiqua et nova* (Dicasteries for the Doctrine of the Faith + Culture and Education, 14 January 2025) + *Quo vadis, humanitas ?* (International Theological Commission, 9 February 2026). A major document of the **2026 social Magisterium**, at the junction of Social Doctrine ↔ AI ethics ↔ big-tech geopolitics ↔ critique of microworker labor/rare-earth extraction. Implicit convergence with **Mensch / Mistral** (AI energy sovereignty), **Sun / NYT Permanent Underclass** (cf. labor→capital shift), **Wallace-Wells / NYT AI Populism** (cf. critique of tech oligarchs), **Mollick × roon** (cf. ASI and internal politics). First encyclical by a Pope to explicitly take AI as a **central, structuring subject** rather than one theme among others.
#Léon XIV#Robert Francis Prevost#social encyclical
**Léon XIV** (de naissance Robert Francis Prevost) · 267e Pape de l'Église catholique · élu le **8 mai 2025** · premier pape américain de l'histoire (né à Chicago, USA, 1955 ; double nationalité américano-péruvienne). Augustinien (ancien Prieur général de l'Ordre de Saint-Augustin 2001-2013) · ancien évêque de Chiclayo (Pérou) puis Préfet du Dicastère pour les Évêques (2023-2025). *Magnifica Humanitas* est sa **première encyclique sociale** · signée *« Donné à Rome · près de Saint-Pierre · le 15 mai de l'année 2026 · la deuxième de mon Pontificat »* — date choisie pour **coïncider avec le 135e anniversaire de *Rerum Novarum*** (15 mai 1891) de Léon XIII · dont il a explicitement repris le nom de pontificat en référence à la tradition sociale lancée par son prédécesseur du XIXe siècle. La référence augustinienne est centrale dans le document (citations massives des *Confessions*, du *De civitate Dei* — *« deux amours ont fait deux cités »*, des *Enarrationes in Psalmos*, des *Sermones*). Trace de paternité collective : multiples références à *Antiqua et nova* (note conjointe DDF + DCE, 14 janvier 2025) et *Quo vadis · humanitas ?* (CTI, 9 février 2026) · suggérant un travail conjoint entre la Secrétairerie d'État · le Dicastère pour la Doctrine de la Foi · le Dicastère pour la Culture et l'Éducation · et le Dicastère pour le Service du Développement humain intégral.
Continuous Delivery as the non-negotiable foundation of AI-assisted development — Dave Farley, on his channel *Modern Software Engineering*, argues that without CD, AI is not an accelerator but a trap (theory of constraints and Jevons paradox applied to generated code, ATDD/BDD as a safeguard, deployment pipeline as quality arbiter).
#Continuous Delivery#Generative AI in the SDLC#ATDD (Acceptance Test-Driven Development)
Dave Farley (Modern Software Engineering — YouTube channel)
Testimony of **Arthur Mensch** (co-founder and CEO of **Mistral AI**) accompanied by **Audry Herblin-Stoupe** (director of public affairs) before the **commission d'enquête sur les vulnérabilités numériques** of the National Assembly (chaired by Philippe Latombe, absent — session chaired by the rapporteur). Testimony under oath, ~1h15, May 2026. Mensch's pivot thesis: ***"cloud is artificial intelligence"*** — no distinction between digital services and AI, AI is the atomic unit of the cloud value chain, from semiconductors (ASML) to enterprise deployment. **Mistral in 2026**: 1,000 employees, €12 billion valuation, target of **€1 billion in revenue by end of 2026**, €1 billion invested in R&D over the year, 30% of revenue in France / 70% outside France / ~75% in Europe, clients: DINUM, Caisse des dépôts, France Travail, MACGM, Stellantis, TotalEnergies, BNP Paribas, ministère des Armées, Luxembourg (central administration). **Mensch's conceptual framework**: AI is a **natural resource** — *"we transform electricity into intelligence, into token generation."* Economics: 1 GW of datacenter = **$50 billion in investment over 5 years**, generates **$20 billion in tokens/year** ≈ 50% gross margin. Along the electron→token chain, **~10% of the value is in the electron**, 90% elsewhere (chips, software, services). **Alarmist macro thesis**: if Europe imports 10% of its payroll in non-European AI, that amounts to **an additional €1 trillion trade deficit**; €20 trillion in infrastructure investment is needed to serve Europe (40 GW France / 400 GW Europe). **Sovereignty strategy**: ***"don't think of sovereignty as isolationism but as leverage."*** **Time pressure**: *"we don't have time"* — a **2-year** window before European energy resources are monopolized by American hyperscalers deploying **$1 trillion/year**. **Five operational diagnoses**: (1) Regulatory burden = 5 compliance staff at Mistral, 27 unsynchronized regulations, entrepreneurs leaving for the US; (2) Fragmented market = ~60 European telcos vs. 3 in the US; (3) Public procurement underused as strategic leverage (50% of EU GDP); (4) Energy: 9 GW of French surplus at risk of being monopolized by US players within 2 years; (5) Distillation = a cost-reduction technique, **not** technological catch-up. **Defense doctrine**: Mistral works with the ministère des Armées, explicitly refusing "oversight" of final use ("we don't have democratic legitimacy"), a positioning *anti-Anthropic-Mythos*. **Cybersecurity**: acknowledges the offensive capabilities of models ("it's rising in a linear, predictable way, for everyone at the same time"), opposes the *fear marketing* of an American competitor (implicitly Anthropic). **Campus IA**: very minority stake, potential supplier (Mistral + hyperscalers), €35 billion MGX/Abu Dhabi + Nvidia, 100 hectares at Saint-Arnoult, 1.4–1.6 GW (= Flamanville), French nuclear power = reduced carbon footprint. **Annotation**: teams of PhD candidates (no more microworkers), Madagascar for robotics with wage guarantees. **Business model**: no bubble on the demand side, **supply bottleneck** (chips, memory, helium, electrons). **Warning conclusion**: *"if we don't do it fast enough, we will become a vassal state."*
#Arthur Mensch#Mistral AI#Audry Herblin-Stoupe
**Arthur Mensch** (cofondateur et directeur général de **Mistral AI**) accompagné d'**Audry Herblin-Stoupe** (directrice des affaires publiques et de la communication, Mistral AI). Mensch a cofondé Mistral AI le 28 avril 2023 avec **Guillaume Lample** et **Timothée Lacroix** — tous les trois précédemment dans les *« gros acteurs américains »* (Google DeepMind / Meta FAIR). Audition tenue devant la **commission d'enquête de l'Assemblée nationale sur les vulnérabilités numériques** · présidée par **Philippe Latombe** (député MoDem, Vendée — absent ce jour). Séance présidée par la **rapporteur** (non nommée dans le transcript) · avec interventions du président lui-même (revenu en cours) · du député **Arnaud Saint-Martin** (LFI/Saint-Arnoult — sa circonscription accueille Campus IA) · et de la rapporteur sur les questions économiques.
Launch of **AI/works™**, an **agentic development platform** claimed by **Thoughtworks** to be *"the new standard for building and running industrial-grade systems in the AI era"*. The core pitch is **economic**: *"the old approach made you pay millions to build, run, then pay again to rebuild — AI/works™ ends that routine"*. The platform covers **the entire SDLC** around a central concept, the ***Super Spec*** (a dynamic, unified specification covering architecture, workflows, security, data, UX), with **six capabilities**: Reverse Engineering (legacy → as-is specs), Dynamic Spec Development (raw requirements → Super Spec), Spec to Code (coordinated agents generating testable code), Developer Experience (governed golden paths), Control Plane (agent orchestration with cost transparency, active guardrails, end-to-end lineage), Runtime Ops (continuous monitoring detecting changes, updating the Super Spec, regenerating impacted code). **3-3-3** methodology: 3 days to align the product concept, 3 weeks for the prototype (desirability/viability/feasibility), 3 months for a production MVP. **Constellation Research** recognition: *"changing the economics of enterprise software delivery"* via a *"spec-driven, lifecycle"* approach. Opening tagline: ***"We are doing it again for the AI era"*** — invoking Thoughtworks' XP/CI-CD/microservices heritage. Anti-hype positioning: *"stands on an engineering foundation rather than enthusiasm"*, *"no consultant crowds"*, *"finance can open the bill without switching on emergency lighting"*. Featured partners: AWS, GCP, Azure, Databricks, Snowflake + Claude, OpenAI, DeepSeek, Gemini, Grok + NVIDIA, Groq, Stripe, Spotify, CAST, Cyn DX, Mechanical Orchard.
#Thoughtworks#AI/works#AI works trademark
**Thoughtworks** (auteur collectif corporate, page produit/marketing). Aucun individu cité sur la page. Contexte des figures Thoughtworks pertinentes en arrière-plan : **Martin Fowler** (chief scientist emeritus, *Refactoring*, *Patterns of Enterprise Application Architecture*) · **Rebecca Parsons** (CTO emeritus) · **Birgitta Böckeler** (Distinguished Engineer, *Harness Engineering for Coding Agents*, fiche 2026-04-02) · **Matt Kamelman** (*Service-as-Software*, fiche 2025-12-03) · **Sam Newman** (*Building Microservices*).
Ethan Mollick's (Wharton) consistency test: we'll know AI labs truly believe in ASI the day they dissolve their *Forward Deployed Engineering* (FDE) teams. Public debate with roon (OpenAI) on LinkedIn: roon objects that this is a **hayekian problem** (intelligence does not automatically resolve organizational information flow) and revives the term "**Gentle singularity**". Consensus in the comments: technology is the easy part; internal politics / legacy workflows / contractual liability are the real bottleneck. Marker phrase: *"Curing cancer might be easier than replacing Accenture"*. Epistemic **East Coast vs West Coast** opposition on the trajectory of AI adoption.
#ASI (Artificial Super Intelligence)#Forward Deployed Engineering (FDE)#AI consulting
Manifesto-style article by **Thariq Shihipar** (Engineer & serial entrepreneur, Claude Code team at Anthropic) announcing a **change in the default output format for agents**: replacing **Markdown with HTML**. Thesis: Markdown has been the dominant format between humans and agents (simple, portable, editable, readable) but has become **a bottleneck** as agents produce longer and richer artifacts (specs, plans, reports, code review). Beyond ~100 lines, no one reads a Markdown file anymore. HTML solves six limitations simultaneously: **information density** (tables, CSS, SVG, scripts, canvas, images), **visual clarity** (navigable, mobile-responsive layout), **ease of sharing** (an S3 link directly openable in a browser), **two-way interactivity** (sliders, knobs, "copy as JSON/prompt" buttons to loop back into Claude Code), **native contextual ingestion** (Claude Code reads the codebase + MCP Slack/Linear + git history + Chrome) and **enjoyment** (the author explicitly claims *"it's joyful"*). Five canonical uses detailed: (1) **specs/plans/exploration** in a comparative grid, (2) **PR review** with inline annotated diff, (3) **design & prototypes** with animation sliders, (4) **reports/research/learning** (the author had a prompt-caching explainer generated from git history), (5) **custom throwaway editors** (drag-and-drop of Linear tickets, feature-flag editors, side-by-side prompt-tuner) that produce a re-injectable "copy as markdown/diff/JSON" export. Explicit anti-pattern: *"I'm a little bit afraid that people will read this article and turn it into a /html skill"* — the author **rejects premature skill-ification**, recommending prompting from scratch ("make a HTML file"). Pragmatic FAQ: token cost absorbed by **Opus 4.7**'s 1MM context, 2-4× longer generation, noisy HTML diffs (a real downside), style kept in check via a reference HTML design system.
#HTML#Markdown#output format
Thariq Shihipar (Engineer & serial entrepreneur, équipe Claude Code chez Anthropic — site : thariqs.github.io/html-effectiveness ; X : @trq212)
Editorial by Andrew Ng in The Batch n°352 of May 8, 2026 — **"There Will Be No AI Jobpocalypse"** — which dismantles the narrative of mass unemployment caused by AI, drawing on the **healthy 4.3%** US unemployment rate and robust tech hiring. Ng identifies **three drivers** of the jobpocalypse narrative: **(1) tech incentives** — AI labs benefit from presenting themselves as transformative-disruptive (funding rounds, valuations, talent); **(2) pricing power** — vendors charge **$10,000+/year** to enterprise clients by **anchoring their pricing on the salary of the replaced employee**, rather than on traditional SaaS pricing (per seat / per usage); **(3) corporate messaging** — companies reframe their layoffs as *"AI efficiency"* rather than acknowledging the **pandemic-era overhiring** of 2020-2022. Honest acknowledgment: *"AI disrupts work"*. But Ng flips this into **"AI jobapalooza"** (a play on Lollapalooza) — job creation in AI engineering and adjacent fields with evolving skill sets. Implicit tension with **Amodei** (50% of white-collar jobs eliminated by 2030) — Ng points out, without naming him, that **Anthropic benefits from promoting this narrative** (tech incentives). Published **the same day** as **Wallace-Wells's "AI Populism" NYT Magazine** piece: a perfect mirror reading — Ng = cold economic analysis / Wallace-Wells = popular panic. Pricing-power convergence with **Bain's "$100B cross-system labor"** (same thesis: pricing anchored on salaries).
#Andrew Ng#The Batch#DeepLearning.AI
Andrew Ng (fondateur DeepLearning.AI, Stanford, ex-Google Brain, ex-Baidu, ex-Coursera)
**David Wallace-Wells** publishes a major political pivot article (~16 min audio read) in the **NYT Magazine** on **May 8, 2026** that formalizes and names the populist backlash against the AI industry: ***"A.I. Populism Is Here. And No One Is Ready."*** Cutting subtitle: *"Silicon Valley oligarchs worried about the risks their technology posed to the world. They forgot about people."* **Pivot thesis**: AI founders (Altman, Amodei, Musk, Zuckerberg, Hassabis) spent a decade obsessed with the **existential** risks of their technology while **neglecting the political risk** of a human backlash — which they thought *"wouldn't materialize in time, would be quickly outmaneuvered by machine intelligence or could be bought off by talk of basic-income payments or thin promises of curing cancer"*. **The backlash struck literally**: April 2026, a **Molotov cocktail** thrown at Altman's San Francisco property, then a few days later a **gun attack** on his house. Wallace-Wells picks up **Jasmine Sun**'s phrase (NYT Opinion 2026-04-30, already on file): ***"A.I. populism's warning shots"*** — an analogy to the assassination of UnitedHealthcare CEO Brian Thompson by Luigi Mangione. **Five labs as the new faces of American oligarchy**: *"a fearsome concentration of economic and social power producing a self-compounding pattern of extreme inequality"* — Sam (Altman), Dario (Amodei), Elon (Musk), Mark (Zuckerberg), Demis (Hassabis), nearly all billionaires, *"several of whom are widely described as sociopaths"*. **Shock statistics**: Pew Research 2025 — **50% of Americans more concerned than excited**, **only 10% more excited**; recent Quinnipiac poll — **only the >$200k income bracket has an optimistic view of AI for daily life**; Heatmap polling — data center support/opposition swing from **+2 points (Sept 2025) to −24 points (Feb 2026)**, a **26-point swing in 4 months**; Northern Virginia 2023-2025 — a **69-point swing against data centers** (+45 → −24). **Loudon County**: data centers will generate **$1.3B of $2.9B** in tax revenue in 2027 (~45%). **Investment-housing asymmetry**: the United States **spent more on AI infrastructure than on single-family homes** in 2025, **10× more data centers than Germany** (#2), **20× more AI investment than China** (#2), amid a **housing shortage of 10 million missing units**. **Central Ted Chiang quote (BuzzFeed 2017)** invoked: *"When Silicon Valley tries to imagine superintelligence, what it comes up with is no-holds-barred capitalism."* **Dario Amodei quote (Anthropic, 2024)**: *"People outside the field are often surprised and alarmed to learn that we do not understand how our own A.I. creations work. They are right to be concerned: this lack of understanding is essentially unprecedented in the history of technology."* **Political pivot flagged**: the **White House** proposes forcing a **federal review of all new proprietary models before release** — a major turn after a pro-industry stance. **Catalyst**: Anthropic's public refusal in **April 2026** to release **Claude Mythos**, a model capable of *"find[ing] and exploit[ing] security vulnerabilities in every tested piece of software, including those used in critical pieces of global I.T. infrastructure"* (already on file via the **AISI UK GPT-5.5 / Mythos** fiche, 2026-04-30). **Dean Ball quote (original architect of Trump AI policy, Palantir Foundation Yale conference)**: *"This giant acid vat which would dissolve the mediating institutions most Americans see as society. It will not be A.I. in government. It's going to be A.I. as governments."* **Jeffrey Ding concept**: *"diffusion marathon"* (vs. winner-take-all race) — AI as a *general-purpose technology* (steam, electricity, internet) where **diffusion** matters more than the **state of the art**. **Pivot conclusion**: *"We still know the names of the robber barons, and live still somewhat in their shadows. But we are not their serfs. Are we sure A.I. will be different?"* Major relevance for the 2026 file: **conceptual formalization of the political backlash** anticipated by Sun (April) and flagged by Ng in The Batch (Altman Molotov cocktail, ~$64B in blocked data centers, Maine 20MW+ moratorium). To be mobilized for AI geopolitics executive committees, regulation debates, strategic presentations on the societal and political risks of AI, and FR/Europe framing of AI's political feedback loop.
#David Wallace-Wells#NYT Magazine#AI Populism Is Here
**David Wallace-Wells** — NYT Magazine staff writer · journaliste américain reconnu pour son travail sur le climat (livre *The Uninhabitable Earth* 2019, ancien deputy editor de *New York Magazine*). Connu pour des essais long-form combinant reportage · prospective et critique politique des technologies. **Article publié dans le NYT Magazine** le **8 mai 2026** (édition online, ~16 minutes audio) · section politique-tech.
Podcast by Greg Isenberg × Meng To (designer, founder of Design+Code, creator of Aura / New Form / Dream Cut) on **`design.md`** — Google's open-source convention, equivalent to `agents.md` / `skills.md` / `soul.md` but **for the design system** (typography, colors, spacing, WebGL/Three.js animations, reveal rules). Central idea: carry "the **soul of design**" in a markdown file that is passed to an agent (Claude Code, Codex, OpenClaude, Gemini, Stitch, Aura, V0, Lovable, Cursor) to preserve **cross-medium consistency** (web, mobile, Replit slides, Hyperframes/Remotion motion design). Triad taught: **HTML = finished dish, design.md = recipe, skills = ingredients** (typography, lasers, skeuomorphic, 3D skills — 63 in New Form). Major diagnosis: **design drift** on one-shot workflows (`v0`, Lovable, Framer) that start strong then drift into generic output. Meta-message: *taste* is the only remaining **moat** — *"if something looks like another thing, its value drops by 10× to 100×"*. Workflow: **Reference → Design.md → Generate → Inspect → Systemize → Iterate (up to 1000+ prompts) → Remix → Expand → Export**. Critique of **purple gradients** ("you just run") as the generic post-vibe-coding baseline. Meng To claims to have spent ~$500,000 on tokens, made 1,000–10,000 iterations per product, and runs 4 products in parallel solo.
#design.md#Google#design system
Greg Isenberg (host — podcast Late Checkout / The Greg Isenberg Show, 12 mai 2026 livestream workshop ideabrowser.com) ; **Meng To** (guest — designer, fondateur Design+Code 2014, créateur Aura / New Form / Dream Cut, autodidacte parti à 18 ans, dropout, francophone d'origine canadienne)
Televised debate on BFM Business (*Tech & Co Business* program, "The Debate" segment, 17 minutes) with **Rémi Jacquet** (CEO of Cast Software France, founder in 2023 of a think tank of about a hundred CIOs on the impact of generative AI on development, partnership with Cigref / Epita) and **Didier Girard** (CTO and CEO of **SFEIR**, a French IT services company (ESN) of about 1,000 people). Strong theses: *"writing code has become an anti-pattern"* (Girard), AI produces code of higher quality than most engineers and is *"2 to 10× more efficient"* — this is a reality, but the profession is not disappearing. The developer becomes a **conductor / agent manager / arbiter**, 14-day sprints are replaced by one-hour to half-day ***bolts***, the **Pizza Team** (8-10 people) no longer works in the agentic era, a new role is emerging — the ***product engineer*** —, the lifespan of a skill drops from **10 years to 1 year**, and **token** consumption becomes the *fuel* of value creation (NVIDIA anecdote allegedly paying bonuses in tokens, taxi driver metaphor for a driver who doesn't consume gas). SFEIR claims *"1,000 people, production capacity of 10,000"*. On the Cast side: positioning on ***harness engineering*** (deterministic vs probabilistic AI, control and guardrails), aligned with Sylvain Duranton's (BCG X) op-ed in *Les Échos* stating that *"an agent = an LLM + harnesses"*. Historical pivot: 2024 *prompt engineering* → 2025 *context engineering* → 2026 *harness engineering*. Key warning: *"the stronger AI becomes, the more we let our guard down — the more risks there are"* (Jacquet). Pivotal role of HR in the transformation, complete overhaul of the SDLC, recommendation to juniors to solidify software architecture fundamentals (*"code is the score, you need to master the symphony"*).
Interview with Boris Cherny (creator of Claude Code, Anthropic) at a Sequoia event (hosts: Asia, Lauren Reader). Cherny states ***"coding is solved"***: he himself has written **0 lines of code** since late 2025, the model writes **100%**, *"a few dozen PRs/day, 150 PRs in a single day record"*. Account of the genesis of Claude Code (Anthropic Labs incubator late 2024, Mike Krieger in charge of round 2, pre-PMF build *"for the next model"*, first release that didn't take off, **exponential growth started with Opus 4 in May 2025**, accelerating with every new model 4 → 4.5 → 4.6 → 4.7). Current personal setup: **"most of my work I do from my phone"** (iOS), 5-10 sessions, **"a few hundred agents going, a few thousand at night"**, **`/loop` is the future** (cron + repeat jobs, agents that babysit CI, rebase PRs, cluster Twitter feedback). **Routines** = server-side equivalent, laptop closed. SaaS vision: no apocalypse, but **reordering of Helmer's 7 Powers framework** (switching costs ↓, process power ↓, network effects/scale economies/cornered resources unchanged) and **10× more disruptive startups** over the next 10 years. Pivot analogy: the **Gutenberg press** (10% literacy in the 1400s → 70% within a few centuries, books 100× cheaper within 50 years), *"software will be similarly democratized, but faster than 50 years"* — *"the best person to write accounting software is not an engineer, it's a really good accountant."*
#Boris Cherny#Anthropic#Claude Code
Boris Cherny (créateur de Claude Code, Anthropic) interviewé par Lauren Reader (Sequoia) avec introduction d'Asia (Sequoia).
LinkedIn op-ed by Alexandre Frizzo after one year of daily use of Claude Code, offering a **nuanced assessment** rare in the 2026 corpus — productivity **multiplied by 3-5×** in his case (consistent with Wescale, and in line with the median of committed practitioners; the elite tail goes much higher, cf. Cherny *few dozen PRs/day + 150 PRs record* and Karpathy *"peaks much higher than 10×"*), but with **hidden cognitive costs** acknowledged. Pivot thesis: ***"the new bottleneck is supervision"*** — the job has changed shape, one no longer *writes* code, one *decides* about code generated by agents. Gains: 3-5× output, previously infeasible projects now achievable (yak-shaving, boilerplate), near-zero cost of experimentation. Acknowledged losses: ***"writing muscle"*** atrophied (manual code now feels *effortful*), **deep flow state rare** (constant context-switching between supervision tasks), **diminished ownership satisfaction** (*"code is good, but isn't quite mine"*). Unresolved tensions: **FOMO** (*"every hour I'm not at the keyboard is an hour an agent could be earning for me"*), **review quality** at 3-5× volume, **skill atrophy**. Statistics cited: median 3-4h effective coding over an 8h day, **23 min** context recovery per interruption (Gloria Mark study), 15-25 min to enter flow, 500% productivity in flow (McKinsey). Exemplary epistemic stance: simultaneously rejects the *"AI is bad"* narrative and uncritical enthusiasm. A salutary counterweight to Cherny's *"coding is solved"* (2026-05).
#Alexandre Frizzo#LinkedIn Pulse#year with Claude Code
Alexandre Frizzo (auteur LinkedIn Pulse, identité tech non précisée par le post au-delà du nom — auteur d'une tribune one-year retrospective Claude Code).
Methodology article by Antoine HABERT (WEnvision) that formalizes **PROJ-AI**: a lightweight methodological layer so that collective projects become transferable rather than dying with their deliverable. Structuring triad: a **version-controlled git repo** (single source), an **AI agent** (Claude Code, Cursor) that reads the doctrine at every session, and a **markdown doctrine** specifying decision protocols and agent behaviors. Six directory zones (DOCS/, IDEAS/, DR/, OUT/, DOCTRINE/, AGENT/), operational **DPEV** cycle (Decide → Promise → Execute → Verify), Decision Records scored across 7 dimensions, dual interface (business Studio + tech CLI/IDE), five agent directives, and a shared **proj-ai-commons** library that bootstraps a project in 30 minutes vs. 1 week. Metrics across 3 engagements: onboarding **3 weeks → 2 days**, structural decisions tracked **30% → 100%**, architecture doc compilation **6 weeks → continuous**. Central aphorism: ***"The project is not a byproduct of the deliverable. The project IS the deliverable."*** Explicit stance: technology 20%, **team discipline 80%**.
#Antoine HABERT#WEnvision#PROJ-AI
Antoine HABERT (WEnvision — cabinet français de conseil en stratégie et IA agentique).