Hackers By Alan Moore
the Computer Community
What is harnessing collective intelligence?
It was Eric Raymond in his famous article ‘The Cathedral and the Bazaar’ who shared with us the insight that ‘with many eyes all bugs are shallow’. What he meant was, as in the case of the Linux open source code, where many people are able to contribute their individual knowledge to a coding problem collectively – the ability to solve that problem rises exponentially. This process is also described as co-creation, an idea whose time has now come and moved centre stage. The result of the open source approach to harnessing and applying the knowledge and collective wisdom has been proven repeatedly in the fields of science (NASA Mars project, and Galaxy Zoo in the UK), R&D (Innocentive, a platform for solving scientific challenges, and YourEncore – a collaborative R&D platform), commercially with Local Motors in the US, TopCoder and politically with Ushahidi. These are but a small sample of a much bigger list.
The hacker ethic and pattern recognition
In my latest book ‘No Straight Lines’, Chapter 8 explores peer-to-peer entrepreneurial learning, innovation in healthcare, political institutional design, farming and agriculture, crisis management and even the plight of the Achuar tribe in the Amazon. All the examples are relevant because they all faced various crisis situations that were so
volatile they presented a deadly endgame. It was the ability of the entrepreneurs or groups of dispersed individuals or situated communities to apply innovative thinking and action that enabled them to adapt to ambiguous, challenging and dangerous situations. They were able to identify a new pattern, a new way of doing things – which was not seen as risky, but eminently doable. Consequently they have all transformed aspects of healthcare, economies, society and politics. There is indeed artfulness, an underlying creativity that is able to operate because the creators have all allowed themselves to imagine what others thought to be impossible. Not because they think it’s a nice thing to do, but because there was a very pressing need – in essence all obstacles must be overcome. They had to design for transformation. So in hacking the future we must ask important questions, for example: How do we remove the acute volatility and therefore risk of running large scale farms by thinking about the problem as a systems challenge? How do we discover a new sustaining business model by enabling our customers to constantly co-create the future of our company, meaning we co-create better products, services, and increase
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59