Your answer doesn’t give confidence that you care about how the code looks. Could imply that you’re sloppy. Some people are very opiniated about style and think it matters a lot. They would be unhappy with people who say it doesn’t really matter.
They’d likely welcome fixes or comments on style. Other people would be very angry if you held up their PR with such trivialities.
I had strong style preferences when I was younger, but after working on so many projects with different styles I really don’t care anymore about any particular style. I just make sure to seamlessly match the style of the code around it.
I work with Python. Usage of formatting tools (black, ruff) are widely adopted. Part of its Zen is “there should be one way to do it”, most of its idioms are widely adopted and if you ask anyone about an example of a PEP, they will respond with “8”.
That is to say, “how python code should look” is somewhat of a solved problem. Any occasional differences that might show up in a codebase are likely to be minor that are simply not worth arguing for.
I think that the interviewer was mostly looking for an answer where I could talk about how I deal with conflict. But to be honest if that was the case I would be either more straightforward about the question, or I would try a different scenario with something that might happen more frequently.
Your answer doesn’t give confidence that you care about how the code looks. Could imply that you’re sloppy. Some people are very opiniated about style and think it matters a lot. They would be unhappy with people who say it doesn’t really matter.
They’d likely welcome fixes or comments on style. Other people would be very angry if you held up their PR with such trivialities.
I had strong style preferences when I was younger, but after working on so many projects with different styles I really don’t care anymore about any particular style. I just make sure to seamlessly match the style of the code around it.
I work with Python. Usage of formatting tools (black, ruff) are widely adopted. Part of its Zen is “there should be one way to do it”, most of its idioms are widely adopted and if you ask anyone about an example of a PEP, they will respond with “8”.
That is to say, “how python code should look” is somewhat of a solved problem. Any occasional differences that might show up in a codebase are likely to be minor that are simply not worth arguing for.
I think that the interviewer was mostly looking for an answer where I could talk about how I deal with conflict. But to be honest if that was the case I would be either more straightforward about the question, or I would try a different scenario with something that might happen more frequently.