3 ms·
Personally I'd regard it as a bit unfair to be rejected just on the grounds of code formatting. I've changed my indentation style before to meet a "house style"
by coroxout 15y ago
Personally I'd regard it as a bit unfair to be rejected just on the grounds of code formatting. I've changed my indentation style before to meet a "house style" and would do so again if asked.
In my opinion it would be more useful to see if the candidate seems prepared to change and has thought about the reasons for their style choice.
(Plus I admit I probably should know the precedence rules for my languages of choice off by heart, but sometimes it's easier just to put extra parentheses in than wait for a compilation error or, worse, an inscrutable bug - especially if you're up against the clock or being watched in an in-person interview)
- mirsadm 15y agoI completely agree. I really meant to say that we looked for someone who was passionate about coding and they could defend their style/structure because they cared. We always worked in the style/structure of the original author because the code should be consistent. That is more important over personal preference. Our arguments over small things like indentation were heaps of fun because everybody there was really passionate. It was never about enforcing it because it is the one and only way to do it. Stubbornness on matters like that is not good.