[raygelogic]

are we talking about project names or the names of classes and objects?

if it's projects, ideally the long-term architecture is well enough understood to give the thing a whimsical yet meaningful name (ideally not cryptic). building a page caching service? call it gutenberg or something to start. when it inevitably grows past scope, it's ok. no one will care if gutenberg also handles analytics callbacks or whatever.

classes really shouldn't change in scope, ideally, so it's probably better to be a bit more specific to their purpose.

overall this is a good hot take, if a bit broadly put.