>with the word "seam" as it pertains to coding
I thought this was an established term when it comes to working with codebases comprised of multiple interacting parts.
https://softwareengineering.stackexchange.com/questions/1325...
No, it’s not an established term outside the mentioned books, beyond the generic meaning of the word.
I can't say it isn't, but I have been writing code since about 2004 and this is the first time I've become aware that this is a thing.
thanks for this.
> the term originates from Michael Feathers Working Effectively with Legacy Code
I haven’t read the book but, taking the title and Amazon reviews at face value, I feel like this embodies Codex’s coding style as a whole. It treats all code like legacy code.