Earlier quoted context omitted.
I find they are very concerned about ever pulling the trigger on a change or deleting something. They add features and codepaths that weren't asked for, and then resist removing them because that would break backwards compatibility. In lieu of understanding the whole architecture, they assume that there was intent behind the current choices... which is a good assumption on their training data where a human wrote it,…
// deprecated; use ThingTwo instead type Thing = ... // deprecated; use ThingThree instead type ThingTwo = ... // deprecated; use... I do frequent insistent cleaning passes with Claude, otherwise manually. It gets out of hand so fast This is one reason why it blows me away that people actually ship stuff they've never looked at. You can be certain it's riddled with craziest garbage Claude is holing away for eternity
> * ABSOLUTELY DO NOT use `@deprecated` on anything unless you are explicitly asked to. Always fully refactor and delete old code as-needed instead of deprecating it
https://github.com/yokuze/aix-config/blob/f5094b5c5169261fae...