Thread

1. LunicLynx · 1790545264 · focus · HN ↗

   Unfortunately this often represents the only feedback given by the people in those „higher“ positions.

   „The indent is wrong here“

   „Comments should end with a period“

   Because this kind of feedback is and was always easy.

   1. parpfish · 1790545674 · focus · HN ↗

      If you get feedback like that, it’s time for your team to get automated linting/formatting

      1. refactor_master · 1790553541 · focus · HN ↗

         Call for a style guide meeting every time you see feedback like this, and write down what everybody agrees on. You’ll never have to do it again after 3-4 of those. Problem solved.

         Still not solved? Guess it was really about the commas and not the value delivered anyway, so do whatever you feel like.

         1. parpfish · 1790563500 · focus · HN ↗

            That meeting sounds like it would be the most bikeshed-y thing imaginable.

            What you actually need to do is have a manager lead assert that it’s happening in a top down way and just run the formatter with the defaults. Let people argue case-by-case on what to change after that.

            1. eichin · 1790570618 · focus · HN ↗

               The point is that you get the (inevitable) bikeshedding done once, everyone feels "involved", and then you have a style guide that is both a style guide and a "crystallized argument" - so when someone wants to change something, they know that dozens of people already signed off on it and do they really want to push against that. (So covering new things is still lower friction...)

Unofficial Hacker News client; not affiliated with Y Combinator.