comparing opensource software development to global guerilla warfare tactics

i’ve been reading a lot at the global guerillas blog. and i’m just floored by this guy’s thought processes. the connection of disparate models is just amazing. here he compares the opensource software model to that of the global guerilla warfare model.


Release early and often. Try new forms of attacks against different types of targets early and often. Don’t wait for a perfect plan.

Given a large enough pool of co-developers, any difficult problem will be seen as obvious by someone, and solved. Eventually some participant of the bazaar will find a way to disrupt a particularly difficult target. All you need to do is copy the process they used.

Your co-developers (beta-testers) are your most valuable resource. The other guerrilla networks in the bazaar are your most valuable allies. They will innovate on your plans, swarm on weaknesses you identify, and protect you by creating system noise.

Recognize good ideas from your co-developers. Simple attacks that have immediate and far-reaching impact should be adopted.

Perfection is achieved when there is nothing left to take away (simplicity). The easier the attack is, the more easily it will be adopted. Complexity prevents swarming that both amplifies and protects.

Tools are often used in unexpected ways. An attack method can often find reuse in unexpected ways.

really mind blowing ideas. it’s got me thinking a lot about how these kinds of ideas can be applied activism [though, i do hate that word].