3 ms·
Have a formatter. There are plently out there that can be part of the compile/build/commit flow, to the point of failing pipelines if the files you changed not
by happymellon 1y ago
Have a formatter. There are plently out there that can be part of the compile/build/commit flow, to the point of failing pipelines if the files you changed not match the style.
Let people know if you have a requirement on layout and enforce it. Code review is far too late.
- bitexploder 1y agoWhere I work the formatter is the final arbiter of formatting code. If you don't like it, good luck justifying a change and you had better have really thought about it and why your change is good, because thousands of engineers have tried and been defeated for one reason or another :)
- happymellon 1y ago> Where I work the formatter is the final arbiter of formatting code. And I'm fine with that. Consistency is key for readability, code is read more than written, legacy code is code that people can't read anymore and want to start again, and most of the changes people want to make aren't standard making it harder for new team members to read the code. Install Black, Prettier, Spotless, and move on.
- bitexploder 1y agoI like it too. It is reliable, predictable. Removes a common source of opinionated friction.