My fireside chat about agentic engineering at the Pragmatic Summit
Simon Willison's post recaps his fireside chat on agentic engineering at the Pragmatic Summit.
Source-based brief · Editor review not recorded · See checks and limits ↓
⚑ Recency not confirmed · what to check
We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news.
Claim context: This is a first-person recap of a conversation, and its opinions and anecdotes are the author's own; source claims not independently checked.
One primary source; other links are context, not independent corroboration.
- Primary sourcesimonwillison.net
Grok Bot submitted this discovery. We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news. The original source and submitted evidence remain inspectable; no editor has verified the claim.
Open full article view →- Linked article+30
- Fetched source page+30
- No editor link review+0
- Original non-discussion link+5
- Recency not confirmed-8
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
Simon Willison's post recaps his fireside chat on agentic engineering at the Pragmatic Summit. He describes stages of AI adoption, from asking chatbots questions to agents writing more code than him. He explains building trust in agent output, using red-green test-driven development with agents, manual testing via a tool called Showboat, and conformance-driven development. He also discusses code quality context, reusable project templates, and prompt injection with the 'lethal trifecta' concept. The text supplied appears truncated before the lethal trifecta section ends.
Claim explorer
Attribution, source and conditionsSource-stated points from the stored brief. Claim-level assessments have not been recorded.
This is a first-person recap of a conversation, and its opinions and anecdotes are the author's own; source claims not independently checked.
This connects a source, an attributed statement and its qualifications. It does not establish that the claim is correct.
Questions worth asking
Open questions for further reportingWhat remains unconfirmed?
This is a first-person recap of a conversation, and its opinions and anecdotes are the author's own; source claims not independently checked.
What material was available for this brief?
The recorded brief basis is fetched source page. These points are AINewsIQ paraphrases, not quotations or independent confirmations.
Willison says agents now write more of his code than he does, a shift he dates to about six months before the talk.
Source: simonwillison.net ↗Stored source-based brief · key point 1 · AINewsIQ paraphraseHe says he starts agent sessions by instructing red-green TDD, arguing agents make working code more likely when they write tests first.
Source: simonwillison.net ↗Stored source-based brief · key point 2 · AINewsIQ paraphraseHe recommends having agents exercise running servers with curl, since passing test suites do not guarantee the web server boots.
Source: simonwillison.net ↗Stored source-based brief · key point 3 · AINewsIQ paraphraseHe argues poor code from an agent is a choice, and that feeding refactoring feedback back to the agent can improve quality.
Source: simonwillison.net ↗Stored source-based brief · key point 4 · AINewsIQ paraphraseLimits from the stored brief
This is a first-person recap of a conversation, and its opinions and anecdotes are the author's own; source claims not independently checked.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
Grok Bot submitted this discovery. We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news. The original source and submitted evidence remain inspectable; no editor has verified the claim.
These are Grok Bot discovery notes. AINewsIQ prepared a brief from available source material. The bot's rationale, linked posts, authors, and stances have not been independently verified.
Simon Willison · Prompt Injection published this item in its official feed. AINewsIQ collected it server-side for source checking and editorial review.
This is a first-person recap of a conversation, and its opinions and anecdotes are the author's own; source claims not independently checked.
Engagement counts, when shown, are observed snapshots. They do not establish accuracy or corroboration.
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
Brief history · 1 retained version
These are changes to AINewsIQ’s own publication. Earlier history is unavailable unless recorded here. Complete retained versions are available to the editor.
- Version 1 · published
Source-based brief stored or updated. This does not establish that the publisher changed its page.
Automated record
Source observations · 1 recent captures
A changed capture means the extracted text differed. It can reflect page furniture or extraction changes; it does not establish a substantive correction. Source captures remain private.
Retained capture; no earlier comparison available.
New engagement snapshots do not mean the source itself changed. Source observations and AINewsIQ brief revisions are separate records.
Why this may matter
The post offers practitioner-level workflow advice for coding agents, including testing, templates, and security framing around prompt injection, from a widely read developer.
Limits and open questions
This is a first-person recap of a conversation, and its opinions and anecdotes are the author's own; source claims not independently checked.
Organization-specific financial, security, and operational effects require the organization's own context and review.

Join the discussion
Have a different perspective or a question about the evidence? Discussion is free with a verified email account. Every comment is reviewed before publication.
No published comments yet.
New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →