Those tools actually save team energy. Without them any programmer has different opinion on formating, code quality, what is readable etc. You can discuss it endlesly or you can just use ruff.

▲

maratc an hour ago | parent | next [-]

We can replace the endless and useless discussion on how to format code with an endless and useless discussion on what linting tool to use.

Another option would be to leave both topics alone and go on with our lives, improving the product, fixing bugs, implementing new features, and generally giving customers a better product and shareholders more value, while respectfully agreeing to disagree on the issues of style.

	▲	Hendrikto 6 minutes ago \| parent \| next [-]
		> We can replace the endless and useless discussion on how to format code with an endless and useless discussion on what linting tool to use. That is why gofmt is so great. As the saying goes: gofmt’s style is nobody’s favorite, yet gofmt is everybody’s favorite.
	▲	jbvlkt 29 minutes ago \| parent \| prev [-]
		People tend to use tools set up in CICD and/or precommit. Without rules everyone uses their tool and is unwilling to compromise. Even if they are willing it is hard to setup tools to do exactly what you want. Default configuration is always the way.

▲

LaGrange an hour ago | parent | prev [-]

Gods forbid I talk to people I work with, learn their preferences, and figure out the way we can accommodate each other. Sounds like such a waste of energy. It’s so much better if we all acquiesce to the preferences of some people neither of works with!

	▲	jbvlkt 34 minutes ago \| parent [-]
		You can still talk to them about more important problems than placement of collons and closing bracket.