Comment author: shminux 18 August 2013 04:29:46PM *  3 points [-]

I am mildly consequentialist, but not a utilitarian (and not in the closet about it, unlike many pretend-utilitarians here), precisely because any utilitarianism runs into a repugnant conclusion of one form or another. That said, it seems that the utility-monster type RC is addressed by negative utilitarians, who emphasize reduction in suffering over maximizing pleasure.

Comment author: novalis 19 August 2013 06:29:35AM 2 points [-]

Isn't there an equivalent negative utility monster, who is really in a ferociously large amount of pain right now?

Comment author: SaidAchmiz 16 August 2013 11:30:19PM 12 points [-]

So here's a question for anyone who thinks the concept of a utility monster is coherent and/or plausible:

The utility monster allegedly derives more utility from whatever than whoever else, or doesn't experience any diminishing returns, etc. etc.

Those are all facts about the utility monster's utility function.

But why should that affect the value of the utility monster's term in my utility function?

In other words: granting that the utility monster experiences arbitrarily large amounts of utility (and granting the even more problematic thesis that experienced utility is intersubjectively comparable)... why should I care?

Comment author: novalis 17 August 2013 12:49:34AM 14 points [-]

why should I care?

Isn't this an objection to any theory of ethics?

Comment author: PhilGoetz 16 August 2013 10:04:57PM *  6 points [-]

The qualification that a utility monster is not susceptible to diminishing marginal returns is made only because they're still assuming utility is measured in something like dollars, which has diminishing marginal returns, rather than units of utility, which do not. Removing that qualification doesn't banish the utility monster. The important point is that the utility monster's utility is much larger than anybody else's.

Comment author: novalis 17 August 2013 12:23:41AM 0 points [-]

Presumably, that's diminishing marginal returns relative to dollars input. In other words, "You can only drink 30 or 40 glasses of beer a day, no matter how rich you are."

Comment author: Kawoomba 13 August 2013 08:01:52PM *  1 point [-]

We seem to agree: if I tell you the length of two pieces of code but nothing else, you won't be able to tell me which of them is more likely to terminate. It could be the one, or it could be the other. The relationship may not be strictly orthogonal (e.g.: longer code could contain more unintended infinite loops), but enough to call it mostly unrelated.

