coding practices - naming conventions

use descriptive names for namespaces, funcitons, global and local symbols

names should elaborate on the contenxt of the namspace, function data structure

avoid single character tor terse names - never use a single character name. if you cant think of a name, then you dont understand something fully.
For example if requireing clojure.alpha.spec into a namespace then use the alias spec.

If you have multiple libraries that could be used to do the same task, then use an alias that describes the purpose or intent of that library. This makes the alias retain its meaning when changing the library (and avoiding refactoring the whole namespace).

Single character names add more cognitive load when reviewing and working on existing code.
Single characters lead to conflct of meaning.

The issue names no file, test, or entry point, so first locate the repository guidance that covers coding practices and naming conventions. Update the relevant guidance to address descriptive namespace, function, symbol, and alias names; done means the stated conventions are documented without ambiguity.