Does anyone really stress over these? Everywhere I’ve used them it’s always been use black/flake8/eslint/prettier with mostly out of the box settings in order to get some low hanging fruit standardisation of the code to avoid people stressing/arguing over them.
If a code style check is worthwhile then it should be PR-able into one of the mainstream automated code linters, style checkers, or formatters.
In one case the person had seniority over me and kept "refactoring" our codebase in a team of 8. You'd write a function that worked one day and come back the next and it was broken because "I changed the name of that function because it did sound right".
Some people are weirdos and nothing short of their manager telling them to STFU and do their job will stop them.
// I prefer to look at this:
function example( whatever ) {
:
}
// Instead of this:
function example(whatever)
{
:
}
Also... my dyslexic coders tend to hate long lines of code, so we sometimes do lispy things like this:
const foo = whatever(
"this is a big long parameter",
( 2 + bar ) * 90,
i,
process.env.HOME || `/mnt/${process.env.USER}`
);
const foo = whatever( "this is a big long parameter", ( 2 + bar ) * 90, i, process.env.HOME || `/mnt/${process.env.USER`);
Was it as bad as my spidey senses are telling me?