I remember learning about how to use this back in the day and what a game changer it was for my workflow.
Today I like to do all of the commits as I’m working. Maybe dozens or more as I chug along, marking off waypoints rather than logging actual changes. When I’m done a quick interactive rebase cleans up the history to meaningful commits quite nicely.
The fun part is that I will work with people sometimes who both swear that “rewriting history” is evil and should never be done, but also tell me how useful my commit logs are and want to know how I take such good notes as I go.
This was one company spying on the users of its competitor via unofficial means. Even in the furthest stretch of the corporate boot licking bullshit that “you signed up for the app so you deserve to be spied on” exists in, I don’t see how this scenario is covered.
I would argue that the signal to noise ratio here makes this metric effectively worthless. Being unpopular doesn’t necessarily indicate bad faith, and downvotes come for many reasons that are not similar enough to group.
Downvotes also bring a unique kind of bad actor: the troll. I have many times seen accounts that go out of their way to farm for downvotes, and that kind of content brings everyone down with it.
I know it’s an unpopular opinion, but I feel strongly that downvoting itself is a problem.
Social media is powered by little bits of endorphins that come from clicking the response buttons, and a certain type of person seems to get a thrill out of the downvote in particular. That personality type does not seem to be conducive to building a strong community, but we give them quite a bit of engagement anyways to keep them coming back.
I don’t think anything of value would be lost by dropping that action all together.
Scamming people out of their life savings can only be done because the victim fell for a ruse; it’s easy to say afterwards “well that never would have happened if you were just more careful” and dismiss it as their own fault.
That is, however, bullshit; because one person making a mistake never, ever excuses another person from exploiting it.
Even in scenarios where I myself could easily say “well sure that was bound to happen” it still doesn’t make the victim complicit in their victimhood because at no point did they actively consent to being victimized.
That’s the whole sticking point for me here: the logic of “well they put themselves into that position” is effectively tantamount to arguing that they asked to be exploited, which is utter nonsense.
I mean… your whole post is a justification for a line of thinking indicating that assessing a risk scenario is the responsibility of a would be victim; the logical extension of this argument is that victims are at least partially complicit in their victimhood.
I am flatly refuting that. Victims are victims, full stop. It flat out does not matter that someone has put themselves into a risky situation, because the choice to exploit that situation is entirely the responsibility of one party.
The insurance company thing is a bad example, because it’s an example of a for profit company maximizing their profits at the expense of the consumer rather than any kind of moral or ethical statement.
I, for one, do not think leaving your keys in the car excuses car theft.
Just because your back is turned does not mandate me to shoot you, and turning your back on me does not mean that you are complicit in being shot. The exploiting party always, always, needs to have the entirety of blame placed on them.
Risk mitigation is wise and situational awareness is good, but a lack of either of these does not excuse exploitation.
Nate Cox @ natecox @programming.dev Posts 1Comments 746Joined 2 yr. ago
I remember learning about how to use this back in the day and what a game changer it was for my workflow.
Today I like to do all of the commits as I’m working. Maybe dozens or more as I chug along, marking off waypoints rather than logging actual changes. When I’m done a quick interactive rebase cleans up the history to meaningful commits quite nicely.
The fun part is that I will work with people sometimes who both swear that “rewriting history” is evil and should never be done, but also tell me how useful my commit logs are and want to know how I take such good notes as I go.