'Verified' mudou de significado: o que agentic engineering exige de times de desenvolvimento
The concept of 'verified' in programming has evolved due to advancements in AI agent throughput. It now emphasizes automated checks over human review, necessitating a shift in how developers ensure code quality. The focus is on creating robust verification systems rather than solely increasing code generation speed.
- ▪The term 'verified' has changed from meaning 'read by you' to requiring checks by tests and automated tools.
- ▪Chris Parsons argues that verification has shifted from human review to automated processes as AI-generated code volume increases.
- ▪Birgitta Böckeler highlights that computational sensors provide more reliable quality assurance than human review.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 1136947) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Bruno Santos Posted on May 27 'Verified' mudou de significado: o que agentic engineering exige de times de desenvolvimento #ai #architecture #programming #development Nos Fragments de 29 de abril, Martin Fowler reuniu três artigos sobre programação agentiva que chegam à mesma conclusão. O investimento que importa não está em velocidade de geração de código, mas em verificação, harness e legibilidade do código para agentes.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
