markdown guide

Well, I recently made a little tool for testing APIs and I called it ... (drumroll please) ... "api-tester" !

I mean, who says you need to give it a fancy name? At least it's immediately clear what it does (more or less).


For internal/personal stuff that will never be published, I just give it a generic but descriptive name.

For stuff I actually intend to publish, if the intenral approach results in a name that appears to be unique enough to not cause any confusion, I just use it. Otherwise, I come up with some word or phrase that seems to fit the project, and then try to find a linguistic permutation of that that I like (IOW, try the same word or phrase in other languages, try it with various synonyms, etc).

In most cases though, I use a temporary name based on the internal approach until I actually get to the point that the project is most of the way done.


Consider using the name "unnamed-project" and get started building it. Once you're done you'll have a better idea of how to brand it, and can easily change the name pre-launch.


That's what it was when I started! But considering I couldn't name it something that excited me, that's when I lost motivation for it.

Classic DEV Post from May 21 '18

Who's looking for open source contributors? (May 21 edition)

Ross Henderson profile image
Oracle Developer using SQL, PL/SQL and Web Development to build Application Express apps. Musician, gamer and dog lover.