Same with complexity of rules versus "solving the games". Go compensates for the simplicity of its rules by blowing up the search space (it's a big board), which doesn't take any noteworthy additional complexity. The rules of a Go variant played on a 5 x 5 board would have about the same complexity as if played on a 3^^^3 x 3^^^3 board.

Some of the easiest-to-play children's board games have some of the hardest rules, compared to Go.

Comment author: novalis 13 August 2013 08:10:31PM 0 points [-]

Yes, but we can generalize the games (which is what Hearn and Demain do), and see how the solving complexity changes with the size of the board. This is the only reasonable way to talk about the computational complexity of games.

Comment author: Kawoomba 13 August 2013 06:56:13AM 3 points [-]

You might also look at the computation complexity of solving the games.

You mean as another, mostly unrelated task.

Comment author: novalis 13 August 2013 07:37:43PM 2 points [-]

Well, it's not entirely unrelated, since jkaufman says:

Go is the most interesting of the three, and has stood up to centuries of analysis and play, but Dots and Boxes is surprisingly complex (pdf) and there used to be professional Checkers players.

The interest here is not provided by the complexity of the rules themselves, but by the complexity of solving the games (or, rather, playing them well, but this is probably related). One can easily imagine games with very complex rules that nonetheless admit simple strategies and are thus boring.

Comment author: novalis 13 August 2013 02:34:49AM 4 points [-]

You might also look at the computation complexity of solving the games. Games, Puzzles, and Computations, by Hearn and Demaine would be relevant here. Dots and Boxes is apparently NP-hard; a variant of Go called Rengo Kriegspiel might be undecidable; NxN Checkers is Exptime-complete.

Comment author: Eugine_Nier 09 August 2013 06:48:14AM 0 points [-]

I think some of it might be a case of the "Typical Mind Fallacy". Maybe if Linus yelled at you, you wouldn't be bothered at all. But I know that my day would be ruined, and I would be less productive all week.

The right comparison is to compare that to how much you'd be bothered if you had to clean up the mess left by an incompetent coworker. Or having to deal with an incompetent bogon in middle management.

Comment author: novalis 09 August 2013 05:29:26PM -1 points [-]

The right comparison is to compare that to how much you'd be bothered if you had to clean up the mess left by an incompetent coworker. Or having to deal with an incompetent bogon in middle management.

Unsurprisingly, I've had to deal with both of these things. It has never seemed to me that yelling at someone could make them more competent. Educating them, or firing them and replacing them seems like a better plan.

Comment author: Lumifer 07 August 2013 07:40:21PM 1 point [-]

Creating projects is easy; forking is hard.

Forking is pretty easy -- it's getting people to follow your fork that's hard.

I also don't think there are necessarily any actual roar-and-smash types.

Well, there are certainly enough programmers who prefer to discuss code in terms of "only a brain-dead moron could write a library that does foo" or "why is this retarded object making three fucking calls to the database for each invocation", etc.

And while people generally don't find it fun to be on the losing side, this does not stop them from seeking and entering competitions and competitive spheres. Consider sports, e.g. boxing or martial arts.

[Linus]: And I do it partly (mostly) because it's who I am, and partly because I honestly despise being subtle or "nice".

Steelman this. I am pretty sure that in the North European culture being "subtle or nice" is dangerously close to being dishonest. You do not do anyone a favour by pretending he's doing OK while in reality he's clearly not doing OK. There is a difference between being direct and blunt - and being mean and nasty.

I think it remains an open question whether Linus's style is in fact better than the alternative from the "get shit done" perspective.

As I said, Linus' style is proven to work. We know it works well. An alternative style might work better or it might not -- we don't know.

I suspect you have a strong prior but no evidence.

Comment author: novalis 07 August 2013 09:46:33PM *  3 points [-]

[Linus]: And I do it partly (mostly) because it's who I am, and partly because I honestly despise being subtle or "nice".

Steelman this. I am pretty sure that in the North European culture being "subtle or nice" is dangerously close to being dishonest. You do not do anyone a favour by pretending he's doing OK while in reality he's clearly not doing OK. There is a difference between being direct and blunt - and being mean and nasty.

I don't understand what you're saying here. Are you saying that anyone is proposing that Linus to act in a way that he would see as dishonest? Because I don't think that's the proposal. Consider the difference between these three statements:

  • Only a fucking idiot would think it's OK to frobnicate a beezlebib in the kernel.
  • It is not OK to frobnicate a beezlebib in the kernel.
  • I would prefer that you not frobnicate a beezlebib in the kernel.

The first one is rude, the second one is blunt, the third one is subtle/tactful/whatever. Linus appears to think that people are asking for subtle, when instead they're merely asking for not-rude. Blunt could even be:

  • When you frobnicate a beezlebib, it fucks the primary hairball inverters, so never do that.

So he doesn't even have to stop cursing.

As I said, Linus' style is proven to work. We know it works well. An alternative style might work better or it might not -- we don't know.

There are many FOSS projects that don't use Linus's style and do work well. What's so special about Linux?

I suspect you have a strong prior but no evidence.

I've run a free/open source project; I tried to run it in a friendly way, and it worked out well (and continues to do so even after all of the original developers have left).

I can also point to Karl Fogel's book "Producing Open Source Software", where he says that rudeness shouldn't be tolerated. He's worked on a number of free/open source projects, so he's had the chance to experience a bunch of different styles.

Comment author: Lumifer 07 August 2013 04:48:30PM *  1 point [-]

I think some of it might be a case of the "Typical Mind Fallacy"

Yes, I think the Typical Mind Fallacy plays some role in this. But then let's explicitly go around it. Let's postulate that the population of, say, qualified programmers, is diverse. Some are shy wallflowers, wilting from any glance they perceive as disapproving, some thrive in a rough-and-tumble environments where you prove your solution is better by smashing your opponent into bits. Most are somewhere in between.

This diverse population would self-sort by preferences -- the wallflowers would gravitate towards polite, supportive, never-a-harsh-word environments (in our case, OSS projects), while the roar-and-smash types will gravitate towards the get-it-done-NOW-you-maggot environments. Since OSS projects are easy to create and it's easy for developers to move from project to project, the entire system should evolve towards an equilibrium where most people find the environment they're comfortable with and stick with it.

Now, that seems to me a fine way for the world to work. But would you object to such a state of the world, after all, there are some projects there which are "mean" and where you (and likely some other people) would be uncomfortable and unproductive?

I'm sure there are studies available of what sorts of management are effective generally.

Oh, there are piles and piles of those. The only problem is, they all come to different conclusions (with a strong dependency on the decade in which the study was done).

I also think there might be a value difference, in that I do value fun pretty highly.

Put yourself into manager's shoes and consider the difference between instrumental and terminal values.

You, an employee/contributor, value fun highly. That is a terminal value for you. Being productive is a secondary goal and may also be an instrumental value (some but not all people are not having fun if they see themselves as being unproductive).

Now, for a manager, the fun of his employees/contributors/developers is NOT a terminal value. It's only an instrumental value, the true terminal value is to Get Shit Done.

Do you see how that leads to different perspectives?

Comment author: novalis 07 August 2013 06:25:19PM -1 points [-]

Since OSS projects are easy to create and it's easy for developers to move from project to project

Creating projects is easy; forking is hard. And nobody wants to create a new kernel from scratch. Kernel hackers don't really have a lot of options. So I don't think your theoretical world has anything to do with the real world. Also, it seems to me that culture doesn't end up contained within a single project; Linux depends on GCC, for instance, so the Linux people have to interact with the GCC people. Which means that culture will bleed over. I was recently at a technical conference and a guy there said, "yeah, security is perhaps the only community that's less friendly than Linux kernel development." So now it's not just one project that's off-limits, but a whole field.

I also don't think there are necessarily any actual roar-and-smash types. That is, I think a fair number of people think it's fun to lay a beatdown on some uppity schmuck. I've experienced that myself, certainly. Why else would anyone bother wasting time arguing with creationists? But I'm not sure there are a lot of people who find it fun to be on the losing end of this. This is an extension of Arguments as Soldiers. When you're having a knock-down, drag-out fight with someone, it's harder to back down.

Notice that the original example of a person in that category was Mannie O'Kelly -- a fictional character.

Put yourself into manager's shoes

[Linus]:

And I do it partly (mostly) because it's who I am, and partly because I honestly despise being subtle or "nice".

(later in that email, he does give a nod to effectiveness, but that doesn't seem to be his primary motivator).

I think it remains an open question whether Linus's style is in fact better than the alternative from the "get shit done" perspective. And the original quote implied, without evidence, that in fact it is. Not really sure why this is a "rationality" quote.

Comment author: Lumifer 07 August 2013 02:16:17AM 1 point [-]

...is good or bad advice

Do you think we have a basic difference in values or there's some evidence which might push one of us towards the other one's position?

You should be even more suspicious, then, of Linus

He has the huge advantage in that he actually delivered and continues to deliver. His method is known to work. Beware the nirvana fallacy.

Comment author: novalis 07 August 2013 05:53:31AM -1 points [-]

Do you think we have a basic difference in values or there's some evidence which might push one of us towards the other one's position?

That's a pretty good question.

Hypothesis: I think some of it might be a case of the "Typical Mind Fallacy". Maybe if Linus yelled at you, you wouldn't be bothered at all. But I know that my day would be ruined, and I would be less productive all week. So I assume that many people are like me, and you assume that many people are like you.

I would be curious about a controlled experiment, where free/open source project leaders were told to act more/less like Linus for a month to see what would happen. But I guess that's pretty unlikely to happen. And one confounder is that a lot of people might have already left (or never joined) the free/open source community because of attitudes like Linus's. We could measure project popularity (say, by number of stars on github) against some rating of a project's friendliness.

We might also survey programmers in general about what forces do/don't encourage them to work on specific free/open source projects.

I'm sure there are studies available of what sorts of management are effective generally. I'll ask my MBA friend. I did a two-minute Google search for studies about what cause people to leave their jobs generally, but found a such a variety of conflicting data that I decided it would need more time than I have.

These things could definitely influence me to change my mind.

I also think there might be a value difference, in that I do value fun pretty highly. That's especially true in the free/open source world, where nobody's getting rich, and where a lot of people are volunteers (this last is less true on Linux than on some other projects, but perhaps part of that is that all of the volunteers have been driven away)? But in general, I would like to enjoy the thing I spent eight (or twelve) hours a day on. And if even if this did make me somewhat less productive than I would be if I was less happy, I don't really mind that much.

View more: Prev | Next