Jan 222010

Update: Questions on Twitter about this post made us realize that more background from Jens’ call for papers would have clarified the issues in the debate over the current state of programming. In particular, on the bias that’s become entrenched over the past 40 years toward engineering that has created a “disregard for programming [that] has taken deeper and deeper roots in our professional culture”, and has contributed to the rise of the software craftsmanship movement. Please read the full call for papers and consider joining in on what’s shaping up to be a lively debate!

The upcoming April 2010 Cutter IT Journal, guest edited by Jens Coldewey, focuses on the current state of programming as a craft — both in agile and traditional programming environments. We’ll explore the ideas, concepts and implications of software craftsmanship on software development organizations. We invite anyone who is interested to send us an abstract for consideration.

TOPICS OF INTEREST MAY INCLUDE (but are certainly not limited to) one or a combination of the following:

  • How has software craftsmanship been incorporated into training and education?
  • What are the organizational implications of software craftsmanship?
  • What kind of surveys /research are being done in the software craftsmanship arena?
  • What are the “war stories” about organizations that embark on craftsmanship?
  • What are the business effects of software craftsmanship?
  • What are effects of craftsmanship on project success?
  • What is the current state of the software craftsmanship community? Which route might it take in the future?

Cutter IT Journal Call for Papers


Christine Generali

Christine Generali is a Group Publisher for Cutter Consortium – responsible for the editorial direction and content management of Cutter’s flagship publication, Cutter IT Journal.


 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>