• Weblog
• Why CPH127?
• Cabin crew
• Newsstand
• Views
• Links

« Service-announcement from the crew | Main | Workflow - a leadership challenge! »

“Open Source”-thinking = Optimal Design Process?

I've been writing about "Open Innovation" before and over the past months I've been s“struggling” with thoughts about how to apply OS with the design process. Is it possible, any ideas, cases?

Eric Raymond's The Cathedral and the Bazaar, a wonderful essay about the "bazaar" (AKA "open source") approach to creating cool stuff.  Please do read it, but in case you can't, here are my favorite bits:

• "...you often don't really understand the problem until after the first time you implement a solution. The second time, maybe you know enough to do it right. So if you want to get it right, be ready to start over at least once."
• "...I think Linus' cleverest and most consequential hack was not the construction of the Linux kernel itself, but rather his invention of the Linux development model."
• "Release early. Release often. And listen to your customers."    
• "Given enough eyeballs, all bugs are shallow...  In the cathedral-builder view of programming, bugs and development problems are tricky, insidious, deep phenomena. It takes months of scrutiny by a dedicated few to develop confidence that you've winkled them all out. Thus the long release intervals, and the inevitable disappointment when long-awaited releases are not perfect.  In the bazaar view, on the other hand, you assume that bugs are generally shallow phenomena - or, at least, that they turn shallow pretty quick when exposed to a thousand eager co-developers pounding on every single new release. Accordingly you release often in order to get more corrections, and as a beneficial side effect you have less to lose if an occasional botch gets out the door." 
• "Often, the most striking and innovative solutions come from realizing that your concept of the problem was wrong." 
• "I think it is not critical that the coordinator be able to originate designs of exceptional brilliance, but it is absolutely critical that the coordinator be able to recognize good design ideas from others."

In relation to handle small pieces - but loosely joined - I think the metaphor is good and applicable, but is it sufficient?

Posted by Hans Henrik H. Heming on August 24, 2005 in Design Process | Permalink

Permanent URL to this entry: http://www.cph127.com/cph127/2005/08/open_sourcethin.html

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8345592f969e200d835536a2669e2

Listed below are links to weblogs that reference “Open Source”-thinking = Optimal Design Process?:

Comments

Post a comment