MajorHavoc

So yeah, taken independently it's a better relationship image than most relationships in most shows, but in the context it's pretty horrible.

Absolutely. I think a lot of the audience realize that if they weren't a gay couple, we would see them with their shirts off together at every opportunity.

The silver lining is that the actors are so attractive and doing such a beautiful and convincing job, that the omission makes the show runners look prudish and silly.

Section 31 is pretty badass, right?

I have to say, I hated that. It feels like C suite "promote our upcoming show" meddling, to me.

"When I have a problem that phasers can't solve, I just kiss a beautiful alien. Then suddenly, I have a completely different problem!" - Jason Tiberius Kirk

Edit: I may have drifted into the Kelvin timeline...

but the most the gay couple gets is sitting next to each other, brushing teeth and a small kiss

While you're absolutely right, I think the record should show that tooth brushing scene is one of the sexiest scenes in television history. Those two have some serious on-screen chemistry.

The only issue disco has ever actually had is their serialized episodes.

And not spending enough on light bulbs in some episodes. I wondered if my TV was broken, at one point. Lol.

Thanks. I hate it.

Gonna go check my cinnamon.

But seriously, thanks.

Well that makes more sense, but it is still a lot of churn.

Sure, I mean it risks a lot of churn, but it hasn't happened, in practice.

My team will debate the merits of a change until the cows come home, but they know that if they actually decide to make the change, I'll expect them to put in all the necessary work to do it right. Ironically, that tends to curb their appetite for perfectionism.

Thankfully we're all pretty much of like-mind. Nothing changes from project to project in the naming realm.

Yeah. Same here. That's really why I get away with technically allowing a change during any retro. My teams appetite for refinements settled down after our first four sprints as a team.

Things might get interesting again, when we make our next hire; but I consider that part of the onboarding process. It should be worth the trouble just in case the new hire brings brings smart new practices we might have been ignoring. And whether anything changes or not, it creates a time and place for the new hire to argue their differences with the team.

We discuss naming conventions whenever we start a new project, and then it's locked in.

That's very practical, and really accomplishes the same net effect as my team's policy, with less theoretical risk of thrashing.

A possible difference is that sometimes my team will insist on a refactor of some old code to update to the latest standards, at the start of a new project updating an old product.

As long as the code test coverage is acceptable to me, I'll green light that effort as part of sprint zero.

We have tens of thousands of files in the project I'm in charge of, so we'd never consider such an extensive refactor.

Oh yeah. I would probably use my manager veto in that case. At some point it's just too much work to verify the change.

We do have one big repo that we're breaking up over time, and I insist that such changes be limited to the current actively developed component. It's a unique case, because the vision for the repo is to get smaller as parts of it are decoupled (and released as open source). So we don't deeply care if different modules have mildly different code standards, since they're destined for separate public repos, in the long run.

I did do away with BEM when I started, because I despise that clusterfuck of a convention for more reasons than I care to explain here, but I waited until a new project to do it, and everyone agreed with me.

That's some holy and righteous work you accomplished. All future developers on that effort owe you a debt!

Lol. Oh, right. I was kind of asking for clarification if tie fighters count, but I guess that's a moot point. I had not thought about the impact of the battle at the start of Ep IV - probably leaves everyone too black out drunk for the rest to matter.

This is perfect. Thank you for this.

Yeah. Their own lawyers have the best chance, but there's so many pages, combined, I wonder if even one of their lawyers has read everything

Great write up. Thanks for sharing it here.

You might as well not have a naming convention then, since the project is going to be full of different conventions.

Oh, I skipped this. Lol. Obviously not. As a team, they can implement whatever convention change they want, every two weeks.

As manager, I expect them to update all active projects, in their entirety, to the new convention, each time.

And as I mentioned in my other comment, if their test coverage isn't at a level that makes me confident in that kind of global change (70% tends to be plenty), then I reserve the right to table it - until they bring the test coverage up (on all impacted projects).