Post by **David "Pragdave" Thomas** (co-author of *The Pragmatic Programmer*, signatory of the Agile Manifesto) published on **June 6, 2026** on his Substack newsletter. **Thesis**: AI does not abolish code degradation, it **accelerates** it. While adding features to a small personal animation/graphics project with **Claude**, the author moves from initial enthusiasm (oklch, SVG animations shipped in a week) to permanent regression cycles by week two. Striking formulation: what teams took ***"18 months, or even more"*** to rot, he reached in ***"18 hours spread over five evenings."*** **Root cause**: the abandonment of **code hygiene** (massive duplication, local solutions to systemic problems, over-conditioning, proliferation of special cases). **Behavioral diagnosis**: LLMs optimize for user engagement and satisfaction (*"That's a great idea, Dave!"*) rather than durability — they are ***"puppy-dog junior developers, eager to please but quite messy to have around"*** who constantly propose new features and discourage refactoring. **Central insight**: any non-developer can succeed at the *"first week"* of AI coding; it is **professional judgment** — knowing when to stop to refactor — that separates the experienced engineer from the novice. **Epigraph** (Gordon Bell): *"Every big computing disaster has come from taking too many ideas and putting them in one place."* **Conclusion**: ***"It's still just programming"*** — untended code rots, whether in 18 hours or 18 months; everything learned about good code still holds, the effect is simply **amplified**. Converges with the *"the faster execution gets, the stricter the framework must be"* doctrine of [[rafal-wenvision-ingenierie-logicielle-ere-ia-tout-change-rien-ne-change-2026-06-01]], the *"AI-assisted development is a trap without continuous delivery"* of [[farley-continuous-delivery-ai-assisted-development-trap-2026-05-13]], and the *"AI moves bottlenecks, it doesn't eliminate them"* of dropbox-okumura-beyond-code-generation-engineering-productivity-ai-agents-2026-05-28; a craftsmanship counterpoint to vibe coding from karpathy-vibe-coding-agentic-engineering-software-3-0-2026-04-29.
#code hygiene#code rot#code degradation
**David Thomas** (alias **« Pragdave »**) · co-auteur avec Andy Hunt de *The Pragmatic Programmer* (1999, éd. 20e anniversaire 2019) · co-fondateur de **The Pragmatic Bookshelf** et l'un des **17 signataires du Manifeste Agile** (2001). Figure historique du *software craftsmanship*. Billet publié le **6 juin 2026** sur sa newsletter Substack *articles.pragdave.me*.
Analysis by **Olivier Rafal** for **WeNvision** (French consulting firm), published on **June 4, 2026** (~4 min read), commenting on the launch of the **Tokenomics Foundation** by the **Linux Foundation** (announced June 3, in partnership with the **FinOps Foundation**), which he sees as the official opening of **the era of "FinOps for AI."** **Pivot thesis**: AI has transformed the economics of software development; the **token** has become *"the new unit of measurement for technology spending,"* mirroring the cloud of the 2010s (**recurring and variable** costs requiring active management), hence the shift by providers from flat-rate pricing to **token-based billing**. **Scale (urgency)**: *"According to Goldman Sachs, global token usage is expected to increase 24-fold by 2030, reaching 120 quadrillion tokens per month"* — an order of magnitude that moves token efficiency from a *"technical detail"* to a **boardroom** topic. Quote from **J.R. Storment** (founder of the FinOps Foundation): *"Token costs and efficiency have become a CEO-level concern, not a technical footnote."* **Transparency/standardization problem**: current AI pricing is not comparable (input tokens / caching systems / output differ from one model to another) → the Tokenomics Foundation aims to **extend the open-source FOCUS specification** to provide a **common language** for purchasing and comparison. **Rafal's central message (beyond cost)**: *"The point of FinOps is not so much to cut costs as to optimize efficiency"* — the real metric is **AI cost relative to business impact** (*time to market, quality, features, eco-design*). **Limits of standards alone**: technical norms are not enough; the **Target Operating Model must be rethought** (teams, processes, data culture, business alignment); Americans are already announcing *"the end of double-pizza teams in favor of sandwich teams."* **Warning marker**: *"an AI-boosted SDLC will merely […] amplify the problems and just help you go faster… into the wall"* (absent organizational foundations). **Foundation sponsors cited**: Accenture, Booking.com, Google Cloud, Microsoft, IBM, Salesforce. **WeNvision's offer**: *"co-build a roadmap, rethink the operating model for the agentic era, and establish the financial governance that has become indispensable."* **French-language reading, aimed at executives/transformation leaders**, of the fiche [[tokenomics-foundation-linux-finops-token-economics-about-2026-06-03]]; converges with the agentic FinOps cluster [[finops-foundation-finops-for-ai-overview-2026-02-17]], finout-finops-ai-agents-four-step-allocation-framework-2026-04-27, gupta-token-budget-wars-marginal-token-utility-2026-05-28 (token→outcome, value > volume).
#Tokenomics Foundation#FinOps for AI#FinOps for AI
**Olivier Rafal** · pour **WeNvision** (cabinet de conseil français — bureaux à Paris, Lille, Strasbourg, Bordeaux, Nantes, Toulouse, Belgique, Luxembourg). Olivier Rafal écrit en analyste/conseil familier des préoccupations de comité de direction (ancien analyste IT, profil conseil-transformation). Publié le **4 juin 2026**.
Engineering write-up from Anthropic's **Data Science & Data Engineering** team (Chen Chang, Clement Peng, Justin Leder, Johanne Jiao, Josh Cherry) published on **June 3, 2026** on the Anthropic blog (*Enterprise AI* category, focus on **Claude Code**). **Headline result**: ***"95% of business analytics queries are automated by Claude, with ~95% accuracy in aggregate"*** (up to **~99%** in certain domains). **Core problem**: analytics is **not** code — *"there's often only a single correct answer using a single correct source"* — it requires **mapping a user question to precise, up-to-date entities** in the data model. Three **failure modes**: (1) **concept↔entity ambiguity** (e.g. *"active users"*: which actions? exclude fraudsters? which window?); (2) **staleness** (assets and the agent's knowledge become *"subtly wrong"*); (3) **retrieval failure** (*"80% of failed queries had the information present in the corpus"* but unfindable). **Solution = a 4-layer "agentic analytics stack"**: (L1) **Data foundations** — dimensional modeling, **canonical datasets** *"single source-of-truth"*, metadata *"as a first-class product"*, integrity via CI/CD; (L2) **Sources of truth** in decreasing order of trust — **semantic layer** (the agent is *"structurally required (by skill instruction) to leverage the semantic layer first"*), lineage graph, **query corpus** (distilled into structured docs, **not** raw retrieval), business context (knowledge graph: roadmaps, decision logs, org); (L3) **Skills** — the decisive lever: ***"without skills … didn't exceed 21% … Adding skills gets these numbers consistently above 95%"***; structured **in pairs** (*Knowledge skill* = router to ~30 reference files; *Unbook skill* = senior analyst workflow: clarify → find sources → execute → **adversarial review**); **colocated** maintenance (*"a code-review hook flags any reporting-model change that doesn't touch a skill file"* → **~90% of data PRs include a skill change**); (L4) **Validation** — offline evals (threshold ~90% to launch an agent, target ~100%), **ablation testing** (notable negative result: raw grep across thousands of SQL files → accuracy moves *"less than a point"*), online (adversarial review: **+6% accuracy, +32% tokens, +72% latency**), **provenance footers** (source tier + freshness + ownership), **active correction harvesting** (scheduled agents scanning channels to draft markdown fixes). **Strategic insight**: *"documentation generated, definitions owned by humans"* — letting the LLM **define** metrics was *"net-negative"*. **Minimal starting point**: a handful of canonical datasets + a few dozen evals + a *thin knowledge skill* capture *"most of the upside"*. Strongly converges with [[shihipar-claude-code-lessons-building-skills-2026-06-03]] (skills = folders, Gotchas, hooks), the *systems around the model* doctrine of [[dropbox-okumura-beyond-code-generation-engineering-productivity-ai-agents-2026-05-28]], the **semantic layer / ontology** of talisman-modern-data-101-ontology-pipeline-refresh-2026-05-04 and seale-semantic-agent-model-harness-ontology-data-2026-04-17, the *context development lifecycle* of debois-tessl-context-development-lifecycle-ai-coding-agents-2026-02-19, and the UDA/knowledge graph of netflix-uda-unified-data-architecture-knowledge-graph-2025-06-12.
#self-service analytics#agentic data analytics#Claude Code
**Chen Chang · Clement Peng · Justin Leder · Johanne Jiao · Josh Cherry** — équipe **Data Science & Data Engineering d'Anthropic**. Article publié le **3 juin 2026** sur le blog Anthropic (claude.com/blog) · catégorie *Enterprise AI* · ~5 min de lecture.
Blog post from **Anthropic / claude.com** by **Thariq Shihipar** (Member of Technical Staff, Claude Code team), published on **June 3, 2026**, which distills Anthropic's **internal experience** on designing and using **Skills**. **Framing thesis**: a Skill is not a simple markdown file but a **folder** (instructions + scripts + resources + config + hooks) that the agent **discovers and manipulates**; *« You should think of the entire file system as a form of context engineering and progressive disclosure. »* The article makes two structuring contributions. **(A) A taxonomy of 9 skill categories** observed at Anthropic: (1) **Library/API Reference** (docs for internal libs/CLIs with *gotchas* — e.g. `billing-lib`, `internal-platform-cli`, `sandbox-proxy`); (2) **Product Verification** (testing/verification via Playwright or tmux — `signup-flow-driver`, `checkout-verifier`, `tmux-cli-driver`); (3) **Data Fetching & Analysis** (access to data/monitoring stacks — `funnel-query`, `cohort-compare`, `grafana`, `datadog`); (4) **Business Process Automation** (repetitive workflows — `standup-post`, `weekly-recap`, `create-<ticket>-ticket`); (5) **Code Scaffolding** (framework boilerplate — `new-migration`, `create-app`); (6) **Code Quality & Review** (`adversarial-review`, `code-style`, `testing-practices`); (7) **CI/CD & Deployment** (`babysit-pr`, `deploy-<service>`, `cherry-pick-prod`); (8) **Runbooks** (multi-tool diagnostics — `<service>-debugging`, `oncall-runner`, `log-correlator`); (9) **Infrastructure Operations** (maintenance with guardrails — `<resource>-orphans`, `cost-investigation`). **(B) A set of best practices**: don't restate the obvious (*« Claude already knows how to code and can read your codebase »* → target what **contradicts default behavior**); polish the **Gotchas section** (*« the highest-signal content in any skill »*); **progressive disclosure** via the file tree (point to reference files depending on the situation rather than loading everything upfront); **descriptions written for the model** (*« the description field is not a summary, it's a description of when to trigger this skill »*); **setup flows** (config in `config.json`, otherwise prompt via `AskUserQuestion`); **persistent memory** (append-only logs / JSON via the `${CLAUDE_PLUGIN_DATA}` variable); **helper scripts** (*« lets Claude spend its turns on composition… rather than reconstructing boilerplate »*); **hooks conditionnels** (enabled only for the duration of the skill — e.g. a security hook blocking destructive commands). **Distribution at Anthropic**: skills are stored in `./.claude/skills`, informally shared via Slack in a sandbox folder, then promoted via **PR** to the internal **marketplace** once they gain traction; **usage measurement** via a **hook PreToolUse** that logs invocations (revealing popular skills versus underused ones). Direct follow-up to the fiche [[shihipar-claude-code-html-unreasonable-effectiveness-markdown-2026-05-10]] (same author) and a concrete complement to the Skills fiches by Anthropic/Willison/Vincent and to *harness engineering*.
#skills#Claude Code#Anthropic
**Thariq Shihipar** (Member of Technical Staff chez Anthropic, équipe **Claude Code** ; @trq212 / @trq sur X, thariqs.github.io) · pour le blog **claude.com**. Même auteur que la fiche *Using Claude Code: The Unreasonable Effectiveness of HTML* (2026-05-10). Publié le **3 juin 2026**.
**About** page of the **tokeneconomics.com** website, presenting the **Tokenomics Foundation** — a **Linux Foundation** project announced on **June 3, 2026**, operated in **close partnership with the FinOps Foundation**. **Stated mission**: *"establish open industry standards, benchmarks, and best practices for the economics of AI infrastructure"* — linking **production, consumption, and monetization** of tokens to **business value**. **Framing definition of tokenomics**: *"Tokenomics is not just about the cost of tokens, it's about the entire layer of AI that they drive from production, to consumption to monetization"* — that is, **the entire economic layer of AI**, from infrastructure cost to model selection to value optimization. **Phase thesis**: early AI adoption prioritized **capability**; the current phase is shifting toward **efficiency and value**, which requires systematic cost management and **visibility**. **5 founding principles**: (1) ***"Efficiency is a design choice. AI cost is shaped by architecture, not just usage"***; (2) ***"Bigger is not always better. The best AI system is not always the one using the most expensive model"*** (right-tool / routing); (3) ***"Visibility comes before optimisation. Teams cannot manage what they cannot see"***; (4) ***"Value matters more than volume. More tokens, more calls, and more automation do not automatically mean better outcomes"***; (5) ***"Open knowledge benefits everyone"*** (shared standards, community learning, transparency). **Governance**: a **Governing Board** (industry direction + fund deployment) and a **Technical Committee** (open specifications + benchmarks). **Deliverables**: extension of the **FOCUS specification** (FinOps), open specs, benchmarks, shared frameworks and metrics. **Target audience**: CAIO, CTO, CIO, CFO, engineers, product teams, FinOps practitioners, researchers, startups, enterprises, public sector. **Stated goal**: moving organizations *"from experimental AI adoption to sustainable AI operations"* by extending the discipline of **variable technology spend** into the token era. **Relevance to this watch**: institutionalization/standardization of **agentic FinOps** at an industry-foundation level — directly converges with the fiches [[finops-foundation-finops-for-ai-overview-2026-02-17]], [[finout-finops-ai-agents-four-step-allocation-framework-2026-04-27]], orq-ai-finops-ai-agents-cost-per-outcome-hosseini-2026-04-15, gupta-token-budget-wars-marginal-token-utility-2026-05-28 (allocation layer, token-to-outcome) and with the **token → outcome** shift (Salesforce/Tallapragada, Sierra/Greenwald). The 5 principles map exactly onto levers already captured: architecture > usage, **Haiku/Sonnet/Opus routing**, observability before optimization, value ≠ volume.
#Tokenomics Foundation#tokenomics#token economics
**Tokenomics Foundation** (entité collective, projet de **The Linux Foundation**, en partenariat avec la **FinOps Foundation**). Page institutionnelle *About* — **aucun auteur individuel nommé**. Annonce datée du **3 juin 2026**.
On the eve of SpaceX's record IPO (targeted valuation of ~$1.75 to 1.8 trillion), The New York Times publishes an interactive analysis of Elon Musk's track record of public promises. Across more than 600 dated, quantified commitments (statements, posts, investor calls), only ~19% were kept on time, if ever. The rate deteriorates over time: ~75% kept in 2015, less than 50% in 2020. Mars, the robotaxi, and full autonomy account for most of the repeated and postponed targets. The piece links this track record to the SpaceX prospectus, which now bets on AI (xAI merged in) and itself acknowledges that the timeline for its major undertakings is undeterminable.
Guide from the media outlet **Every** (every.to/guides) published on **June 2, 2026**, co-signed by **Mike Taylor, Laura Entis and Claude**, proposing an **8-level maturity scale for AI adoption**. **Pivot thesis**: AI adoption **is not a race toward maximum sophistication** — ***« a higher level isn't necessarily better »*** ; one must identify the level that **matches one's own workflow and level of trust**, then regularly reassess whether moving up a notch adds **real value**. ***« The best way to find value in AI is to use it in a way that fits your work. »*** **Structuring axis**: at each level, *« you delegate more of your work to—and place more trust in—the AI »* (increasing delegation + trust). **The 8 levels**: **(1) Chatbot** — conversational interface with no embedded context (ChatGPT, Claude, Gemini); **(2) Copilot** — AI embedded in the workspace with access to the current file (Cursor, Claude in Excel, Gemini in Docs); **(3) Agent** — reactive system that executes step-by-step while requesting approval (Cowork, Codex); **(4) Autopilot** — one describes the **outcome** and the agent executes autonomously, review of the **final result** only (Lovable, Codex, Claude Code; tied to *vibe coding*); **(5) Workflows** — engineers building **harnesses** around agents (planning, review, confidence checks, guardrails; Compound engineering, Claude Workflows, Copilot AI Studio; shift from one-shot vibe coding → **agentic engineering**); **(6) Assistant** — **proactive, always-on** agents that monitor a domain and surface information without being prompted (OpenClaw, Hermes Agent, Claude Managed Agents; e.g. `heartbeat.md` every 30 minutes); **(7) Multi-agent** — simultaneous management of **several long-running agents** with distinct roles (Claude Managed Agents, OpenClaw, Codex Goals; *« firmly in senior engineering territory »*); **(8) Orchestrator** — an **agent manager** directs a team of sub-agents (planning, delegation, monitoring, consolidation; Gas Town, Paperclip, Symphony/OpenAI; *« highly experimental »* — even frontier engineers themselves hold this role). **Sweet spots by role**: **knowledge workers** typically operate between levels **1-4**, **engineers** between **5-8**. **Canonical parallel of intern onboarding**: *« Expect to put in a similar amount of effort with your agents before you can trust them… at the next level of autonomy »* ; and the marker phrase ***« You wouldn't brag that you had eight interns working overnight on a key project, and you hadn't checked their output. »*** The right level depends on **4 criteria**: output quality, cost, reliability (trustworthiness), stakes of failure; and **model capability** progressively shifts the "safe" level of autonomy. A framework directly usable to structure an **adoption doctrine** on the consulting side. Convergence with *systems around the model* (Dropbox/Okumura), *harness engineering* (Böckeler, Lattice, Wescale), Karpathy (vibe coding → agentic engineering), Cherny (/loop + Routines), and the *agent manager* doctrine (BFM/Girard).
#AI adoption#maturity scale#eight levels
**Mike Taylor** · **Laura Entis** et **Claude** (co-auteurs déclarés) · pour **Every** (every.to) · rubrique *Guides*. Mike Taylor est un auteur connu sur les sujets prompt/AI (co-auteur de *Prompt Engineering for Generative AI*) ; Laura Entis est journaliste/éditrice. La co-signature explicite de **Claude** comme auteur fait partie du positionnement éditorial d'Every (entreprise AI-native). Publié le **2 juin 2026**.
Op-ed by **Olivier Rafal** (Consulting Director Strategy, **WeNvision** — **SFEIR** group; former editor-in-chief of *Le Monde Informatique*) published on **June 1, 2026** on **CIO-Online**, structured around a **paradox**: in the age of AI, software engineering **changes everything… and nothing changes**. **What changes is the operating model.** Roles are redefined: the **Product Owner** shifts from backlog breakdown to **generating context usable by AI**; the **developer** shifts from writing code to **framing, steering, and reviewing** agent execution; **QA** gains the ability to define **expected proof** upfront. Team structure shifts from *"double pizza teams"* (hand-off chains of ~8 people) to ***"sandwich teams"***: a **tight pairing of a business expert and a tech lead, both AI-augmented**, with other skills in support. Internal **Sfeir** figure: *"this pair now drives roughly 80% of the production chain,"* the remaining ~20% (architecture, data governance, security) being centralized. Pivot quote: ***"The issue isn't a tooling issue, it's an operating-model issue."*** **What doesn't change is the discipline of the cycle.** The **SDLC** phases (define → build → verify → deploy → maintain) remain identical and non-negotiable; AI removes none of them, it **intensifies** them: ***"all the slack that human pacing used to absorb, however imperfectly, becomes, at AI speed, industrial-grade defects"*** (an amateur-vs-professional sports metaphor). Hence **three inviolable *gates*** (human control): **specification, planning, delivery review**; validation **by proof** (not by AI's own assertions); **systematic capitalization** (each cycle feeds the next) → measured result: **−30% correction iterations after ~10 cycles**. Principle: ***"the faster the execution, the stricter the framework must be."*** Concepts invoked: **harness** (agentic rules adapted to context), **vibe-coding** judged **untenable in the enterprise**. **Third pillar = governance, FinOps & value-driven management**: **variable and recurring** AI costs (~**€10/hour** per augmented role), shift from flat-fee licensing to usage-based billing (a parallel with cloud in the 2010s); **FinOps** does not aim to cut costs but to *"optimize tool efficiency"* (cost relative to value); aligning **business metrics** upfront (time-to-market, features, performance, eco-design). **Conclusion**: acceleration makes the fundamentals **non-negotiable**; the challenge is **organizational and cultural**, not technological — without securing the business relationship and collective discipline, an AI-powered SDLC only **amplifies the problems** (driving into the wall faster). Extends the WeNvision doctrine of [[rafal-wenvision-ia-generative-produit-techno-pas-projet-2024-02-23]] and [[rafal-wenvision-tokenomics-foundation-finops-ia-2026-06-04]]; converges with *systems around the model* dropbox-okumura-beyond-code-generation-engineering-productivity-ai-agents-2026-05-28, *harness engineering* osmani-agent-harness-engineering-2026-04-19, agentic Salesforce, and the *agent manager* debate (BFM/Girard, SFEIR).
**Olivier Rafal** · *Consulting Director Strategy* chez **WeNvision** (groupe **SFEIR**). Ancien **rédacteur en chef du *Monde Informatique*** · et auparavant consultant analyste du marché IT (~10 ans). Tribune publiée dans la rubrique *Tribune* de **CIO-Online**. Publié le **1er juin 2026**.
Atlassian data study (Inside Atlassian) measuring the actual return of an **AI-native SDLC** powered by **Rovo Dev**. Across 3,400 repositories from 2,500 customers (a quasi-experiment with propensity-score matching), adopting repositories merge **19% more PRs per month**; up to **37-51%** on low/medium-activity repositories and **59-87%** when **3 to 5 members** of the team adopt the tool. On the efficiency side, developers save **2-3 h/week** (≈10% of the 24 hours devoted to coding and review), i.e. 20-30 hours/week reinvested for a team of 10. The thesis: resolve Solow's (1987) "productivity paradox" by shifting from **usage metrics** (tokens) to **impact metrics** (throughput, time saved, failure rate, satisfaction). Recommendation: start with a **team** (not an individual) and measure 2-3 months later.
Blog post by **Pasquale Pillitteri** (software engineer, Palermo) published on **May 29, 2026** (FR version), 18-minute read, *Claude Code & Anthropic* section. **Pivot thesis**: *« Claude Opus 4.8 is the most powerful SEO model of 2026, but almost everyone uses it wrong »* — not a model problem but a **system** problem. The golden rule: ***« strategy is a whiteboard, production is an assembly line »*** — SEO must be **split into two distinct phases**, and mixing them is *« the fastest way to waste a model that costs five dollars per million input tokens and twenty-five for output »*. **Model context**: Opus 4.8 released on **May 28, 2026** (41 days after Opus 4.7), **1M-token** context, **GraphWalks Long-Context F1 at 1M: 40.3% → 68.1%**, **SWE-bench Verified 88.6%**, **USAMO 2026 96.7%** (+27.4 pts), **HLE with tool 57.9%**, unchanged price **$5/$25** per M tokens, **Fast Mode 2.5× at $10/$50**, four **effort levels** (Low, High, Extra, Max). **The central anti-pattern** = *« the giant conversation »* / **context drift**: mixing strategy, keyword research, competitive analysis and writing in a single chat produces a *« mush of contradictory intentions »* → the model slides toward **generic best practices** ("holistic optimization", "strategic approach") instead of data-anchored content. **Phase 1 — Strategy (whiteboard, visual UI, one-off)**: dashboard / Google Sheet / Claude.ai canvas to decide while looking at the data together. **3 plays**: (a) **classified keyword research** (table of volume / difficulty 0-100 / intent / business potential / priority = volume÷difficulty×business weight); (b) **visual competitive analysis** (topic-coverage matrix, gaps); (c) **phased roadmap** (quick wins M1-2 / medium term M3-6 / pillar pages M7-12). **Extra/Max** mode is justified here (*« one right strategic decision is worth a thousand well-written pages on the wrong keywords »*). 3 closed artifacts saved to Notion/Drive. **Phase 2 — Production (assembly line, Opus 4.8 + MCP)**: the model shifts from strategist to **execution machine**; every decision **anchored to live data** via the **Model Context Protocol**. **Minimum MCP stack**: **GSC MCP** (AminForou/mcp-gsc, 500+ stars), **official Ahrefs MCP** (98 stars), **GA4 MCP**; the `modelcontextprotocol/servers` repo = **86,440 stars**, **10,000+ active servers**, 97M SDK downloads/month. Setup ~35 min, monthly refresh ~20 min. **Weekly loop**: a single prompt pulls live data, builds the brief (top 10 SERP + GSC + Ahrefs), derives H2/H3, writes, checks density, suggests titles → **+45% productivity**, draft in **6-12 min** (explicit reference to **Ryan Law / Ahrefs content engineering**, 23 skills). Mentions Anthropic's **Dynamic Workflows** (up to 1,000 subagents). **4 common mistakes**: (1) not checking the numbers (spot-check mandatory, *trust & verify*); (2) fully replacing Semrush/Ahrefs (MCP is a **layer on top**, not a substitute); (3) ignoring the **paid-organic content gap** (education client case: **2,742 wasted terms / 351 opportunities** identified in 90 s); (4) using Opus 4.8 where **Haiku 4.5** suffices (meta descriptions, alt text). **Cost**: $1-3 per 2,500-word article. **Sonnet 4.6** suffices for recurring production, Opus 4.8 reserved for strategy. SEO-optimized and self-referential article (the author writes about SEO in content itself designed to rank for "Opus 4.8 SEO"). Direct convergence with **Ryan Law/Ahrefs** (cited), **systems around the model** (Dropbox/Okumura), **skills-over-prompts** (Lattice), Haiku/Sonnet/Opus model routing (Gupta token-to-outcome).
#Claude Opus 4.8#AI SEO#two-phase workflow
**Pasquale Pillitteri** — Ingénieur informatique / développeur logiciel basé à **Palerme** (Italie) · certifié Innovation Manager UNI 11814:2021. Auteur d'un blog tech actif (rubrique *Claude Code & Anthropic*) · avec une newsletter hebdomadaire (~3,4k lecteurs). Article publié en version **FR** le **29 mai 2026** (lendemain de la sortie d'Opus 4.8).
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 the **Uber** Engineering 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. **Pivot thesis**: existing identity models (humans + workloads) fail to 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)** (short-scoped JWT issuance) + **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-lived token (TTL on the order of minutes) is issued for a **specific single-hop destination** (targeted `Audience` claim). **Pivot 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."*** **Preservation of the actor chain**: a 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 history of the request**. **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"* — with 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) industrializing agent security at the infrastructure level, closing 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.
**Zed** blog post signed by **Franciska Dethlefsen** (head of growth and marketing), published on **May 14, 2026** — the day after Anthropic's announcement — to answer Zed users' questions. **Subject**: starting **June 15**, Anthropic **splits Claude subscription billing into two pools** — one for its **first-party tools** (chat, the official Claude Code CLI), the other for **third-party agent and SDK usage** (anything going through **ACP**, `claude -p`, or a third-party tool). Usage via ACP **then stops drawing from the Pro or Max limits** and switches to a monthly **"Agent SDK" credit**: **$20 for Pro, $100 for Max 5x, $200 for Max 20x**. Once the credit is exhausted, usage continues **at standard API pricing** if overage is enabled — otherwise requests stop until the next cycle. **The figure driving the article**: subscriptions had until then subsidized agentic usage by a factor of **≈15 to 30×** relative to API pricing, and the new credits are billed **at full API rates** — hence *« for anyone using agents heavily, this is a major cost increase »*. **Three options are proposed**, in an order that reveals Zed's position: (1) keep the subscription by running the **official `claude` CLI in a terminal inside Zed** rather than via ACP — *« when the official claude CLI runs in the terminal, it uses your subscription's limits, not the new credit »*; (2) use Zed's built-in agent with the provider of one's choice (Zed-hosted models, API keys, Copilot, local Ollama, DeepSeek); (3) plug in **any ACP agent** — OpenCode, Codex, Factory, Cursor —, several of which still offer rate-limited subscriptions that subsidize heavy usage. **The underlying thesis**, and the real reason for the post: *« ACP is an open protocol… so that your editor is never locked into one provider's pricing decisions »*, with the explicit anticipation that *« this kind of change won't be the last »*. **The post carries an addendum dated June 16, 2026** announcing that **the change is suspended**: ACP, `claude -p`, the Agent SDK, and third-party applications continue to work with subscriptions **as before**, no separate credit to claim, limits unchanged, Anthropic revising its plan with advance notice announced. **The artifact is thus self-contradicting**: its most important content — the reversal — postdates its own publication date by a month.
#Zed#Anthropic#Claude subscription
**Franciska Dethlefsen** — head of growth and marketing chez **Zed Industries**. Le rôle est déterminant pour lire le texte : ce n'est pas un billet d'ingénierie mais une **communication de crise produit** · écrite le lendemain d'une annonce d'un fournisseur dont Zed dépend · à destination d'utilisateurs inquiets. La signature growth/marketing explique la structure (problème → options → réassurance) et le fait que l'argument protocolaire arrive en conclusion plutôt qu'en tête.
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)