Software Engineering Has Its Own Political Axis From Conservative To Liberal
An anonymous reader writes "Steve Yegge is back at it again. This essay is on the notion that software engineers range from conservative to liberal in their notion of software and how it should be built. He says, 'Just as in real-world politics, software conservatism and liberalism are radically different world views. Make no mistake: they are at odds. They have opposing value systems, priorities, core beliefs and motivations. These value systems clash at design time, at implementation time, at diagnostic time, at recovery time. They get along like green eggs and ham. I think it is important for us to recognize and understand the conservative/liberal distinction in our industry. It probably won't help us agree on anything, pretty much by definition. Any particular issue only makes it onto the political axis if there is a fundamental, irreconcilable difference of opinion about it. Programmers probably won't — or maybe even can't — change their core value systems. But the political-axis framework gives us a familiar set of ideas and terms for identifying areas of fundamental disagreement. This can lead to faster problem resolution.'"
Does this mean they sit on a plate waiting to get eaten?
What he really means is, when it gets done, 1 group wants to give it out for free and the other wants to charge lots of money and DRM it lol.
(cue left-wingers saying "that's the right wing" and right-wingers saying "that's the right wing")
Inser ftfy meme here.
Don't be a h8r.
Because, you know, there are like only two ways to code: Liberal and Conservative. There certainly can't be a THIRD way like Funny or Informative or Surprise and Fear. Damn! Or Ruthless Efficiency!
I'm definitely a Surprise programmer. I'm surprised when it works.
Well, I never heard of him, but he does have a wikipedia entry so he can't be that obscure.
Free Martian Whores!
Why are there people who try to create binary conflicts when there really aren't any?