I HATE clever names. Clever names are fun. They tickle that little corner of the developer brain that delights in obscure trivia, and makes everyone smile and n

I HATE clever names. Clever names are fun. They tickle that little corner of the developer brain that delights in obscure trivia, and makes everyone smile and nod and pat themselves on the back as they celebrate their cleverness. Fast-forward 2 years, and no one can remember what thing does what. 1. New devs on the team have to learn a long list of acronyms and code names, slowing down their ramp-up. 2. Trying to find information is nearly impossible, since you can't just keyword-search for "test" and see all the related dependencies, but instead have to reference some internal code sheet. 3. Duplicate work often results, since you can't easily see the thing you did last time, and if you forget where you put it you'll never find it again. "Wait, is this Kraken? Or was that supposed to be Ahab? Is Nemo the search indexing service or was that Marlin?" In my teams, I've always dictated boring but descriptive project naming, along with a nice README that includes a description of what the thing does, why it exists, and a handy list of keywords in case you try to find this information later. BTW this also works well for class names, variable names, etc. Or you could, you know, do something fun and not boring. And have all the developers who come after you curse your name.