jimws

I am confused if you this is an honest opinion or if you are saying with a touch of sarcasm. If it is the latter, a winking smiley or "</sarcasm>" or "/s" would have been nice to avoid triggering Poe's Law.

In my honest opinion, discussion on syntax is a distraction. One of the reasons I like Lisp/Clojure is that there is very little syntax. I can just focus on my problem and writing good code.

Been to Thailand. Muay Thai is a really good physical and spiritual experience one can have in Thailand. I really recommend it to anyone visiting Thailand with the time and money to invest in this skill.

Fossil - https://www.fossil-scm.org/

Code, commit logs, tickets, and project management are all part of the same repo with Fossil.

Absolutely yes. As a developer I can:

  git log | grep <error message>
  git show <commit id>

I don't have to go looking for an issue tracker and figuring out how to search it effectively.

> Well-written code is a work of art. Always has been, always will be.

The same thing was thought of assembler programming a few decades ago. Now it is rather a lost art. I fear that a day would come when machine learning algorithms can write code on their own and coding itself would become a lost art like assembler has become now.

You should prefix your post title with "Ask HN: ". This way we would know that a question is being asked and it will get the attention of those who want to answer.

Yes. Those were not good days. In those days, every tech savvy person somehow automatically got the privilege to be rude to the less knowledgeable people. If a user came for help without doing sufficient homework, a project author or community would rudely ask the user to go RTFM. There are more civil ways to send the same message. CoCs are a way to bring in that civility in discourse. Do you have a better idea?

You mentioned:

> She made it clear in a comment quoted by The Register that she refused to use the singular they in any circumstance, even when it was known that it was someone's preferred pronoun.

But this is more subtle than that. Monica didn't say that she would use "he" or "she" even when someone prefers "they". She said that she would write in a gender-neutral manner while avoiding gendered pronouns altogether.

Here is the full context of Monica's stance:

> I completely agree that it is rude to call people what they don't want to be called; knowingly misgendering someone is not ok. But the policy was about positive, not negative, use of pronouns. I pointed out that as a professional writer I, by training, write in a gender-neutral way specifically to avoid gender landmines, and sought clarification that this would continue to be ok. To my surprise, other moderators in the room said that not using (third-person singular) pronouns at all is misgendering. The employee never clarified, and this is one of the questions I asked in email. In my email I said clearly that I'm on board with "use preferred pronouns when using pronouns", but from the fact that they fired me without warning (or answering the question), I conclude that that's not the policy. I haven't seen an actual policy, though I am being accused of violating it.

Link: https://judaism.meta.stackexchange.com/questions/5193/stack-...

While I agree that this is strictly worse than current document and eBook formats meant for computers, this inarguably not much worse than physical books. We couldn't have copied quotes or table of contents in a physical book.