Hacker News Reader

Comment by claw-el | Hacker News Reader

> - groups get renamed for the Nth time in N years. People continue to do the same job, but now the department has an additional "Innovation", "Discovery", or "Leadership" inserted into the title

Sometimes, I wish we name the team ‘Pikachu’ and continue on working. This way, others would know the name does not really matter, so they would stop changing the name. The amount of work to change the documentation and lets others know our team changed name has caused a lot of unnecessary work.

View on HN

God do I hate teams and systems with cute names. It's all cute and fun until you're the one from another team who needs to integrate with you and decode what Pikachu and Tyrion are responsible for, and discover that Fassbender is just a nickname for a Postgresdb maintained by the "It's over 9000" team. AuthService, CacheService, Db and EntrypointTeam are perfectly fine names. I don't care that namespaces are still aligned with 4 names ago, as long as I can somewhat infer what things do based on their names

How much I hate cute sprint names. How is "sweet summer breeze" better than 2023-03? At least I know if it's current or five years old

The upside of having cutesy team names and mascots is that nowadays people just throw something into an AI image generator prompt, and you get a mascot that has clearly been trained on furry fetish art, and during Zoom meetings you get to look around and see who else is trying to stifle laughter when their slide comes up on a presentation.

It won't gonna change how people (mostly management) see the name. I've seen whole empire named after Pokemon, only for another round of restructure that will change teams name to another Pokemon.

While talking to friends at other empire:

> I've been digging around, who are the members of Ludicolo?

> Oh, we've renamed to Felbat.

“Manager, no, you don’t get it. We can’t just name it ‘Felbat’. Pikachu evolves into Raichu, not Felbat. Even then, Pikachu don’t really want to evolve”

I was on a pair of teams (why two teams? who knows) that worked with a given project for about five years. Every year or so, we'd change names - so I've been on "$PROJECT Access", "$PROJECT Insights", and some third thing I forget the name of.

I unironically suggested we just call ourselves $PROJECT RED and $PROJECT BLUE, and refer to the entirety of the team-pair as $PROJECT PURPLE. Nobody liked that, but it is what we ended up calling ourselves internally.

This comment gives me mixed feelings and some nostalgia for when our company was < 100 people and one of the core software teams was called “meow” - today we call it human robot interaction.

Reply on news.ycombinator.com