> Naming software experiments is a barrier to entry for me. Typically, I need to come up with a name before I can even create a project. Using numbers removes that burden and lets me start with a readme or a bit of code. This is the first of those numbered experiments.
(From the project readme on GitHub)
I have the exact same issue, not only for projects, but also servers, structures or variables. If the name doesn't clearly communicate the purpose, I can't go ahead. What helps me is settling for an unrelated naming scheme like greek gods or NASA missions (servers), going with concepts, like batch-importer or note-app (projects), or choosing the first generic name that occurs to me, eg. EncodingManager (code structures). The only important thing is a simple path to renaming stuff later on as its purpose becomes clear :)
(From the project readme on GitHub)
I have the exact same issue, not only for projects, but also servers, structures or variables. If the name doesn't clearly communicate the purpose, I can't go ahead. What helps me is settling for an unrelated naming scheme like greek gods or NASA missions (servers), going with concepts, like batch-importer or note-app (projects), or choosing the first generic name that occurs to me, eg. EncodingManager (code structures). The only important thing is a simple path to renaming stuff later on as its purpose becomes clear :)