Re:Inheritance was invented as a performance hack
by jollyllama on Thursday May 08, 2025 @09:03AM
(#43925718)
So if you've got a data object, defined in multiple places in a sprawling codebase, that you want to change, are you going to trust the LLM to find them all, and not miss a single one?
Re:Inheritance was invented as a performance hack
by josephg on Thursday May 08, 2025 @09:32AM
(#43925956)
Why is your data object defined in multiple places in your codebase? And why aren't you using your IDE to change them all at once?
Re:Inheritance was invented as a performance hack
by jollyllama on Thursday May 08, 2025 @10:05AM
(#43926208)
> Why is your data object defined in multiple places in your codebase?
Because that's the negation of my premise which you disagreed with: "Keeping to the DRY principle is also more valuable in the age of AI when briefer codebases use up fewer LLM tokens."
> And why aren't you using your IDE to change them all at once?
It sounds like you're assuming that they're all defined in the same way that you can catch them with a search.
Re:Inheritance was invented as a performance hack
by actionfromafar on Thursday May 08, 2025 @12:36PM
(#43927944)
So everyone is incentivized to increase sprawl until the equilibrium is found.
The cost of working with code is much lower with LLMs than with humans and it's falling by an order of magnitude every year.