>Linting, refactoring and testing all have obvious benifits for anyone who has done any small to medium sized project and has had to rewrite and debug some amount of code, even if they don't know the concepts by name
I'm curious but have you ever heard of anyone that works as a programmer that has not been especially keen on linting and testing (as in automated testing)?
I thought that examples of not being overly keen were quite abundant.
And it is often lamented on this site about how much work it is to get even people who have made a small to medium sized project and have the word programmer or developer in their job title to actually want to do linting and testing.
So what I'm saying is that at least for linting and testing yes, these really might seem like
>exercising artisanship that only the experts would see value in rather than solving a technical problem.
Yeah, I’ve been coding for 30 years, and to me, linting seems like alphabetizing the tools on your peg board. There are plenty of times where I want to break an expression into multiple lines—or not—in the service of readability. And there are no clear rules I could dictate to codify how I make that call.
I get that it helps people who are collaborating on large codebases. But to me, typography is orders of magnitude more important, because it’s facing the end-user.
I'm curious but have you ever heard of anyone that works as a programmer that has not been especially keen on linting and testing (as in automated testing)?
I thought that examples of not being overly keen were quite abundant.
And it is often lamented on this site about how much work it is to get even people who have made a small to medium sized project and have the word programmer or developer in their job title to actually want to do linting and testing.
So what I'm saying is that at least for linting and testing yes, these really might seem like
>exercising artisanship that only the experts would see value in rather than solving a technical problem.