Essay by **Donn Felker** published on **September 14, 2026** on his Substack (~4,400 words, subtitle *"Your identity was built on a bottleneck"*). The author, AI platform lead at **Polygon** and formerly at **Tinder**, an Android specialist for over ten years, dates his shift to **July 2025** based on three facts: a SaaS built without writing a single line, a threading library migration at Tinder cut from **6-8 hours** to **10 minutes** by a **2,000-word** prompt, and non-technical people (a CFO, a gym manager) shipping complete products. **(A)** He draws from this a psychological framework — *occupational categorization*, *professional identity centrality* — to explain engineers' anxiety: *"It was never about coding, it's about the ability to execute"*. **(B)** He proposes an image of a **leverage pendulum** between product and engineering: AI shifts the initial leverage toward product, complexity and scale pull it back toward engineering, and each oscillation dampens as guardrails and architecture get codified. **(C)** He describes a hybrid role, the **agentic builder**, and a two-step path (codifying one's knowledge into skills, shifting from specialist thinking to systems thinking) with a stated horizon of **six months**. Extends the shift to *agentic engineering* described in [[karpathy-vibe-coding-agentic-engineering-software-3-0-2026-04-29]] and the collapse of boundaries between professions from [[sfeir-ia-frontieres-metiers-skill-based-organisation-2026-08-01]].
*Deepdive* by **Gergely Orosz**, **Jessica Salmon**, and **Ivan Klaric** in *The Pragmatic Engineer*, published on **August 25, 2026**, based on interviews with Ramp's CTO **Rahul Sengottuvelu**, head of engineering **Hamid Dadkhah**, and **Zach Bruggeman**, founding engineer of **Inspect**. Paywalled article: the note covers the public portion (sections 1 through 3 and the opening of section 4; detailed architecture, sandbox internals, and collaboration remain behind the paywall).
SFEIR analysis note that reexamines the software architect profession in the age of generative AI through the framework of **Gregor Hohpe** (*The Software Architect Elevator*). Central thesis: the « **Oracle** » architect — the holder of supreme knowledge dictating rules from an ivory tower — is obsolete, since AI generates code and proposals on demand; the modern architect becomes an **intelligence amplifier (IQ Amplifier)** who provides teams with mental models, business context, and decision tools to leverage AI while ensuring system coherence. The document breaks down the impact **floor by floor of the "Architect Elevator"** (Enterprise / Solution / Platform / Software architect) and argues for **Domain-Driven Design (DDD)** as an essential safeguard: the **ubiquitous language** serves as the basis for *system prompts* (a domain dictionary injected via `.clinerules`/templates, reducing hallucinations and business misinterpretations) and **bounded contexts** restrict the scope entrusted to AI to maximize generation reliability. Conclusion: AI is not a threat but a catalyst that relieves the architect of technical grunt work to emphasize synthesis, strategic vision, modeling, and the human link between tech and business. Domain: software architecture, the architect's role, DDD, structured prompting, enterprise AI governance.
#Software architect#architect's role#generative AI
Legal.io relay of the MIT NANDA study "The GenAI Divide: State of AI in Business 2025": 95% of enterprise AI pilots deliver no measurable ROI despite $30-40B invested. Concept of the "GenAI Divide", "shadow AI economy", four structural failure factors, back-office and build-vs-buy recommendation. Empirical justification for the HR-organizational shift.
#MIT NANDA#GenAI Divide#95% pilot failure
Legal.io (relais et synthèse) — étude MIT NANDA "The GenAI Divide: State of AI in Business 2025"