# ensarguet-pattern-lineage-design-patterns-architects-ai-2026-06-10

## Veille

Philippe Ensarguet (Orange) argues that fifty years of design patterns form a continuous lineage: at a time when AI commoditizes code and breaks the traditional way architects are trained, "pattern literacy" (reading a system through its invariant forces) becomes the durable skill to teach — as a grammar, not as catalogues.

## Titre Article

The pattern lineage: Why fifty years of design patterns may hold the key to growing the architects AI cannot replace

## Date

2026-06-10

## URL

https://www.linkedin.com/pulse/pattern-lineage-why-fifty-years-design-patterns-may-hold-ensarguet-sldae/

## Keywords

design patterns, pattern lineage, software architect, pattern literacy, architectural judgment, Christopher Alexander, Gang of Four, Hillside Group, invariant forces, coupling and cohesion, abstraction boundary, failure isolation, state governance, indirection, feedback loop, non-determinism, IA agentique, platformization, telecom, control plane / user plane, upskilling, skills growth, judgment transmission

## Authors

Philippe Ensarguet

## Ton

Profile: reflective op-ed by a technical executive (first-person perspective, CTO/VP Engineering at a telecom operator), essayistic-professional register in English, high but accessible technical level, aimed at architects, CTOs, and engineering/training leaders. The tone is that of a deliberately "intuition under construction": Ensarguet lays out a personal thesis, documents it historically (50 years of pattern books, bibliographic references provided), and explicitly submits it to debate ("I am publishing it precisely to stress-test it"). Authority grounded in experience ("I'm 53," 30 years in the field, personal library cited) and in a rigorous genealogy linking Alexander, the Gang of Four, and the 2024-2026 agentic catalogues. Narrative style structured in movements (the breaking pipeline, what a pattern really is, the genealogical tree, the archetypes, the grammar to teach), sustained metaphors (the genealogical tree, grammar vs. catalogue, the pattern that "changes clothes without changing purpose").

## Pense-betes

- **Central paradox**: the architect role becomes critical at the exact moment its training pipeline is breaking down — AI absorbs the entry-level work (writing code) that once forged architects' judgment.
- **Thesis**: the answer to "what to teach future architects" has been sitting on the shelf for years — the lineage of design patterns, read as a continuous story.
- **Definition of a pattern (Alexander, 1977)**: a named, recurring solution to a problem within a context, including the forces in tension and the consequences. It is not a recipe — it is **judgment shaped into a transmissible form**.
- **Recipe vs. judgment distinction**: a recipe tells you what to do; it never tells you when NOT to do it, nor what you're trading off. Judgment = deciding under pressure while knowing the cost of each option — what AI cannot take away.
- **Lasting value of the Gang of Four book**: not the 23 patterns, but the **format** (problem, context, forces, solution, consequences) that makes a trade-off discussable and teachable.
- **Genealogical tree**: GoF (1994) → POSA (1996) → Fowler PEAA (2002) → Hohpe & Woolf EIP (2003) → Nygard Release It! (2007) → cloud (Wilder 2012, Azure/AWS) → Microservices/Cloud Native/Kubernetes Patterns (2018-2019) → agentic catalogues (Anthropic, Ng) 2024-2026.
- **Six invariant forces**: coupling/cohesion, abstraction boundary, failure isolation, state governance, indirection, feedback loop. **+ a seventh**: non-determinism (agentic systems break the assumption of deterministic actors → evaluators, reflectors, validation gates).
- **Concrete lineage**: Circuit Breaker (Nygard 2007) becomes a config field in a service mesh; Proxy (1994) → Sidecar (cloud-native) → LLM guardrails; prompt chaining (Anthropic) = Pipes and Filters.
- **IT / telecom network convergence**: control plane / user plane = abstraction boundary + indirection; network slicing = Bulkhead at carrier scale; intent-based networking = feedback loop (Kubernetes operator model). The grammar is common to both worlds.
- **AI as an ally**: freed from implementation, training can become deliberate — AI generates 3 candidate architectures, the trainee names the forces, weighs the trade-offs, justifies a decision. The machine produces options, the human supplies the judgment.
- **Conclusion**: teach the **grammar** (reading the forces), not the **catalogues** (which age). "The catalogues age; the way of thinking they encode does not."

