4 ms·

> call someone names, curse at them, sarcastically suggest they should have been aborted, and many other such tactics. That's a positive change. But it also ou

> call someone names, curse at them, sarcastically suggest they should have been aborted, and many other such tactics. That's a positive change. But it also ought to be possible to say "this is a dumb idea" or to engage in friendly ribbing when someone does something dumb. These are good, healthy mechanisms in normal groups of people. Eliminate all teasing, and everyone is friendly on the outside and bitter and resentful on the inside. People should be teased for breaking things. There is such a thing as attempting to be too professional.

FuckOffNeemo 8y ago
I completely agree. Calling an idea dumb is candid, I'd consider it a breath of fresh air from corporate speak. I left my prior position for similar concerns, specifically 'Architects' who I'd called out (and rather abruptly so) when they quoted AWS as being 'not redundant and only have one DataCentre'. We're not talking a conversation from 10 years ago either. This was June last year! Comments or statements like that need to be shouted out of the room. I feel there's a finesse to be drawn and understood here. If some one states, AWS is single site and no one else in the room challenges the stupidity of the claim. Some one ought to. That guys/girl is a fucking idiot. But some one who perhaps needs to be coaxed or massaged into a different angle because their code base will grow 90% in size? Depending on the context that might be for the best. Or it might not be. Coming back to my earlier analogy. Hammers and scalpels are both honest. Different tools for different needs.
jancsika 8y ago
> But it also ought to be possible to say "this is a dumb idea" or to engage in friendly ribbing when someone does something dumb. "Friendly ribbing" doesn't translate well on a public mailing list, especially one with an international audience. > People should be teased for breaking things. Again, that doesn't work very well on a public mailing list, especially one with an international audience. If people break things they should be told clearly and precisely what they did wrong. > There is such a thing as attempting to be too professional. Do you have an example of a current FLOSS project that is too professional?

FuckOffNeemo 8y ago

I completely agree. Calling an idea dumb is candid, I'd consider it a breath of fresh air from corporate speak. I left my prior position for similar concerns, specifically 'Architects' who I'd called out (and rather abruptly so) when they quoted AWS as being 'not redundant and only have one DataCentre'. We're not talking a conversation from 10 years ago either. This was June last year! Comments or statements like that need to be shouted out of the room. I feel there's a finesse to be drawn and understood here. If some one states, AWS is single site and no one else in the room challenges the stupidity of the claim. Some one ought to. That guys/girl is a fucking idiot. But some one who perhaps needs to be coaxed or massaged into a different angle because their code base will grow 90% in size? Depending on the context that might be for the best. Or it might not be. Coming back to my earlier analogy. Hammers and scalpels are both honest. Different tools for different needs.

jancsika 8y ago

> But it also ought to be possible to say "this is a dumb idea" or to engage in friendly ribbing when someone does something dumb. "Friendly ribbing" doesn't translate well on a public mailing list, especially one with an international audience. > People should be teased for breaking things. Again, that doesn't work very well on a public mailing list, especially one with an international audience. If people break things they should be told clearly and precisely what they did wrong. > There is such a thing as attempting to be too professional. Do you have an example of a current FLOSS project that is too professional?