Code style in reviews is a subject fraught...

Code style in reviews is a subject fraught with disagreements. Like the rest of software engineering, though, the answer to how much it matters is “it depends.” Style requires that each team member quickly understands the code, can make changes to it, and build on top of it. There are fewer people to satisfy in a small team, so code style isn’t all that important. In contrast, large organizations need a consistent style to enable quick changes and to have engineers flex into other areas of the codebase. " "" "An orthogonal aspect, though, is linters. Linting can automate code style, but setting up those rules and automation takes its own set of skills, which a small team often doesn’t have. If you’re in a small team, don’t let style create massive debates that distract you from the actual problems. If you’re in a big organization and code style is an issue, find someone who can automate it, allowing the team to focus on what’s important. Code style is not the goal; it’s a means to an end, always remember that #bendevtip

---

Original post on LinkedIn