git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 4/4] CodingGuidelines: recommend singular they

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Jun 8, 2021, 01:47 UTC
Message-ID
<60becc2adf199_dcf6520847@natae.notmuch>
In-Reply-To
<875yyp4fun.fsf@evledraar.gmail.com>
Ævar Arnfjörð Bjarmason wrote:
> On Mon, Jun 07 2021, Derrick Stolee via GitGitGadget wrote:
Show 26 quoted lines
> > If the reader does not consider that pronoun to apply to them,
> > then they can experience cognitive dissonance that removes focus from
> > the information. [...]
> > When choosing a gendered pronoun, that pronoun no longer applies to
> > nearly half of possible readers. Even if we alternated between "he/him"
> > and "she/her" perfectly evenly, we would still expect male and female
> > readers to experience an incorrect pronoun half the time. However, some
> > readers will not prescribe to either of these binary genders. Those
> > readers hence suffer an incorrect pronoun the entire time. Singular
> > "they" applies to every reader.
> 
> I'd expect most people to not actively read technical documentation and
> try to personally actively ascribe themselves to prose that clearly
> forms an example of something they may or may not do.
> 
> If that is how people commonly read documentation and find it
> off-putting I'd expect gendered language to be the least of our
> problems, since even with s/\bhe|she\b/they/g so much of what's left is
> still referring to hypothetical situations most users won't want to find
> themselves in.
> 
> Maybe I'm overthinking this, but per the above I'd think if this is a
> problem with losing the reader that we'd need more structural solutions
> to it in the common case, e.g. more guarded language that you should not
> read further if you don't care about XYZ aspect of the technical feature
> we're about to discuss.

Personally I have no trouble at all reading instructions mentioning a female user and see how they apply to me just the same.

Using a singular "they" for semantically singular antecedents does sound totally broken to me, and that does distract me from what the documentation is supposedly trying to transmit.

I have trouble parsing the documentation as it is--which does feel to be in a very detached and unpersonal style. Changes like s/s?he/they/ only make the situation worse. I would rather have the documentation speak to me more like a person, and less like a previous-generation AI.

