Skip to content

root / tags / ddd

#DDD

2 fiches

Architecture & Construction Auto-verified translation

Le Rôle de l'Architecte à l'Ère de l'Intelligence Artificielle

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

SFEIR (synthèse) — d'après Gregor Hohpe

AI Coding Agents & Skills Auto-verified translation

grill-with-docs — « Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise »

**Skill** entry (not an article): `grill-with-docs` by Matt Pocock is a structured interview technique that "grills" an architecture plan by methodically confronting it against the project's business vocabulary (the `CONTEXT.md` glossary) and already-documented decisions (ADRs). Rather than rushing into implementation, it challenges assumptions one by one through a question/answer dialogue, cleans up terminology, checks consistency against the actual code, and captures decisions on the fly in the right artifacts. An upfront-design skill, inspired by Domain-Driven Design.

#skill#grilling#adversarial interview

Matt Pocock