Tuesday, May 1, 2007

The programming language cycle

Love this programming language cycle from Megginson Technologies:



  1. Elite (guru) developers notice too many riff-raff using their current programming language, and start looking for something that will distinguish them better from their mediocre colleagues.


  2. Elite developers take their shopping list of current annoyances and look for a new, little-known language that apparently has fewer of them.


  3. Elite developers start to drive the development of the new language, contributing code, writing libraries, etc., then evangelize the new language.


  4. Sub-elite (senior) developers follow the elite developers to the new language, creating a market for books, training, etc., and also accelerating the development and testing of the language.


  5. Sub-elite developers, who have huge influence (elite developers tend to work in isolation on research projects rather than on production development teams), begin pushing for the new language in the workplace.


  6. The huge mass of regular developers realize that they have to start buying books and taking courses to learn a new language.


  7. Elite developers notice too many riff-raff using their current programming language, and start looking for something that will distinguish them better from their mediocre colleagues.

No comments: