> "I avoided implementing this correctly because of migration concern for existing installations of this code I'm writing right now"

This one grinds my gears so bad, probably 1/4 of my job at this point is telling an LLM (either in my own editor or in review comments for someone's MR) "how about we do this right _before_ merging it, eh?".

Or:

foo = abc

<Maybe 4-10 lines of code>

if foo != None:

    ...

In my experience giving it "rules" not to do this does nothing, but a separate pass (could be by a different model but really just fresh context is enough) does okay