## RésuméDe400mots

Philippe Ensarguet (Orange) starts from a seemingly administrative question — designing an upskilling path toward the architect role — to articulate a deeper intuition. This role is critical to the "platformization" of a telecom operator (bringing together the IT and network worlds, separated for decades, into programmable platforms). Yet it becomes critical at the exact moment its training pipeline is breaking down: demand for architects is rising (platforming, cloud-native, IA agentique shift complexity from components to the relationships between them), while the talent supply chain is dismantling itself. The traditional path ran through years of writing code; AI now absorbs an increasing share of that work. If the entry-level work that once forged architects is delegated to machines, where will the next generation come from?

The answer, according to Ensarguet, has been sitting on the shelf for fifty years. He returns to the original meaning of a pattern, as defined by building architect Christopher Alexander (1977): a named, recurring solution to a problem within a context, including the forces in tension and the consequences. It is not a recipe — it is transmissible judgment. The Gang of Four book (1994), which emerged from the Hillside Group convened by Kent Beck and Grady Booch, gave the industry its first shared vocabulary — its lasting value being the format (problem, context, forces, solution, consequences), not the 23 patterns themselves.

Ensarguet traces a genealogical tree: POSA (1996), Fowler (2002), Hohpe & Woolf (2003), Nygard (2007, Circuit Breaker), the cloud catalogues (2012+), microservices and Kubernetes (2018-2019), up to the agentic corpora now taking shape (Anthropic's "Building Effective Agents," Andrew Ng's four patterns, the two-axis framework by Huang & Zhou in 2026 — echoing the GoF's two axes thirty years earlier). Beneath the catalogues, six invariant forces persist: coupling/cohesion, abstraction boundary, failure isolation, state governance, indirection, feedback loop — joined by a seventh, the non-determinism introduced by agentic systems.

This "pattern literacy" is the resilient skill, and the only one that finally bridges IT and network (control plane / user plane = indirection; network slicing = Bulkhead; intent-based networking = feedback loop). AI then becomes an ally: freed from implementation, training can become deliberate — the machine produces options, the human supplies the judgment. What must be taught is the grammar, not the catalogues: catalogues age; the way of thinking they encode does not. Ensarguet is publishing this thesis precisely to stress-test it through debate.

## GrapheDeConnaissance

- Philippe Ensarguet —travaille_chez→ Orange (ORGANISATION, 0.97)
- Philippe Ensarguet —publie→ The pattern lineage (DOCUMENT, 0.98)
- Philippe Ensarguet —affirme_que→ la pattern literacy est la compétence durable que l'IA ne peut remplacer (AFFIRMATION, 0.95)
- Philippe Ensarguet —recommande→ enseigner la grammaire des patterns, pas les catalogues (AFFIRMATION, 0.93)
- Christopher Alexander —a_créé→ concept de design pattern (CONCEPT, 0.95)
- design patterns —permet→ transmission du jugement architectural entre générations (CONCEPT, 0.92)
- Gang of Four —s_inspire_de→ travaux de Christopher Alexander (DOCUMENT, 0.9)
- Kent Beck —a_créé→ Hillside Group (ORGANISATION, 0.88)
- pattern literacy —s_applique_à→ rôle d'architecte logiciel (CONCEPT, 0.93)
- IA agentique —réduit→ apprentissage traditionnel des architectes par l'écriture de code (CONCEPT, 0.9)
- design patterns —est_basé_sur→ forces invariantes (CONCEPT, 0.88)
- prompt chaining —est_variante_de→ Pipes and Filters (METHODOLOGIE, 0.9)
- non-déterminisme —affine→ forces invariantes (CONCEPT, 0.87)
- Philippe Ensarguet —affirme_que→ le rôle d'architecte devient critique quand son pipeline de formation se brise (AFFIRMATION, 0.92)
- pattern literacy —converge_avec→ mondes IT et réseau télécom (CONCEPT, 0.88)
- Anthropic —publie→ Building Effective Agents (DOCUMENT, 0.9)
- IA —permet→ formation délibérée au jugement architectural (CONCEPT, 0.85)

---
Canonical: https://www.thekb.eu/en/fiches/ensarguet-pattern-lineage-design-patterns-architects-ai-2026-06-10/