The dead man, whomever is in question, can no longer harm you. He was a man, maybe a husband and father, and speaking ill of them is of no tangible benefit. To those that respected or loved them, the relationship is gone, and it is not wise to add to their pain.
I have been to the funeral of bad men. His earthly power is gone and if there is an afterlife his judgment is sealed.
This goes for all enemies and tyrants and criminals. We use the term "I am sorry for your loss" because most times the loss is not ours.
I disagree. I say speak against the ideas, not the person, as the person dies, except Jesus who people continue to invoke his name, which probably means he transcends an idea or belief.
I have a terrible toxic belief troubles you. Can I be a member of society just because I believe pineapple on pizza is acceptable? If you associate me as a person with that belief instead of someone who believes, I suddenly become a problem, and not the belief. Jesus said to love your enemies. He also spoke against ideas, not people.
I suppose you shouldn't jeer at them for being dead, for a start, and you should make allowances for their being dead when judging their actions. Treat them fairly.
This has been mentioned a few times in this thread. But it doesn't really make a lot of sense, especially in the case of someone famous.
If two or three days ago, not knowing he was sick (which I didn't), I had said to someone "That Dilbert guy seems to be sort of a whack job," why would it matter that he was alive to hypothetically defend himself? It's extremely unlikely that he would ever be aware of my comment at all. So why does it matter that he's alive?
Outside of Scott Adams and all of that. And I think public figures, especially those whose major schtick was to engender reaction, are a different story.
But it's basically getting the last word in because the other party is unable to respond. It's seen as a little uncouth.
On reddit, it's kind of like those people who respond, then block you to make sure you can't respond. They aren't there to make an argument or convince you, they just want to get the last word and they're doing it in a way where you cannot respond.
Like I said, I don't entirely agree with "don't speak ill of the dead". Especially for figures who used their platform to elicit responses. But that's one of the reasons behind the sentiment. Right, wrong, that's for you to decide.
I didn't fear reprisal from Scott Adams when he was alive, either.
And there are plenty of people willing to step in for Scott and defend him, as evidenced by the contents here.
Someone dying doesn't mean the consequences of their words and actions disappear and acting like we should pretend that death washes away those consequences is silly.
That's a fair observation, and yet anecdotally I agree with the parent comment. In my career I fixed quite a few bugs about dates being passed around and unexpectedly modified, while I struggle to remember the same problem with objects in general (could be a case of selective memory).
If I had the guess, I'd say it's a combination of:
- the difference between the mental model and the implementation. Dates are objects but "feel" like values: dates are parsed from a single value, and when stored/printed they collapse back to a single value (as opposed to custom objects which are generally a bag of properties, and when printed/stored they still look like an object)
- most common date operations causes the original date object to be mutated, which implicitly causes developers to mutate the passed value even if that's not what they explicitly meant
So the default combination is a calling code that expects date to be treated as a value, and the called code accidentally mutating the data because it's convenient to do so. If anything then causes the original value to be saved back in the db, the data gets corrupted.
Most experienced developers will remember to make a copy of the date object both in the calling code and in the receiving code, but the default remains dangerously easy to get wrong.
What parent commenter meant was language level support of immutable objects. There is const, in for example JavaScript, but it supports only immutability of variables, not objects themselves. That later one is possible in C++ for example, where const can be used for both. Of course, it’s still possible to fake immutability with interfaces in some languages, or have a real one forced by implementation (like with Temporals), but it’s much nicer to have an indicator forcing that.
I would like to add, that both variable and object immutability should be the default, and mutability should have a keyword, not other way around how in C++ and Java.
Codex is a sufficiently good reviewer I now let it review my hand-coded work too. It's a really, really good reviewer. I think I make this point often enough now that I suspect OpenAI should be paying me. Claude and Gemini will happily sign off work that just doesn't work, OpenAI is a beast at code-review.
A language is LLM-optimized if there’s a huge amount of high-quality prior art, and if the language tooling itself can help the LLM iterate and catch errors
I’m doing both. For production code that I care about, I’m reading every line the LLM writes, correcting it a lot, chatting with an observer LLM who’s checking the work the first LLM and I are writing. It’s speeding stuff up, it also reduces the friction on starting on things. Definitely a time saver.
Then I have some non-trivial side projects where I don’t really care about the code quality, and I’m just letting it run. If I dare look at the code, there’s a bunch of repetition. It rarely gets stuff right the first time, but that’s fine, because it’ll correct it when I tell it it doesn’t work right. Probably full of security holes, code is nasty, but it doesn’t matter for the use-cases I want. I have produced pieces of software here that are actively making my life better, and it’s been mostly unsupervised.
reply