Finding good names
It happens all the time. I am about to start a new project and I can't find a good name. I could postpone the decisions until publication. With my completion rate, that would save me a lot of thinking. Still, the name of a project, a programming one at least, is scattered all over the place from the start: you create a tree in your cvs/git/svn, you create a package/namespace/module in your programming environment and you write the project's name in the documentation (at least you intend to). You can change the name later but you save a lot of work if you start with the right one.
There was a time when you could pick a random word from the dictionary and be done with it. Today, it seems, all the real words are taken, even vellication. Here I use a widely accepted definition of "taken": is the .com owned by someone else. There are other root domains (.net, .org, .info) but the squatters bought the most of the dictionary there too. If we don't limit ourself to the dictionary, why should we after all, combinatorics saves the day. There are just to many ways to put letters together. Squatters can buy all the tree letter acronyms but that's as far as they can get.