3 ms·
Don't worry about the name. A bad name won't hurt your project. What will hurt your project is calling out how bad your name is in the project description. You
by mkoryak 8y ago
Don't worry about the name. A bad name won't hurt your project.
What will hurt your project is calling out how bad your name is in the project description.
You have a short sentence to sell me a reason to read more of your readme but instead you use that time to point out the issues with the project name.
(I wrote a thing called floatthead which is an aweful name, but no one has ever complained about _that_)
- ironmagma 8y agofloatthead isn’t an awful name. It’s essentially meaningless. Bad names can make projects not take off as much as they would have due to ambiguity, unpleasant associations, and difficulty of expressing support. We often don’t hear about those projects precisely because they don’t succeed.
- jspash 8y agoIntroduce the project like this "Debucsser, CSS debugging made easy" (pronounced de-buk-sir) better yet (or not) You could find someone to draw a little cartoon in the style of the New Yorker showing a herd of deer, one of them with enormous antlers, and two men with hunting gear (a butler and his master, or a king and his servant. something like that). The caption would read. "Which one do I shoot?" "De buck, sir. Only de buck."
- lucagez 8y agoHaha so funny, thank you
- cjohansson 8y agoCalling out the bad name was what really got my attention for this project, in a good way, so I don't think it's generally a bad practice