Cheers.
-- 
Felipe Contreras
Previous: Ævar Arnfjörð BjarmasonNext: Felipe Contreras
Message 46 of 124 in “Use singular "they" when appropriate”
  1. 0/4 Use singular "they" when appropriateDerrick Stolee via GitGitGadget, Jun 7, 2021
  2. 2/4 *: use singular they in commentsDerrick Stolee via GitGitGadget, Jun 7, 2021
  3. Ævar Arnfjörð BjarmasonJun 7, 2021
  4. Derrick StoleeJun 7, 2021
  5. Johannes SchindelinJun 10, 2021
  6. Junio C HamanoJun 7, 2021
  7. Felipe ContrerasJun 7, 2021
  8. Emily ShafferJun 8, 2021
  9. 1/4 Documentation: use singular they when appropriateDerrick Stolee via GitGitGadget, Jun 7, 2021
  10. Ævar Arnfjörð BjarmasonJun 7, 2021
  11. Derrick StoleeJun 7, 2021
  12. Andrei RybakJun 7, 2021
  13. Ævar Arnfjörð BjarmasonJun 7, 2021
  14. Johannes SchindelinJun 10, 2021
  15. Felipe ContrerasJun 10, 2021
  16. Felipe ContrerasJun 7, 2021
  17. Phillip SusiJun 9, 2021
  18. Felipe ContrerasJun 9, 2021
  19. Phillip SusiJun 11, 2021
  20. Felipe ContrerasJun 11, 2021
  21. Derrick StoleeJun 10, 2021
  22. Junio C HamanoJun 11, 2021
  23. Felipe ContrerasJun 11, 2021
  24. Phillip SusiJun 12, 2021
  25. Junio C HamanoJun 8, 2021
  26. Kerry, RichardJun 8, 2021
  27. Junio C HamanoJun 8, 2021
  28. Derrick StoleeJun 9, 2021
  29. Junio C HamanoJun 10, 2021
  30. Emily ShafferJun 8, 2021
  31. Felipe ContrerasJun 8, 2021
  32. Kerry, RichardJun 9, 2021
  33. Felipe ContrerasJun 9, 2021
  34. Kerry, RichardJun 25, 2021
  35. Junio C HamanoJun 9, 2021
  36. Johannes SchindelinJun 10, 2021
  37. Felipe ContrerasJun 10, 2021
  38. Robert KarszniewiczJun 14, 2021
  39. 4/4 CodingGuidelines: recommend singular theyDerrick Stolee via GitGitGadget, Jun 7, 2021
  40. Junio C HamanoJun 7, 2021
  41. Derrick StoleeJun 7, 2021
  42. Junio C HamanoJun 8, 2021
  43. brian m. carlsonJun 10, 2021
  44. Johannes SchindelinJun 10, 2021
  45. Ævar Arnfjörð BjarmasonJun 7, 2021
  46. Felipe ContrerasJun 8, 2021
  47. Felipe ContrerasJun 7, 2021
  48. Phillip SusiJun 9, 2021
  49. Felipe ContrerasJun 9, 2021
  50. Robert KarszniewiczJun 7, 2021
  51. Felipe ContrerasJun 7, 2021
  52. Jeff KingJun 8, 2021
  53. Felipe ContrerasJun 8, 2021
  54. Derrick StoleeJun 9, 2021
  55. Felipe ContrerasJun 9, 2021
  56. brian m. carlsonJun 10, 2021
  57. Felipe ContrerasJun 11, 2021
  58. Emily ShafferJun 8, 2021
  59. Junio C HamanoJun 9, 2021
  60. Derrick StoleeJun 9, 2021
  61. 3/4 *: fix typosDerrick Stolee via GitGitGadget, Jun 7, 2021
  62. Emily ShafferJun 8, 2021
  63. Johannes SchindelinJun 10, 2021
  64. Derrick StoleeJun 10, 2021
  65. Johannes SchindelinJun 11, 2021
  66. Felipe ContrerasJun 7, 2021
  67. 0/4 Use singular "they" when appropriateDerrick Stolee via GitGitGadget, Jun 9, 2021
  68. 4/4 CodingGuidelines: recommend singular theyDerrick Stolee via GitGitGadget, Jun 9, 2021
  69. Felipe ContrerasJun 9, 2021
  70. 3/4 *: fix typosDerrick Stolee via GitGitGadget, Jun 9, 2021
  71. 2/4 *: use singular they in commentsDerrick Stolee via GitGitGadget, Jun 9, 2021
  72. Felipe ContrerasJun 9, 2021
  73. 1/4 Documentation: use singular they when appropriateDerrick Stolee via GitGitGadget, Jun 9, 2021
  74. Felipe ContrerasJun 9, 2021
  75. Ævar Arnfjörð BjarmasonJun 9, 2021
  76. Felipe ContrerasJun 9, 2021
  77. Junio C HamanoJun 10, 2021
  78. Junio C HamanoJun 10, 2021
  79. Felipe ContrerasJun 10, 2021
  80. brian m. carlsonJun 10, 2021
  81. Ævar Arnfjörð BjarmasonJun 10, 2021
  82. Felipe ContrerasJun 11, 2021
  83. Derrick StoleeJun 11, 2021
  84. Felipe ContrerasJun 11, 2021
  85. Ævar Arnfjörð BjarmasonJun 13, 2021
  86. Junio C HamanoJun 15, 2021
  87. Derrick StoleeJun 15, 2021
  88. Felipe ContrerasJun 15, 2021
  89. Junio C HamanoJun 14, 2021
  90. 0/4 Avoid gendered pronounsDerrick Stolee via GitGitGadget, Jun 15, 2021
  91. 2/4 comments: avoid using the gender of our usersFelipe Contreras via GitGitGadget, Jun 15, 2021
  92. 1/4 doc: avoid using the gender of other peopleFelipe Contreras via GitGitGadget, Jun 15, 2021
  93. 3/4 *: fix typosDerrick Stolee via GitGitGadget, Jun 15, 2021
  94. 4/4 CodingGuidelines: recommend singular theyDerrick Stolee via GitGitGadget, Jun 15, 2021
  95. Ævar Arnfjörð BjarmasonJun 15, 2021
  96. Felipe ContrerasJun 15, 2021
  97. Junio C HamanoJun 16, 2021
  98. Junio C HamanoJun 16, 2021
  99. Bagas SanjayaJun 16, 2021
  100. Derrick StoleeJun 16, 2021
  101. Ævar Arnfjörð BjarmasonJun 16, 2021
  102. Felipe ContrerasJun 16, 2021
  103. Junio C HamanoJun 17, 2021
  104. Derrick StoleeJun 17, 2021
  105. Felipe ContrerasJun 17, 2021
  106. Ævar Arnfjörð BjarmasonJun 17, 2021
  107. Felipe ContrerasJun 17, 2021
  108. brian m. carlsonJun 18, 2021
  109. Felipe ContrerasJun 18, 2021
  110. Felipe ContrerasJun 17, 2021
  111. Ævar Arnfjörð BjarmasonJun 17, 2021
  112. brian m. carlsonJun 18, 2021
  113. Ævar Arnfjörð BjarmasonJun 18, 2021
  114. Felipe ContrerasJun 18, 2021
  115. Junio C HamanoJun 19, 2021
  116. Junio C HamanoJun 28, 2021
  117. Felipe ContrerasJun 29, 2021
  118. Derrick StoleeJun 29, 2021
  119. Ævar Arnfjörð BjarmasonJun 29, 2021
  120. Felipe ContrerasJun 17, 2021
  121. Felipe ContrerasJun 17, 2021
  122. Felipe ContrerasJun 15, 2021
  123. Bagas SanjayaJun 12, 2021
  124. Phillip SusiJun 12, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.