"seam" is apparently... according to Claude itself a term from 'Working Effectively with Legacy Code' by Michael Feathers which I have not read. All it took was for one sub agent to use this term and it stated using it everywhere all the time. I have not read the book and prefer other terminology but it only takes 1 sub-agent or 1 usage in the context before it poisons everything else.

▲

sudosteph 40 minutes ago | parent | next [-]

That's funny. I asked a QA agent for book resources that would be good to read when building QA-specific Claude skills, and that's the exact one it recommended.

▲

oooyay an hour ago | parent | prev [-]

An interface is an example of a seam in regular code. It's basically what forms architectural shapes that you can depend on for both design and testing.

▲

5 minutes ago | parent | next [-]

[deleted]

▲

chuckadams an hour ago | parent | prev | next [-]

It's a fairly good concise term ... load-bearing, even. /ducks

But even then, I think "boundary" was the more common term before some LLM decided it really liked "seam" instead.

	▲	SoftTalker 5 minutes ago \| parent [-]
		In architecture, a seam is not load bearing. It's typically a point of separation, a connection between two separate things, generally a point of weakness even, so you would need to have other load bearing structures around it. "Load-bearing seam" doesn't make any sense.

▲

tempest_ 24 minutes ago | parent | prev [-]

Yes, and I prefer that term because no one but claude ever talks to me using the word seam every other paragraph.

I have instructions which is confidently ignores to never use seam and instead say interface.