Back to the radar AI-Assisted Development

InfoQ Online Cohorts Address AI Security and Coding Agent Verification

A look at two InfoQ online certification cohorts covering security and privacy decisions in production AI systems and the verification needed when coding agents work in existing codebases. By Artenisa Chatziou

A look at two InfoQ online certification cohorts covering security and privacy decisions in production AI systems and the verification needed when coding agents work in existing codebases. By Artenisa Chatziou

In context

  • Topic: Desarrollo con IA — Copilotos y agentes en el ciclo de desarrollo de software.
  • Source: InfoQ
  • Published: 30/09/2026

Continue reading at the original source →

Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.

Why it matters

When a tool appears promising faster development, the useful question is not how much code it generates but how much work it generates downstream. Tests, review, security, technical debt, incidents: that is where the promise gets paid or charged.

I distinguish between accelerating an experienced developer and accelerating someone just starting. In the first case the tool multiplies judgement; in the second it multiplies the lack of it. Adoption policy has to acknowledge that difference or the codebase fills with plausible, wrong code.

What usually goes wrong

What usually goes wrong is that review does not grow at the same rate as production. The team generates twice as much and still has the same two people reviewing, who get tired, start approving faster, and three months later quality has dropped without any indicator showing it yet.

What to watch

  • What happens to code review: if the assistant produces more, somebody has to read more.
  • What happens to tests — generating code without generating tests only moves the problem forward.
  • Where the source code travels when the assistant is used, and what the contract says about it.

How I read this entry

If I were rolling this out, I would do it with written rules: what can be generated, what always gets human eyes, and what is off limits to an assistant — typically anything handling money, identity or personal data. Rules give freedom, they do not remove it.

This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Share
Source. InfoQ

Comments

No comments yet. Yours can be the first.

Plain text only, no links. No email is requested. Comments are reviewed before they are published.

Living through this in your own team?

Open the chat and tell me how you're handling it. I'm interested in comparing notes.

Keep reading

More entries from the radar

See all
Darinel Ortega Online · I reply during the day
Today
Hello. I'm not selling anything here: this is for exchanging knowledge about technology.
Write whatever you like — you can send text, images or documents. Messages reach my console and I reply from there.
You are writing outside working hours. I will read you as soon as the day starts.

An open conversation to share knowledge. Messages reach my console and I reply from there.

Let us book a conversation

Pick the day and time that work for you. Thirty minutes, no sales pitch.

Video call

For a video call, just ask for one here and I'll send you the session link.