In a team of engineers, find one that complains about the configuration formats or linting rules, and with 100% confidence, you know who will ruin your meetings.
Source: empirical study from me
Thanks for not being that person.
Source: empirical study from me
Thanks for not being that person.
* for new projects, use a well-established, reputable standard
* for existing projects, use what is already in place if it is consistent
* in case of inconsistency, fix to the closest industry standard
* Use an auto-formatter and enforce it in CI
Github even has public beta support for it, though they require a specific name for the ignore revs file: https://docs.github.com/en/repositories/working-with-files/u...
But if this project made a weird decision I'm ok with it, as long as it's enforced consistently.