Why do programmers always use 'we' when really they mean 'me' or 'you'? [closed]

Question

Something I've noticed a lot from reading articles on stack overflow is that programmers tend to use the term 'we' a heck of a lot. I'm a programmer myself and I must admit, of all the times I've given people a few programming lessons or a bit of programming help, I've never felt compelled to use the term 'we' when talking about something you can do in the language.

For example (picking from some stackoverflow suggestions): "When do we really need to use hibernate for our Java code?" and "Why do we use process when we do have threads? [closed]"

Really what these people mean is: "When do you really need to use hibernate for your Java code?" (in which case 'you' acts as an informal equivalent of 'one') and "Why is process used when threads can be used instead?"

Has anyone else noticed this? Is there a reason programmers tend to use 'we' when discussing programming when really they mean 'you' or 'me' or the question could be asked without the terms.

Does anyone know where this trend/habit started or why so many people do it? Frankly it's starting to bother me because it results in an awkward use of English that doesn't feel natural and isn't particularly easy to take in.

Answer 1

This is a rhetorical narrative voice which is used in nonfiction. It has the effect of creating a sense of level ground between the narrator and audience by creating an inclusive feeling. There is a separation between us and the subject matter, but we (narrator and audience) are both on the same side of it, approaching it together as equals.

It is not confined to academic presenting or writing. For instance, a cooking recipe might be written in various voices, including we:

Imperative: Then, place the ingredients into the skillet and simmer on low heat.

We: Then we place the ingredients into the skillet and simmer on low heat.

I: Then I placed the ingredients into the skillet and simmered them on low heat.

You: Then you place the ingredients into the skillet and simmer on low heat.

All the various voices create their own mood.

The first person plural we-voice is particularly suitable for presenting in front of an audience.

Programmers have sat through lots of lectures in school, so the we voice is drilled into their heads. How do we know this is true? We solve this equation ...

You, we and one are all different voices which mean the same thing: any person at all in an applicable situation, but with different moods.

Answer 2

You'll see that in every field, not just programming. It 'means' that the problem or practice or need or stupid behavior is endemic to the field, not just to isolated practitioners.

For instance, in my old field of literary scholarship, I might ask plaintively,

Why, just when the advent of personal computers made it possible to create handsome, intelligible footnotes and marginal notes, have we decided to adopt the loathsome social-sciences practice of inline citation, which disfigures the typographic beauty of my page and renders my skillfully crafted prose difficult to follow?

I didn't decide to adopt that practice; I trust that you as a fellow-scholar didn't decide to adopt that practice; but somehow or other we have adopted that practice, and I'd like to know Why? (And what the hell you and I and other right-minded people can do about it.)

Answer 3

I learned this practice from mathematics professors, who said that we use "we" in mathematical writing to be welcoming and inviting to the reader - you and I are doing math together. Seems a little silly now that I'm writing it, but this is how I learned it.

Answer 4

Your question triggered a few minutes of introspection as I went over the document I had written this afternoon in which I had taken out a few I's and replaced them with the plural under discussion.

Why did I do it? Now that I think about it, it is a consciously nurtured habit. So, here is the hypothesis based on my recollection of my programming days: Programmers are loners, with long bouts of concentration and Eureka moments where their own stupidity or that of someone else shines through the code. Hold this thought for a second. The good ones are particularly good at this and are orders of magnitude better than the 'wannabes' and are often resented by the struggling programmers (who will be future managers) and termed arrogant and not team players.

At least this is how I developed this habit — going out of my way to show teamwork and not throwing it in someone's face with an accusative 'you'.

Answer 5

As a programmer myself, I consciously use "We" in the code comments and other written media. Why? Because at any time, I consider there are at least two parties involved - the person that wrote it and the person reading it. One is in the past and the other is in the present. The one in the present is trying to follow what the one in the past meant.

In other words, I see it as a conversation through time, where the person who wrote the code is trying to explain something in a way that involves the person trying to understand it. We is more inclusive - I wrote it, you need to fix it, let's figure it out together.

This is also why I never use we when I am explaining my work in person, which is also usually verbally.

Answer 6

I see it as induction into a culture or practice. We're not describing mere preference - there's an element of normativity in our preferences. It's like when a teacher says to a child, "We raise our hands when we have a question." That statement isn't mere description of a state of affairs - it's a statement about what we should do - the "we" being the culture one is being inducted into.