Stop naming software libraries. Forever. I mean YOU.
Being a C++ developer who tends to get his kicks writing compilers and signal processing software, I don't often get to play with the wonderful world of 'using other people's really fucking stupidly named libraries'.
( That's ignoring the C++ 'std' namespace - you just go.. numb after a while ).
This: 'huge issue with accordions' I know what those words mean, but WTF is it? Well, you can easily work it out can't you?
And that's a second of my time when I could have been thinking about breakfast, or cheese, or sunflowers or pies or something better. That is a tiny little example, not even that bad. There are way way worse.
Name. Engineering. Stuff. After. What. It. Fucking. Does.
'But how do I make my library stand out if I don't name it something cool?!' you ask. Of course, you want people to use your stuff don't you! Well, when I'm looking around for some bit of code to handle a certain task, I'm looking for what it does, not your fancy name which I don't even fucking know yet!
And if you do what every other thing does.. why would you expect anyone to use your code? I'd pick the one with the more boring name every time.
It's probably better engineered due to being used and developed by more people.
( as a note, I found it hard to remember what stupid names I'd seen, due to the fact that when I see one, I immediately retire that name from my working memory ).
2087
snowghoul
stormborns
janainaart
gummygunk
origamiaround