temps estimé pour lire ce billet : 1 minutes
Just found (out of Serendipity) an Interesting presentation ( video plus slides) introducing to Diffusion of Innovation with Sociology / Social Patterns, mentioning several times Haskell. Good introduction to a mix of techniques for whoever interested in Haskell proselytism, and go to market strategy, drawing from Change management and Technology adoption lifecycle / Tipping Point, etc, in a pragmatic way.
The « switching cost » approach (perceived adopted gain / perceived adopted pain >1 ) [Coburn]  introduced at 00:50 , is interesting to show where you can try to lower the pain, or augment the perceived gain. I now understand better the effort of those trying to explain monads in C++ , or Edsl in Scale/ Java, etc, i.e. lower the denominator.
It also reminded me of the Beckard formula for change, saying in a nutshell that you not only need to be dissatisfied with the present situation to commit to a change, but also perceived HOW to change it, ie have a vision , and what are the next steps … ( Exactly what this site is about..)
more links and details in a paper on Leo A. Meyerovich site :
- [Leo A. Meyerovich and Ariel S. Rabkin. Socio-PLT: Sociological Principles for Programming Language Adoption. Onward! 2012]
By the way, who could point some prior work listing the benefits of Haskell ? ( FP/ HOF, type safety, EDSL..) and possibly pain points for starters ? anybody interested in a (serious) discussion on these, to feed a strategy ?
 P. Coburn. The Change Function: Why Some Technologies Take Off and Others Crash and Burn. Portfolio Hardcover, 2006.