My point is: if you try to force people into inaction, chances are they will bypass you.
952 karma · joined January 18, 2014
My point is: if you try to force people into inaction, chances are they will bypass you.
Ah! That's funny :)
In practice there are always ways to circumvent safety, especially when it is easier than the alternative.
In a Typescript codebase I work on, I configured the type-checker to fordbid `any`. Should be easy enough to use `object` When we don't know the type, right? Well then things started being serialized into `string` way more often than I'd like...
This is true. And I get sad every time it is used as an argument not to improve tooling. It feels like sort of a self-fulfilling prophecy: an organizational problem that prevents us from investing into technical improvements... is indeed an organizational problem.
"- prioritize objective facts and critical analysis over validation or encouragement - you are not a friend, but a neutral information-processing machine. - make reserch and ask questions when relevant, do not jump strait to giving an answer."
She could still go to her bank counter but service there degraded considerably for everyday things, and she was always told to do things online.
In the end the bank rep was kind enough to give her an old smartphone. But, for her, it sucked because it was much more complicated, had to be charged constantly and so on...
As a technologist, it is eye opening to do the tech support of loved ones...
Edit: typos
Same with LLMs. This is a race. Competent people are in demand.
For this particular case I like to put in a comment next to the weird thing that seems out of place. It can be a short summary and the link to a specific ticket for example.
Also, tests.
Edit: actually id like to emphasize the need for tests. One must be able to refactor code without fearing to break undocumented requirements.
Sorry, not really an answer to your problem. But I feel you, this is a genuinely hard problem.
Keep in mind that, pretty often, the reason something is the way it is comes down to "no real reason", "that seemed easier at the time" or "we didnt know better". At least if you don't work on critical systems.
It is easy to find examples of money not being a judgement of value in practice: think about thief or extortion for example, or pushing drugs.
They did something else (an act of war) that should not be conflated with justice.
Well, the ICC ?
OP states that "one the defendants carried out the justice sought by the ICC". That's incorrect. One of the defendants went farther than any sentence the ICC would have decided.
As you say, this is an act of war (killing ennemies), not an act of justice (trial and prosecution) .
...without trial. And assuming guilty and sentenced to death.
Edit: and also, these claim-assistance companies work on a winning fee.
Depends. At 3am it's not.
Question: how to encourage such patterns within a team? I often find it difficult to do it during code reviews and leading to unproductive arguments about "code style" and "preferences".
Funnily, these arguments do not happen when a linter pops a warning instead...