• MajorHavoc@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    2 days ago

    Oof. This is a pet peeve of mine.

    As manager, I shut this conversation down via direct messages to each team member involved.

    I remind them that they agreed during retro to live with the current set of decisions for exactly two weeks until next retro.

    I don’t dictate much, but I do dictate that Slack isn’t an acceptable place for this kind of discussion, on my team.

    The only related thing, that belongs in slack, on my team, is a link to the current accepted team standard - which will be open for review and changes again during next retro.

    Alternately, if there’s no strandard for this yet then my team knows they’re encouraged to wing it until we discuss at next retro.

    And yeah, I’ve had to open an issue to revisit a variable name after retro, lol.

    My team are an opinionated bunch, and they’re often perfectionists.

    • AwkwardLookMonkeyPuppet@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      17 hours ago

      You allow naming schemes to change every two weeks? That’s just insane! You might as well not have a naming convention then, since the project is going to be full of different conventions.

      • MajorHavoc@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        16 hours ago

        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).

        • AwkwardLookMonkeyPuppet@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          6 hours ago

          Well that makes more sense, but it is still a lot of churn. I guess it’s fine in a project where you can change it all in a couple days. We have tens of thousands of files in the project I’m in charge of, so we’d never consider such an extensive refactor. We discuss naming conventions whenever we start a new project, and then it’s locked in. Thankfully we’re all pretty much of like-mind. Nothing changes from project to project in the naming realm. 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.

          • MajorHavoc@programming.dev
            link
            fedilink
            arrow-up
            0
            ·
            edit-2
            4 hours ago

            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!

            • AwkwardLookMonkeyPuppet@lemmy.world
              link
              fedilink
              English
              arrow-up
              0
              ·
              4 hours ago

              That’s cool that you take input from new-hires and consider the viewpoints they bring to the team. It’s always annoying to be excited about a new job, and then be told “this is the way we do it, and that’s final”.

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

              Ha! Thanks! They were using it because that’s what Adobe recommends, and I made a very strong and opinionated case as to why Adobe needs to pull their heads out of their asses. Haha. Unexpectedly, everyone agreed with me.