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]
  • []

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.

What moves me

When preparing the root Cause Analysis at the 1st Person, I realize I was listing feelings in fact, or values, so I did the motivator exercise from Jurgen Appello, i.e. :

  1. classifying your motivation in your personal order, then
  2. perceiving the delta for a given situation ( target would be here is a Haskell job) ( the + /- here below )

interesting findings:

  • mainly gains, no loss
  • if I would map these values to my currents jobs, I am FAR offset… 1 to 3 are barely touched…
  1. goal +++
  2. curiosity ++
  3. freedom +++
  4. mastery ++
  5. honor
  6. power
  7. relatness – (physical isolation) ++ virtual community
  8. status
  9. acceptance
  10. order

Why did I created this blog ?

The Short Story:

  • I want to have a job I like, that is: Experiment with Haskell. I realized it will not happen by magic and that I may have to create it. I also realize I will not be able to do it alone. nor would it be fun. And I will need other Haskell lovers feedback to keep me going. and Celebrate.
%d blogueurs aiment cette page :