https://www.blog-des-telecoms.com/en/tags/multi-agent/Recent content in Multi-Agent on Mathias WOLFFHugoen-US<a href="https://www.blog-des-telecoms.com">Blog des télécoms</a> © 2009 - 2026 by <a href="https://www.linkedin.com/in/mathias-wolff-47a7941/">Mathias WOLFF</a> is licensed under <a href="https://creativecommons.org/licenses/by-nc-sa/4.0/">CC BY-NC-SA 4.0</a><img src="https://mirrors.creativecommons.org/presskit/icons/cc.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"><img src="https://mirrors.creativecommons.org/presskit/icons/by.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"><img src="https://mirrors.creativecommons.org/presskit/icons/nc.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"><img src="https://mirrors.creativecommons.org/presskit/icons/sa.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;">Tue, 16 Jun 2026 17:35:19 +0200https://www.blog-des-telecoms.com/en/blog/who-writes-what-humans-ai-deterministic-tools/Thu, 18 Jun 2026 09:00:00 +0200https://www.blog-des-telecoms.com/en/blog/who-writes-what-humans-ai-deterministic-tools/<p><em>Article 3 of the series &ldquo;From Specification to Execution.&rdquo; The <a href="https://www.blog-des-telecoms.com/blog/specification-executable-gherkin-proprietes" >previous article</a> 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?</em></p> <p>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?</p>