-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Think up a better name #10
Comments
I like prospector or object_prospector or gardener or weeder or object_pruner but I do like latent object detector as a description of what it does. lod_runner? (latent object detector runner), in the spirit of roodi (ruby object-oriented design inferometer) FWIW, I have a list of other code analysis tools up on the metric_fu wiki, for thinking about names, maybe |
lod_runner would /have/ to be pronounced "load runner" for obvious reasons. |
@BanTiK suggested "snuffle" because it sniffs out hidden things, like a pig finds truffles by smell |
I like the association with (code) smells as well |
How about "smelly_cat"... smelly because it smells code and cat because ruby developers are obsessed with cats. And also smelly cat is a famous song(which had really nice music) in a popular TV show 'Friends'. |
As @BanTiK can attest to, I've never really liked the name "latent_object_detector" but was never able to come up with something better (ironic, I know.) This might almost be a priority for me before any further release (especially a CLI release)
Names relating to:
The text was updated successfully, but these errors were encountered: