What Developers Can Learn From Anonymous
snydeq writes "Regardless of where you stand on Anonymous' tactics, politics, or whatever, I think the group has something to teach developers and development organizations,' writes Andrew Oliver. 'As leader of an open source project, I can revoke committer access for anyone who misbehaves, but membership in Anonymous is a free-for-all. Sure, doing something in Anonymous' name that even a minority of "members" dislike would probably be a tactical mistake, but Anonymous has no trademark protection under the law; the organization simply has an overall vision and flavor. Its members carry out acts based on that mission. And it has enjoyed a great deal of success — in part due to the lack of central control. Compare this to the level of control in many corporate development organizations. Some of that control is necessary, but often it's taken to gratuitous lengths. If you hire great developers, set general goals for the various parts of the project, and collect metrics, you probably don't need to exercise a lot of control to meet your requirements."
What the group has to teach is simple: If all you want is to disturb the normal process, and highlight certain aspects, then you don't need much organization.
Wake me up when anonymous actually produced something non-trivial.
I was reading "The mythical man-month" only this weekend, which starts with the observation that "everyone knows" that two kids in a garage can do more than a corporate development team, and then points out that, if this was actually true without caveats, corporations would hire two kids in a garage every time. There's a difference between producing a standalone program and developing/maintaining a product system.
Virtually serving coffee
The only lesson here is that creating chaos doesn't require any kind of organizational structure (which is almost tautological). Producing something orderly is a whole different question, and unless you happen to have an infinite number of monkeys at your disposal, the chance of that happening in a finite period of time is pretty damn improbable.
http://alternatives.rzero.com/
And it has enjoyed a great deal of success - in part due to the lack of central control.
But Anonymous hasn't really done anything that requires the true contributive efforts of more than a few people at a time. LOIC doesn't count, because "here, run this" isn't in the same ballpark as actually contributing code to a project. The person/people who wrote LOIC still exercised control over the actual software and made decisions about what features went in and what didn't.