4 ms·
It could also be a testament of the reviewer's inability to read code written differently. Style is not consistent across authors, codebases, projects, even co
by Hydraulix989 8y ago
It could also be a testament of the reviewer's inability to read code written differently.
Style is not consistent across authors, codebases, projects, even companies. I had to learn to read code in many different styles.
Enforcing consistency can be done with formatters/linters. It doesn't need to come up in review.
- sauceop 8y agoIt depends on how important you think it is to optimize for future readers or maintainers of the code. I weigh that pretty heavily and a do think relatively minor style issues impose a tax once they're pervasive in a codebase. Tooling is great, but I think there are a lot of style issues that aren't readily enforceable with linters - commenting, naming, control flow, abstraction, etc.