In the enterprise, we are already adopting them. “Seam”, I term I’d never heard used before, is now not only our defacto way to describe the boundary between systems/workflows/components, it is encoded into our organizational roles and responsibilities descriptions.

I am the proud owner of several seams, and am considering giving them person-names. The empty space between my inventory APIs and their clients might be “Karen”.

I can’t say that Claude invented this; the same type of terminology cycling happens every few quarters based on what leadership is reading/being told by Gartner.

▲

rsanheim 3 hours ago | parent | next [-]

"seam" dates back to refactoring & software engineering literature that pre-date LLM use by 20 years -- see Working Effectively With Legacy Code for one example (https://www.oreilly.com/library/view/working-effectively-wit...). Its a great book, still use techniques from it everyday.

"load-bearing" I have never heard used for programming before Opus, and its incredibly annoying and over-used.

	▲	thewebguyd 2 hours ago \| parent [-]
		load-bearing was/is used frequently on the ops side of things, I assume the LLMs picked up from physical engineering texts or sysadmin type blogs.

▲

QuercusMax 3 hours ago | parent | prev [-]

I believe the term "seam" came from Michael Feathers' "Working Effectively with Legacy Code": “a seam is a place where you can alter behavior in your program without editing in that place”.

https://martinfowler.com/bliki/LegacySeam.html

Claude is using it a bit liberally, but not totally incorrectly.