"Seam" is a term from a 2004 book on legacy code. Almost nobody used it until coding agents started saying it constantly, and now it's in your repo too. Annoying in a code comment. In a ticket summary your triage team reads, it's a bug that never raises. ๐˜ƒ๐—ผ๐—ฐ๐—ฎ๐—ฏ๐—ด๐˜‚๐—ฎ๐—ฟ๐—ฑ catches the drift in a Pydantic AI agent output before the write lands: pydantic.io/KN3Lh

Sep 4, 2026 ยท 9:46 PM UTC

3
5
34
3,751
Sort replies: Relevant Recent Liked
Replying to @pydantic
gpt 5.4 was fan of seam word too. it had been using it very frequently... the funny part is it's one of my top used words. seems like i became officially a clanker.
1
118
Replying to @pydantic
A seam is only worth the word if you can run the old path and the new one at the same time and compare. That was the point in Feathers' book: find a place to change behavior without editing in place, so you can get a test around code nobody understands yet. When an agent says seam it usually means "I found somewhere to inject," which is a much smaller claim. The questions I care about are whether you can flip it back without a deploy, and whether anyone can tell which path produced the number in the report.
1
112