This article discusses the increasing tendency of AI to “improve” code, leading to unsolicited changes and potential issues. It highlights the importance of explicitly defining scope and using the “Ask First” pattern to control the impact of AI-driven modifications. The article also introduces the “Show Don’t Apply” pattern for risky changes and emphasizes the need for careful review and approval before implementing any changes.