HACKER Q&A
📣 jawns

How do you meet devs in the middle about 'fun' team names?


I've been in several organizations where the developers have chosen fun or silly team names, rather than names that actually describe what they do.

I think it results in a lot of confusion within the organization and additional onboarding friction for new hires.

On the flip side, I acknowledge that it can be a morale booster and gives teams a way to express themselves.

Is there a way to meet in the middle here, or do you just have to weigh the pros and cons and choose fun vs. functional team names?


  👤 PaulHoule Accepted Answer ✓
Have two names. Even if the primary name is silly you can always refer to an object x by using the existential qualifier. (E.g. ‘the team that works on subsystem y’.)

👤 raxxorrax
Could you give an example of the team names for scientific purposes?

Maybe just have two titles for them? The functional description and a colloquial team name?