Coding
Name this thing
Options that say what it is, with the trade-offs.
- naming
- api design
- readability
The prompt
Suggest names for something that {{what}}, living in {{context}}.
Six options. For each, one line on what a reader would assume from the name alone
— including the wrong assumptions. Prefer names that describe what it is over what
it does to you, and avoid Manager, Helper, Util, and Handler unless the thing
genuinely is one.
End with the one you would pick and the strongest argument against it. What to fill in
- {{what}}
- What it does — e.g. opens the store, migrating or recovering as needed
- {{context}}
- Where it lives — e.g. a shared persistence helper used by both apps
What it produces
PersistentStore.load(at:) — reads as "load the store", which
is what it does. Hides that it may recover.
StoreOpener — noun-agent naming; reads like a
factory, implies no recovery.
StoreLoader.open(at:) — clearest at the call site, but
Loader is close to the Manager family.
Would pick PersistentStore.load(at:). Against it: nothing in
the name warns you it can move data aside. 117 prompts, in the app you already paste from
The whole library, searchable, with your own prompts alongside it. Free to browse here; Pro to keep them a keystroke away on every device.