<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Multi-Agent on Mathias WOLFF</title><link>https://www.blog-des-telecoms.com/tags/multi-agent/</link><description>Recent content in Multi-Agent on Mathias WOLFF</description><generator>Hugo</generator><language>fr-FR</language><copyright>&lt;a href="https://www.blog-des-telecoms.com"&gt;Blog des télécoms&lt;/a&gt; © 2009 - 2026 by &lt;a href="https://www.linkedin.com/in/mathias-wolff-47a7941/"&gt;Mathias WOLFF&lt;/a&gt; is licensed under &lt;a href="https://creativecommons.org/licenses/by-nc-sa/4.0/"&gt;CC BY-NC-SA 4.0&lt;/a&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/cc.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/by.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/nc.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/sa.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;</copyright><lastBuildDate>Tue, 16 Jun 2026 17:35:19 +0200</lastBuildDate><atom:link href="https://www.blog-des-telecoms.com/tags/multi-agent/index.xml" rel="self" type="application/rss+xml"/><item><title>Qui écrit quoi ? Répartir les rôles entre humain, IA et outils déterministes</title><link>https://www.blog-des-telecoms.com/blog/qui-ecrit-tests-code-ia-outils-deterministes/</link><pubDate>Thu, 18 Jun 2026 09:00:00 +0200</pubDate><guid>https://www.blog-des-telecoms.com/blog/qui-ecrit-tests-code-ia-outils-deterministes/</guid><description>&lt;p&gt;&lt;em&gt;Article 3 de la série &amp;ldquo;De la spécification à l&amp;rsquo;exécution&amp;rdquo;. L&amp;rsquo;&lt;a
 href="https://www.blog-des-telecoms.com/blog/specification-executable-gherkin-proprietes"
 
 
&gt;article précédent&lt;/a&gt; traitait de la spec exécutable, c&amp;rsquo;est-à-dire de la manière de formaliser une intention sans ambiguïté. Ici, je passe au point suivant. Une fois la spec posée, qui écrit quoi ?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;La question utile n&amp;rsquo;est pas de savoir si l&amp;rsquo;IA remplace les développeurs. Je n&amp;rsquo;y gagne rien pour le travail quotidien. La question qui compte est plus simple. Dans le pipeline qui va de la spec au code, qui écrit les tests, qui écrit le code, et qui vérifie que la suite ne s&amp;rsquo;est pas dégradée en route ?&lt;/p&gt;</description></item><item><title>Who Writes What? Splitting the Roles Between Humans, AI, and Deterministic Tools</title><link>https://www.blog-des-telecoms.com/en/blog/who-writes-what-humans-ai-deterministic-tools/</link><pubDate>Thu, 18 Jun 2026 09:00:00 +0200</pubDate><guid>https://www.blog-des-telecoms.com/en/blog/who-writes-what-humans-ai-deterministic-tools/</guid><description>&lt;p&gt;&lt;em&gt;Article 3 of the series &amp;ldquo;From Specification to Execution.&amp;rdquo; The &lt;a
 href="https://www.blog-des-telecoms.com/blog/specification-executable-gherkin-proprietes"
 
 
&gt;previous article&lt;/a&gt; covered executable spec, that is, how to formalize an intention without ambiguity. Here I move to the next point. Once the spec is in place, who writes what?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The useful question is not whether AI will replace developers. That does not help my daily work. The question that matters is simpler. In the pipeline from spec to code, who writes the tests, who writes the code, and who checks that the suite has not drifted along the way?&lt;/p&gt;</description></item></channel></rss>