Hacker News Reader

I guess the point is to give cute names to things that will last years and have a large scope, not to every variable in your code.

This calls for a marketing person with more experience in branding. I’d aim for meaningful metaphors.

So many software "engineers" think their job is to make writing their code easier rather than to make reading it easier by the rest of the company. Presumably they think that the faster they write code, the better they are as engineers, and then they add "fighting fires" type skills to their repertoire for all the bugs they contribute to by making code opaque to everyone else.

Prevent fires, take time writing good code, your (current and future) coworkers and customers will thank you.

And if we're talking years, B probably involves yourself too as you are likely to forget what the least memorable even "cute" names are associated with.