Moving or renaming files without a reason
Files and folders: one of the ways AI coding agents bloat software, from lessloc's pattern catalog. lessloc catches it as moved-files.
What makes moving or renaming files without a reason a bad practice?
The standard that calls it a bad practice: Google engineering practices: separate refactoring changes.
What does lessloc do about moving or renaming files without a reason?
lessloc catches it as moved-files.
moved-files(tier 2): Files moved or renamed when the request did not ask for a refactor.
Related patterns
The other patterns in Files and folders:
- Scratch, backup, copy and harness files: lessloc catches it as
junk-fileand refuses it before it lands. - Caches, build output and logs about to be committed: lessloc catches it as
junk-file. - CI workflows and Dockerfiles nobody asked for: lessloc catches it as
unrequested-file. - Tiny one-function files; file-per-concern splits: lessloc catches it as
tiny-fileandnew-files. - New folders for one or two files; layer trees for small apps: lessloc catches it as
new-folder. - Junk-drawer utils and helpers modules and folders: lessloc catches it as
junk-drawer. - Vague names (process_data, handle): lessloc catches it as
vague-name. - Secrets: a committed .env, API keys, private keys: lessloc catches it as
secret.