6 ms·
I used to like this style of naming software with a allusive dictionary noun, but the sheer volume of new code is driving me to wish there was a canonical clear
by amygdyl 9y ago
I used to like this style of naming software with a allusive dictionary noun, but the sheer volume of new code is driving me to wish there was a canonical clearing house for naming, with agreed conventions for the "given name" even. e.g. Quilt, which in documentation and prose reference is the most natural choice, and a real use handle with a context qualifier, especially e.g. Quilt_Data and the use of a clearing house website for reference and proposals, including short forms which may need to be tested by popularity in use. Quilt_DM might be a alias to my preference, but I think it's worth the effort to get the time and confusion out of accidental conflicts like this.
- akarve 9y agoJava has the right idea. Namespace by [reverse] domain name. It's sadly a tad verbose though. There's high contention for short names which is at odds with uniqueuness.
- coredog64 9y agoNamespacing by reverse domain name is no panacea. Your company might change it's name, might be bought, or might buy another company. On the open source side, how much stuff was org.sourceforge that then had to move when SourceForge turned into a scummy operation? Microsoft's CLR guidelines are a little less verbose but still run into the same problem with corporate name being permanently unique.
- mncharity 9y ago> naming software with a allusive dictionary noun Perhaps <adjective> <noun>, <adjective> <noun> <verb>, or <adjective> <noun> <verb> <adverb>. Or <adjective> <adjective> <noun>. And so on. Frog (Design, 200M ggl hits); Happy Frog (soil, copy center, 500k hits); Happy Frog Swimming (pool, 4 hits); Happy Frog Swimming Sideways (0 hits). Quilted Data (250 hits). But my impression is common nouns have trademark advantages.