The Insufferable Arrogance of Linters

3 pointsGoladus6y ago6 comments

Your preferred coding style is not a "best practice" simply because you've written a parser to automatically detect deviations or because your others on your team agree to follow one convention for the sake of consistency.

The Insufferable Arrogance of Linters

3 pointsGoladus6y ago6 comments

6 comments

6 comments · 2 top-level

Digg_mov6y ago· 4 in thread

consistency?

bzlw6y ago

IMO, this is biggest reason to use linters. I don’t really mind what the “standard” is, as long as everyone is using the same one.

GoladusOP6y ago

Yes, consistently formatted code tends to be easier to read and tends to help teams be (slightly) more efficient.

muzani6y ago

It's helping me a lot searching for, say, "thing" versus 'thing' or url vs URL.

I don't mind whether the coding style is ¿question? or simply question?, but I don't want to see both in the same file.

gtirloni6y ago

I think that seals it, no?

GoladusOP6y ago

> your others

And yes I understand the value of linters :p

j / k navigate · click thread line to collapse

6 comments

6 comments · 2 top-level

Digg_mov6y ago· 4 in thread

consistency?

bzlw6y ago

IMO, this is biggest reason to use linters. I don’t really mind what the “standard” is, as long as everyone is using the same one.

GoladusOP6y ago

Yes, consistently formatted code tends to be easier to read and tends to help teams be (slightly) more efficient.

muzani6y ago

It's helping me a lot searching for, say, "thing" versus 'thing' or url vs URL.

I don't mind whether the coding style is ¿question? or simply question?, but I don't want to see both in the same file.

gtirloni6y ago

I think that seals it, no?

GoladusOP6y ago

> your others

And yes I understand the value of linters :p

j / k navigate · click thread line to collapse