4 ms·
If it’s configurable, then it’s never settled. People will find reasons to want to change it, or someone new will come in that used a better config at their las
by sixstringtheory 3y ago
If it’s configurable, then it’s never settled. People will find reasons to want to change it, or someone new will come in that used a better config at their last job.
- pyrale 3y ago> People will find reasons to want to change it, or someone new will come in that used a better config at their last job. This is fine. Discussing code style once in a while is not a problem. What's a problem is discussing it at every PR. Having to endure through asinine style errors that no one in your team chose or even agrees with is worse than spending a couple hours every 6 months discussing a rule or two.
- stevelini 3y ago> Discussing code style once in a while is not a problem. What's a problem is discussing it at every PR. I worked a team where this happened. Black was a godsend
- Pannoniae 3y agoThat just means your coworkers are anti-social... this masks the problem but the real solution is educating people so they won't be anti-social anymore and stop nitpicking about others' style.
- sixstringtheory 3y agoTeaching people to “just don’t be anti-social” is not the purview of people on a team trying to get work done, nor is it even possible in many or most cases.