Re:The cult of design dictatorship (2012)
by coldtea on Sunday May 26, 2013 @01:41PM
(#5771768)
>Ah the whine of the open source developer who wonders why the average joe finds OSS unusable and impregnable.
No, the whine of the open source developer who knows why the average joe finds the OSS project he talks about unusable and impregnable: the BS decisions of "designer dictators" that alienate the users.
>So either you don't understand his article, or he's applying a generalisation drawn from Gnome3 and then deliberately applying it to the wider world. Which?
Or, you don't understand the obvious: that things that hold for Gnome 3 can also hold for a wider world -- and that some of them (like a friendly decision process) can be especially important for OSS projects.
Reading comprehension problems?
> Perhaps you could spend "fainting" (sic)
>I'm obliged to point out, with a sense of delicious irony, that you are using sic incorrectly ;)
Wrong again. I only forgot the words "less time" between spend and fainting. As for "sic" I used it as it is meant to be used. It has no hard dependency on the tense or form of the word used -- ("feel faint" vs "fainting"). It just means that those were your words (even if adjusted to fit the quotation's syntax).
>>It's not like most designers working in web/software startups are trained professionals,
>What? Yes, they are.
Oh, I'm afraid they are not. You can count the number of them that have a university degree in HCI in one hand.
>I guess there's an inherent risk with drawing _massive, sweeping generalisations_ from "I've met some of these"
Yes, it's called deductive reasoning. You should try it. It's not like there's an infinite number of startups either -- so it can also be exhaustive or near exhaustive sampling.
>1. If a designer is doing their job properly, then the characteristics described in the original article all hold true, but the outcome is successful so nobody cares.
2. The point laboured in the article is, essentially, that design is not a democracy and you should "go home" if you don't like a product. I counter that this is a platitude: it could be true of any product ever made.
OK, so your argument is wrong. (1) is a statistical noise (a few highly talented designer arseholes) so for all practical cases the bad end result the article laments holds true.
>My point was: But so what? Every single piece of software is made with opinion behind it.
Which is a useless platitude in itself. The important thing is the degree of opinion in each software. Others are "taking or leave it and fuck you", and others listen to their team/community/users.
>That's true of everything from bottled water to delivery pizza.
Not really. There are "designer" pizza places that only sell you a specific kind and fuck off if you don't like it. And there are places that let you design your own pizza, sandwich, coffee, whatever. And places in between.
No, the whine of the open source developer who knows why the average joe finds the OSS project he talks about unusable and impregnable: the BS decisions of "designer dictators" that alienate the users.
>So either you don't understand his article, or he's applying a generalisation drawn from Gnome3 and then deliberately applying it to the wider world. Which?
Or, you don't understand the obvious: that things that hold for Gnome 3 can also hold for a wider world -- and that some of them (like a friendly decision process) can be especially important for OSS projects.
Reading comprehension problems?
> Perhaps you could spend "fainting" (sic) >I'm obliged to point out, with a sense of delicious irony, that you are using sic incorrectly ;)
Wrong again. I only forgot the words "less time" between spend and fainting. As for "sic" I used it as it is meant to be used. It has no hard dependency on the tense or form of the word used -- ("feel faint" vs "fainting"). It just means that those were your words (even if adjusted to fit the quotation's syntax).
>>It's not like most designers working in web/software startups are trained professionals, >What? Yes, they are.
Oh, I'm afraid they are not. You can count the number of them that have a university degree in HCI in one hand.
>I guess there's an inherent risk with drawing _massive, sweeping generalisations_ from "I've met some of these"
Yes, it's called deductive reasoning. You should try it. It's not like there's an infinite number of startups either -- so it can also be exhaustive or near exhaustive sampling.
>1. If a designer is doing their job properly, then the characteristics described in the original article all hold true, but the outcome is successful so nobody cares. 2. The point laboured in the article is, essentially, that design is not a democracy and you should "go home" if you don't like a product. I counter that this is a platitude: it could be true of any product ever made.
OK, so your argument is wrong. (1) is a statistical noise (a few highly talented designer arseholes) so for all practical cases the bad end result the article laments holds true.
>My point was: But so what? Every single piece of software is made with opinion behind it.
Which is a useless platitude in itself. The important thing is the degree of opinion in each software. Others are "taking or leave it and fuck you", and others listen to their team/community/users.
>That's true of everything from bottled water to delivery pizza.
Not really. There are "designer" pizza places that only sell you a specific kind and fuck off if you don't like it. And there are places that let you design your own pizza, sandwich, coffee, whatever. And places in between.