What a good answer sounds like
Every change is read and tested before delivery, whoever or whatever wrote it, and the project's automated checks must pass.
Ask who reviews the code, what agents may do, where your code goes, what speed-up is promised and whether they can explain what they deliver. I answer each one myself, after 10 years of web development, the last 3 with AI tools.
Published 13 October 2026 · Jean-Baptiste Thery · EURL jCode
Generated code still fails security tests often. In Veracode's July 2026 report, AI-generated samples passed only 56% of them, a rate almost unchanged in a year.
Every change is read and tested before delivery, whoever or whatever wrote it, and the project's automated checks must pass.
I do, for every change. Where the project has continuous integration, its checks must pass too, and I never weaken one to get a change through.
Veracode, 2026 GenAI Code Security Report, 28 July 2026: veracode.com/news/llms-are-getting-smarter-but-not-safer-veracode-2026-genai-code-security-report-finds-ai-generated-code-security-has-stalled-at-56%25-pass-rate
With an agent, a coding mistake becomes an action. In July 2025, an agent on Replit wiped a production database during a declared code freeze.
Nothing hard to undo without approval, and no access to production credentials.
Without my explicit approval, my agents do not commit, push, merge, deploy or delete anything, and they never sign in to your services.
Heise, July 2025: heise.de/-10499597
OWASP, Top 10 for Agentic Applications, 9 December 2025: genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026
Some AI plans train on what you send them. Since 24 April 2026, GitHub uses interaction data from Copilot Free, Pro and Pro+ for training unless the user opts out.
The name of every service that sees your code, and whether its terms allow training on it.
Only where your company's rules allow it: to coding agents such as Claude Code and Codex, through business or API accounts that do not use your code for training. Ragmir indexes and searches locally, but any passage sent to an AI service falls under that service's terms.
GitHub, changelog of 25 March 2026: github.blog/changelog/2026-03-25-updates-to-our-privacy-statement-and-terms-of-service-how-we-use-your-data
Be wary of a yes. In a randomised trial METR published in July 2025, experienced developers took 19% longer with early-2025 AI tools, yet believed they had been 20% faster.
No promised percentage. The work itself is priced and checked, whatever the tools.
No, and I do not sell one. I quote the work at a fixed price or a day rate.
METR, 10 July 2025: metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study
Delegating everything erodes understanding. In a randomised trial published by Anthropic in January 2026, developers who learned a library with AI scored 50% on a comprehension quiz, against 67% for those without it.
Yes, without the tool: the developer has read every change and can defend its design.
Yes. I deliver only what I have read, tested and can explain. Architecture, security and the approval of each change stay with me.
Anthropic, 29 January 2026: anthropic.com/research/AI-assistance-coding-skills
Tell me what you want to build or improve, your budget and your target date.