quick reference card pour l’ecocycle


Mise en ligne d’une quick reference pour l’ecocycle et création d’une section référence cards (dans le menu). Car il existe peu de littérature de synthèse disponible pour introduire l’ecocycle finalement ( Rien que des gros trucs à lire, ou pas trop évidents), et je vais en avoir besoin dans les prochains article sur les #transformation .

Par contre, je fais ça en anglais, pour que ca serve un plus grand public, vue que c est plutôt « niche » comme sujet. Des objections ? des opinions ? un intérêt à avoir cela en français ? Si il y a un intérêt exprimé, je traduis…

Presentation Introducing to Diffusion of Innovation, with Sociology Patterns and Haskell

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] [15] 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..)

Adapted Beckard Change Model
]4 Adapted Beckard Change Model

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]
  • [http://www.infoq.com/presentations/Socio-PLT]

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 ?

[15] P. Coburn. The Change Function: Why Some Technologies Take Off and Others Crash and Burn. Portfolio Hardcover, 2006.

%d blogueurs aiment cette page :