I'm happy to forgive that kind of small typo in a hacker news comment, but generally it's easy to catch these things by just reading over the thing one time. If you're putting any amount of thought into your contribution it should be much faster to read it over one time than it was to write in the first place.
Well, I keep missing the "serve"/"server" thing because spell checkers think "server" is a real word so don't flag it. :-)
I'm happy to forgive that kind of small typo in a hacker news comment, but generally it's easy to catch these things by just reading over the thing one time. If you're putting any amount of thought into your contribution it should be much faster to read it over one time than it was to write in the first place.
Getting that wrong is a small price to pay. Plus, people know what you mean.
Too much effort, bruh.
Capitalization is apparently too much effort for some now. Who would have thought the Ai would make us so lazy so quickly?
Who cares about people with reading disabilities, let's shift burden onto the reader. My time is better spent managing my Ais.
This started years before LLMs, as a way of signaling unconventional thinking. Maybe influenced by the UX of instant messaging.
1 reply →
>onto the reader
Or the reader's AI who is able to format or translate the text to make it easier to read for the reader.
2 replies →
IMO, if it's too much effort to improve one's comments, then it's too much effort to write them in the first place.
There's something viscerally distasteful about a one-liner comment berating the author of a long thoughful comment for exerting too little effort.