4 ms·

Ugh tell me about it. My large enterprise company has been piling these on lately. You also get blocked from checking in any ignore eslint statements unless you

by dexwiz 4y ago

Ugh tell me about it. My large enterprise company has been piling these on lately. You also get blocked from checking in any ignore eslint statements unless you ask some review board that meets once a week with a month long waiting list. I know all jobs are balance of productivity and bookkeeping, but all these CI checks are really starting to make me consider switching jobs.

hinkley 4y ago
I keep trying to tell people that the metrics knife is sharpened on both sides. The only way to be absolutely, categorically sure of your trajectory is if your velocity is 0. And that is, as they say, a "divide by zero error". These rules and tools go in to fix a hurt caused by making mistakes, and somewhere it gets twisted away from "not making the same dumb mistakes repeatedly" to "never make any mistakes", which slows things down until you eventually make the chiefest of mistakes for a capitalist venture: never shipping. Two of my better bosses pointed out that only people who risk nothing avoid making mistakes. One of those thought that "perfect estimates" meant you were over as often as you were under (the old accuracy vs precision argument). You can't achieve anything without taking some risks, and 'boring company' only works in a few niche markets, that don't pay well.
- andrekandre 4y ago
  > These rules and tools go in to fix a hurt caused by making mistakes, and somewhere it gets twisted away from "not making the same dumb mistakes repeatedly" to "never make any mistakes" (except for the chiefest of mistakes for a capitalist venture: never shipping). tools cant really prevent mistakes anyways, because people will always find a way to "get the job done anyway" by working around them... the end result in many cases is actually... more mistakes! at some point you have to hire people you can trust, no tool or process can fix that!
  - atom_arranger 4y ago
    If the people working with tools like ESLint or TypeScript don't appreciate what they're doing for them, then yeah they'll work around them. I guess you need to teach people like that how they can work with the tools to get things done, with higher quality results. For my part I very much appreciate that ESLint and TypeScript can help me write better code, they're helpful and consistent reminders. I understand that I should use ===, I understand I should check for null, but without the tools I won't remember to do it in 100% of the cases I should.

by dexwiz 4y ago

hinkley 4y ago

I keep trying to tell people that the metrics knife is sharpened on both sides. The only way to be absolutely, categorically sure of your trajectory is if your velocity is 0. And that is, as they say, a "divide by zero error". These rules and tools go in to fix a hurt caused by making mistakes, and somewhere it gets twisted away from "not making the same dumb mistakes repeatedly" to "never make any mistakes", which slows things down until you eventually make the chiefest of mistakes for a capitalist venture: never shipping. Two of my better bosses pointed out that only people who risk nothing avoid making mistakes. One of those thought that "perfect estimates" meant you were over as often as you were under (the old accuracy vs precision argument). You can't achieve anything without taking some risks, and 'boring company' only works in a few niche markets, that don't pay well.

andrekandre 4y ago
> These rules and tools go in to fix a hurt caused by making mistakes, and somewhere it gets twisted away from "not making the same dumb mistakes repeatedly" to "never make any mistakes" (except for the chiefest of mistakes for a capitalist venture: never shipping). tools cant really prevent mistakes anyways, because people will always find a way to "get the job done anyway" by working around them... the end result in many cases is actually... more mistakes! at some point you have to hire people you can trust, no tool or process can fix that!
- atom_arranger 4y ago
  If the people working with tools like ESLint or TypeScript don't appreciate what they're doing for them, then yeah they'll work around them. I guess you need to teach people like that how they can work with the tools to get things done, with higher quality results. For my part I very much appreciate that ESLint and TypeScript can help me write better code, they're helpful and consistent reminders. I understand that I should use ===, I understand I should check for null, but without the tools I won't remember to do it in 100% of the cases I should.