kaoudis on Nostr: It bugs me (fully recognising I may be a picky minority here) when there is spurious ...
It bugs me (fully recognising I may be a picky minority here) when there is spurious gender included in academic papers or other technical work. There is no reason your users, attackers, etc have to be she/her or he/him. Inserting personal pronouns where they don't belong reads weirdly and distracts me. Instead of "The attacker does blah to her system", why not "The attacker does blah to THE system"? Just focus on the attacker's capabilities please. Why not consider gender out of scope of the work, unless the work is about gender?
Published at
2023-06-11 19:32:31Event JSON
{
"id": "d02d67195d66e7ae0bbb2d7c045421372ffeab81fae12c0c755dec404bf4bf9a",
"pubkey": "354dce9e47f6f2c2b7491e72f6019cdc0eb6558ddbf9efe1a092c64b78a89129",
"created_at": 1686511951,
"kind": 1,
"tags": [
[
"mostr",
"https://infosec.exchange/users/kaoudis/statuses/110527247231848771"
]
],
"content": "It bugs me (fully recognising I may be a picky minority here) when there is spurious gender included in academic papers or other technical work. There is no reason your users, attackers, etc have to be she/her or he/him. Inserting personal pronouns where they don't belong reads weirdly and distracts me. Instead of \"The attacker does blah to her system\", why not \"The attacker does blah to THE system\"? Just focus on the attacker's capabilities please. Why not consider gender out of scope of the work, unless the work is about gender?",
"sig": "d47e1c923db7ea627e38ad21ff14ba6dcedf7416afd006ec129678145d154bb02025eaf8ddef39a013d3ba08e13005b7c09021c5dba86ee5c65cb42a866ca1e4"
}
