| ▲ | 3eb7988a1663 4 days ago |
| Missing - new leadership will push out the old guard and replace them with friends - 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 |
|
| ▲ | claw-el 4 days ago | parent | next [-] |
| > - 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. |
| |
| ▲ | charles_f 4 days ago | parent | next [-] | | 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 | | |
| ▲ | pavel_lishin 4 days ago | parent | next [-] | | 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. | |
| ▲ | cenamus 4 days ago | parent | prev [-] | | 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 |
| |
| ▲ | bentinata 4 days ago | parent | prev | next [-] | | 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. | | |
| ▲ | claw-el 4 days ago | parent [-] | | “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” |
| |
| ▲ | pavel_lishin 4 days ago | parent | prev | next [-] | | 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. | |
| ▲ | poslathian 4 days ago | parent | prev [-] | | 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. |
|
|
| ▲ | protocolture 4 days ago | parent | prev | next [-] |
| >- new leadership will push out the old guard and replace them with friends My mortal nemesis brings his whole helpdesk and development team across slowly whenever he starts at a new business. Which is crazy, because as far as I can see the benefit to him is simply loyalty. They dont complain or go over his head when he fails to deliver. I have receipts from staff who worked with him at other businesses where he just follows the same pattern. 1. Identify problems (The problem is the lack of a new CRM from a big microsoft partner.) 2. Spend lots of money to fix the problem (Free trips to vegas 3 times per year thanks to the CRM partner and microsoft) 3. Fail to deliver the CRM (The problem was not a big enough scope) 4. Rescope the project. (more bennies) 5. Would have failed to deliver it again however I just got a new job transforming another business enjoy your crapheap. |
|
| ▲ | linkage 4 days ago | parent | prev | next [-] |
| We have an internal infrastructure-as-code library built on Terraform CDK that automatically provisions monitoring resources in Datadog and Pagerduty. One day, I simply removed a required argument named 'team', realizing that it has a half life of 7 months. |
|
| ▲ | vjvjvjvjghv 4 days ago | parent | prev [-] |
| Whenever I see or an initiative have "Excellence" in its name I know it's BS |
| |
| ▲ | vineyardmike 4 days ago | parent | next [-] | | Everywhere I've worked that added "Excellence" to a name did it when they really wanted to say: "This team wasn't working hard enough before , so I told them to be better now". | | |
| ▲ | ericbarrett 4 days ago | parent [-] | | Agreed, and a great example of the signal often hidden in anodyne corporate titles. |
| |
| ▲ | 3eb7988a1663 4 days ago | parent | prev | next [-] | | "Excellence" was a huge miss on my part! | |
| ▲ | koolba 4 days ago | parent | prev [-] | | Cross functional excellence is an important KPI when you want to expand your market leading synergies. |
|
