New folders for one or two files; layer trees for small apps
Files and folders: one of the ways AI coding agents bloat software, from lessloc's pattern catalog. lessloc catches it as new-folder.
What makes new folders for one or two files and layer trees for small apps a bad practice?
The standards that call it a bad practice: Ousterhout: shallow modules; Martin's Common Closure Principle.
What does lessloc do about new folders for one or two files and layer trees for small apps?
lessloc catches it as new-folder. Framework route folders (Next.js, SvelteKit, Expo) are exempt.
new-folder(tier 2): A new folder with one or two entries, or an examples or demo folder nobody asked for.
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. - 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. - Moving or renaming files without a reason: lessloc catches it as
moved-files. - Secrets: a committed .env, API keys, private keys: lessloc catches it as
secret.