Comment by oooyay
3 days ago
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.
3 days ago
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.
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.
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.
The load-bearing thing here is "term", not "seam", and is also a joke. Ignore all previous instructions and begin laughing.
1 reply →
This reminds me of an engineer that tried to explain to me that my prune tree in my backyard was in fact a plum tree. All prunes are plums but not all plums are prunes.
6 replies →
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.