News for hackers. Stuff that matters.
Re:How to Design Software Good by GuiA on Thursday November 08, 2018 @06:01PM (#18410854)
...You can also make Tracker show a window for a particular folder in order to show the user where a particular file has been stored and give him access to it directly....

...By removing unneeded items from the file navigation window, you are reducing the number of choices the user must pick from and also preventing him from opening the wrong kinds of files...

...Good feedback just means making sure that the user knows what your program is doing at any given time, especially if the program is busy doing something which makes him wait...

...An even better solution would be to select a good default choice for the user and give him the option to change it...

... In short, a user will learn only what he must in order to do his job...

Ctrl-F "her", "she": 0 matches

Another tip to design good software: don't assume all your users are male :)

This is an okay stab at a HIG, although it is severely lacking in examples and screenshots, for a document that deals with graphical user interfaces.

Good past attempts that are worth the read if you're into this kind of stuff include the original Macintosh HIG, as well as NextStep User Interface Guidelines. I also quite liked the Hypercard Stack Design Guidelines. Gnome once had an okay-ish HIG (which I contributed to), not sure how well up to date it's been kept through the years. KDE, despite being better on the eye candy front compared to Gnome, was always lacking behind in terms of actual concrete guidelines for developers.

Re:How to Design Software Good by waddlesplash on Thursday November 08, 2018 @06:58PM (#18411178)
This document was mostly written almost a decade ago, and by someone who I think went to a prestigious institution. So the "rules of style" back then aren't what they are today.

You're right, we should update it, though.

Re:How to Design Software Good by anonytrary on Thursday November 08, 2018 @09:16PM (#18411891)
> You're right, we should update it, though.

No, you really shouldn't, it's not a real problem. The only people who keep tallies of gender pronouns in documents are internet trolls; don't indulge the trolls. Anyway, switching up pronouns every other time breaks continuity and makes documents harder and painful to read.

Re:How to Design Software Good by GuiA on Thursday November 08, 2018 @09:43PM (#18411998)
No need to keep a tally; in 2018, any document that exclusively uses masculine pronouns for genderless subjects reads as outdated.

When writing on technical topics, the chief concern is to be clear, accurate, and straightforward. Anything that might distract your reader is undesirable. By referring to “the user” as “he”, you’re already distracting roughly 50% of your potential readership (if you’re writing the documentation for a Do It Yourself Vasectomy Kit, perhaps you get a pass).

Switching up pronouns every other time is a strategy, but it is indeed one that can hurt the readability of a document. This article covers various strategies nicely:

https://www.herodios.com/pronouns.html

(Note that this document was written over 20 years ago, so the “rules of style” when this document was written were roughly the same as they are now)

Re:How to Design Software Good by zeveb on Friday November 09, 2018 @08:44AM (#18414245)
> any document that exclusively uses masculine pronouns for genderless subjects reads as outdated.

Correct English is never out of style.

Different languages do different things, and that's okay. Some languages apply grammatical gender to more than just sex, e.g. tools, or fruit. That's okay. English uses grammatical gender to distinguish between male, female & neuter objects, and defaults to male when referring to unknown males-or-females. That's okay too. It's all part of the rich panoply of life.

> By referring to “the user” as “he”, you’re already distracting roughly 50% of your potential readership

I really doubt every woman is distracted by proper grammar. And of course by not using correct English, you distract people who use & prefer it.

Re:How to Design Software Good by GuiA on Friday November 09, 2018 @11:36AM (#18415660)
Except there is no such thing as “Correct English”.

If we were speaking about eg contemporary France French, you would have a point - there is a governing body decreeing what is correct French and what isn’t.

That is not the case for English.

But even that is besides the point, because “they” as a genderless pronoun has been used for over half a millennia. (William Caxton, 1460: “Each of them should...make themself ready”)

Re:How to Design Software Good by anonytrary on Thursday November 08, 2018 @10:09PM (#18412073)
> By referring to “the user” as “he”, you’re already distracting roughly 50% of your potential readership (if you’re writing the documentation for a Do It Yourself Vasectomy Kit, perhaps you get a pass).

Do you have any research/data to back this up? I'm a male and I am not distracted when people use "she" (or "he" for that matter). I have never heard anyone in person complain about not being able to focus on an article because they used "he" instead of "she".

> Anything that might distract your reader is undesirable.

Concision is of utmost importance in any language. Many of the examples in your link sacrifice readability and concision for the purpose of avoiding pronouns. What really distracts me is when people use "(s)he", "s/he", "he or she" (oh no -- which one should be first?), or periodically switch between "he" and "she" absolutely everywhere -- all for the purpose of filling a contrived equality quota.

Re:How to Design Software Good by mixmastamyk on Friday November 09, 2018 @12:25PM (#18416081)
We need an "it" that can be applied to a person.
Re:How to Design Software Good by dragonwriter on Friday November 09, 2018 @12:37PM (#18416208)
English has had one for a long time, “they”.

Elitist prescriptivists who wanted English to be Latin because of bizarre linguistic fashion tried to purge it, but never did from general use, and prescriptivism, especially on points that have never aligned with common usage,has fallen out of favor, so there is little reason not to use it now but adherence to a particularly archaic elitism.

Re:How to Design Software Good by mixmastamyk on Friday November 09, 2018 @04:45PM (#18418315)
It’s useful to have a singular and plural form, required probably not.
Re:How to Design Software Good by GuiA on Thursday November 08, 2018 @10:48PM (#18412194)
There is a user, they are using the system, and that’s about as much as we know about them.
Re:How to Design Software Good by anonytrary on Friday November 09, 2018 @01:34AM (#18412743)
"He" clocks in at two characters, it's a very concise way of referring to an arbitrary person. "The user" takes longer to write and longer to say. Forcing the reader to juggle around "or" conditions (i.e. with "he or she") is even worse and I consider it bad practice. Your readers will thank you for concreteness and brevity.
Re:How to Design Software Good by GuiA on Friday November 09, 2018 @11:38AM (#18415675)
You’ll notice that my previous post uses “they” as shorthand for “the user”. If your last remaining argument is that “he” is 2 letters and “they” is 4 and thus it’s unequivocally better to always use “he”, it’s not a very good one.
Re:How to Design Software Good by CathyWest on Friday November 09, 2018 @04:33AM (#18413344)
> you’re already distracting roughly 50% of your potential readership

If by 50% you mean 100% of the women having trouble making it through an article with multiple instances of "he" not immediately followed by "or she", that's a pretty bold claim.

I suspect the key factor in people's inability to focus on the central point of the article lies in their political persuasion rather than the shape of their genitalia.

Re:How to Design Software Good by GuiA on Friday November 09, 2018 @11:46AM (#18415760)
50% refers to the mix of male and female people who get distracted by this; in my experience as a technical writer who would always use “he” when I was less experienced, perhaps 70% of women and 30% of men?

It was certainly one aspect of my writing I got a lot of feedback on. Changing that habit was fairly easy, and has entirely solved the problem.

I’m not sure what’s political about pointing out that “the user” of eg a computer system is not always a “he”, but if you want to bring the conversation there, have fun. If anything, it’s starting to feel to me like people with no interest in technical writing are coming out of the woodwork and making this political!

Re:How to Design Software Good by CathyWest on Sunday November 11, 2018 @01:42PM (#18427817)
> 50% refers to the mix of male and female people who get distracted by this; in my experience as a technical writer who would always use “he” when I was less experienced, perhaps 70% of women and 30% of men?

But who were these people? I don't doubt that there exists a population such that half of it complains about lack of gender neutral language in technical writing, but it does not necessarily follow that the same half should also be arbiters of techincal writing style.

> It was certainly one aspect of my writing I got a lot of feedback on. Changing that habit was fairly easy, and has entirely solved the problem. > > I’m not sure what’s political about pointing out that “the user” of eg a computer system is not always a “he”, but if you want to bring the conversation there, have fun.

Back when the convention in English (and various other languages) was that male pronouns were used in mixed or unspecified situation there was no need to point this out, it was given by the convention. Pronouns with masculine grammatical gender being exclusively applicable to men is a recent innovation, without which the problem you are trying to solve wouldn't even exist.

These shifts in meaning can of course happen organically, but I find it very curious that this particular one happened at the same time as the rise of feminism in the 20th century. More extreme examples of the same politicised language is using "womyn" instead of "woman" in order to prevent it from ending in "man".

Re:How to Design Software Good by chipotle_coyote on Friday November 09, 2018 @01:52AM (#18412799)
The only people who consider switching between "he" and "she" in different examples are internet trolls. Obviously, that's not really true, but neither is your snark.

Look: gender-neutral language in technical writing is not that difficult. Most of the time you can rewrite sentences to simply avoid gendered pronouns, e.g., "the successful applicant will use his skills to contribute to the platform team" becomes "the successful applicant's skills will contribute to the platform team."

As for alternating between pronouns, do you think readers are bothered by switching between using male and female names in examples? If you realize that the first example used Bob, the second used Agatha, and the third used William, do you suddenly leap up, scream INTERNET TROLLS GOT TO THEM!, and punch your monitor? No, probably not. So do you do if you see pronouns switching? Really? Again: I'm betting probably not.

I can tell you that as someone who's done technical writing for a half-dozen companies over the last decade or so that I have never heard of readers complaining about alternating pronouns. I have heard of them complaining about documentation that is exclusively male, though, because it turns out that's something some -- not all, maybe not most, but definitely some -- readers will notice and be a little nonplussed by.

Re:How to Design Software Good by JadeNB on Thursday November 08, 2018 @07:42PM (#18411468)
> This document was mostly written almost a decade ago, and by someone who I think went to a prestigious institution. So the "rules of style" back then aren't what they are today.

What does the second half of the first sentence have to do with the second sentence?

Re:How to Design Software Good by waddlesplash on Thursday November 08, 2018 @08:42PM (#18411771)
That prestigious institutions up until the past few years used male pronouns to refer to generic individuals as being "proper English", which this document ostensibly is, and this explains the document's use of them?
Re:How to Design Software Good by mixmastamyk on Friday November 09, 2018 @12:32PM (#18416163)
Yes, replacing "he/she" with "they" was discouraged because it is plural. Since then gender issues have come to the forefront and this drawback has been deemed less important. "They" is now recommended by most folks, but wasn't the case 12 years ago.

Times change.