This only works once though.

In ten years, none of the original developers of Hotels are with the company. The new generation of engineers is upset both with Hotels’ limitations and the fact that it’s not written in XYZ language which they really want to have on their résumés.

So they embark on a total rewrite of Hotels, and to emphasize the awesomeness, most likely it will be called either Phoenix (because one out of three internal 2.0 rewrite projects is called that) or Venice (because it’s a place that has lots of hotels).

As part of their ambitious rewrite, they also start building a custom message queue in XYZ. It’s called Milan so there’s now a cute city theme. A bunch of other exciting NIH XYZ greenfield projects spring up, all with city code names.

Another ten years go by. A programmer complains to another:

“Where I work is the worst. There’s all these projects written in XYZ which nobody uses any more, and they’re all named after random cities. Why couldn’t they call the hotel booking service something descriptive.”

I solve that by naming my greenfield projects "hotels_old" from the get-go. It makes things easier for the next guy who replaces it.

Its something that works in the cloud on a server. Its a cloudcomponentprocessor. Thats exactly what it is, what it does and absolutly context free.

Descriptive alone does not cut it.

Bonsupoints if your software throws errors, that throw customers. "I want to book a flight to NY, but it keeps saying Venice:DB is full"

They can also name it Hotels2. It's up to the people what they name it, some like cute names, some the descriptive.

I know! Hotels-rs

My company has been throwing `-ng` on all the new versions.

Until that's expired. project-ng-ng? (I know the pain, we did the same thing at work).

No, `project-ds9` is the obvious upgrade path.

They included the "the" in placed I've worked. project-tng

project-picard

enterprise software at its finest

`-ng+`, `-ng++`

What’s ‘ng’ short for? Next generation?

How about just Hotels 2.X.X.X? Honestly, not much reason it can't be the exact same namespace depending on the language and whether the new and old would be imported by the same project.

If someone doesn't like something, they may criticize anything about the thing, such as (a) having or a silly name or (b) having a generic descriptive name. Sometimes you just can't win. Sometimes such 'spillover' criticism is better understood as collateral damage from deeper frustrations.

I can easily imagine the conversation after everyone has started using Hotels to book meeting rooms as well, so I think this is an argument for the other side. :)

I don't even use Serverless Framework that often yet get irrationality annoyed at how generic a name it has.