> On the other hand, maybe I can convince people in my org to get better at software engineering by telling them its for the AI to work better.

Really good engineering practices are fundamental to get the most out of AI tooling. Convoluted documentation, code fragmentation, etc all pollute context when working with AI tools.

In my experience, just having one outdated word (especially if it's a library name) anywhere in code or documentation can create major ongoing headaches.

The worst part of it is trying to avoid negative assertions. When the AI tooling keeps trying to do "the wrong thing" it's sometimes a challenge to rephrase instructions for "the right thing" to frame a positive assertion.