I recently posted to the Artsy engineering blog about why projects need code names.
At Artsy, our systems have peculiar code names like Gravity, Pulse, and Vortex. There’s a persistent learning curve as you contribute to different repositories or as new services get created. Numerous times, I’ve wondered: are code names worth the trouble?
It took me a while to be convinced of code names’ value, and I even propose some rules for your own project naming scheme: