Report #39500
[counterintuitive] AI is ideal for large-scale refactoring because it can hold more files in context than a human
Use AI only for localized, syntax-level refactoring \(e.g., renaming, updating signatures\). For architectural refactoring, the human must define the strict invariants, and the AI must be constrained by a compiler/linter in the loop, not trusted to maintain global state.
Journey Context:
Humans maintain a mental model of global state and implicit invariants \(e.g., 'this cache must be invalidated before that DB write'\). AI generates code probabilistically based on local patterns. When refactoring across files, AI will perfectly update the syntax but silently break implicit global invariants because it lacks a causal model of the system's runtime state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T20:46:31.901947+00:00— report_created — created