InfoQ

InfoQ

Presentation

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Recorded at:
Recorded at

Danger! Software Craftsmen at Work

Presented by David Harvey on Oct 12, 2010 Length 00:52:22     Download: MP3
     Slides
Sections
Process & Practices,
Architecture & Design
Topics
QCon ,
Software Craftsmanship ,
Agile ,
Conferences ,
QCon London 2010
The next QCon is in London March 5-9, Join us!
 

How would you like to view the presentation?

In case you are having issues watching this video, please follow these simple steps to help us investigate the issue:
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
Summary
David Harvey is concerned that some of the craftsmanship discourse can end up creating a barrier between the software builders and their customers, suggesting that the current Software Craftsmanship movement is a distraction, even a danger.

Bio
David Harvey has over 20 years experience in designing, building and managing software development. Now he is working as an agile coach and consultant in some of Europe's largest companies. He has helped companies adopting C++ and OOP, and has spoken on patters, distributed computing, software architecture and practice at various conferences, being chair for OT99 and SPA2009.

About the conference
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community.QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

  • This article is part of a featured topic series on Agile
Danger ! Manifesto misinterpretation ahead by Guillaume L Posted
Re: Danger ! Manifesto misinterpretation ahead by Andy Dent Posted
Re: Danger ! Manifesto misinterpretation ahead by Javier Diaz Posted
Answers in Blogs by Gael Fraiteur Posted
  1. Back to top

    Danger ! Manifesto misinterpretation ahead

    by Guillaume L

    If I understood it well, David states that the Software Craftsmanship Manifesto is too tame to be called a manifesto while McBreen's book is a proper manifesto but too extreme to be followed. Should we deduce that whatever it is they're about, manifestos are useless ?

    I think the presentation completely misses the main point that triggered the creation of the SCM in the first place, which is the need for recognition of software development as a profession.

    Since computers exist we have seen various organizations being formed by IT people and the IT industry in general, but not really a wide-scale joint effort of programmers as a self-proclaimed community. Yet when you think of it, it's high time that we get a little more considered by "the outside world". We're often regarded as obscure fifth wheels, silent executants, and sometimes even deprived of outside recognition that we know how to do our job and that this job requires a certain skill.

    As with any movement whose goal is to assert an identity (civil rights movements and teenage are examples), before acknowledgement comes, before pride comes, the first step is a self-defense reflex. It's about rebelling and gathering forces to oppose the status quo. That's what the Craftsmanship movement is trying to do, to connect developers together around the formation of a craft, a set of practices widely recognized as state-of-the-art. To put forward the profession as one that requires great expertise and not just typing skills, and its members as people who constantly seek improvement and don't just go through the same basic tasks and mistakes over and over.

    "Software Craftsmanship Manifesto: A Call to Arms" was the title of an article that appeared here on InfoQ shortly after the manifesto was released. And this is for a reason. The paper captured precisely what for me was the original spirit of the SCM initiative. You don't "call people to arms" just for the pleasure of showing how crazy developers are and how much they like to oppose to other professions. It's a necessary struggle on the path towards recognition.

  2. Back to top

    Re: Danger ! Manifesto misinterpretation ahead

    by Andy Dent

    @Guillaume Sorry, I have to disagree with your assertion. Professional bodies for software developers have been around for decades earlier than the SCM movement. I'm a senior member of the Australian Computer Society which as a society has been member of the Australian Council of Professions for several years. You should also look into the history of ACM.

    I also think it's ironic that you talk about "IT people and the IT industry" because, increasingly, I see them as being independent of what software development is about. The vast majority of IT people and IT projects are about installation, management and configuration of software. They have little to do with development. Speaking from a 25+ year perspective, which has been spent doing mostly software development (I was a sysadmin in the eighties), I'm concerned about a growing LOSS of professionalism. I think the SCM movement is not so much a "finally we're getting professional" as an attempt to regain those attitudes and I think it's very significant that many of the people driving it are my peers.

    I remember when "design at the keyboard" was a slur. Nowadays it almost seems to be praise - someone who actually does design.

    (yes I know that's a gross exaggeration and I hope it remains as such)

  3. Back to top

    Re: Danger ! Manifesto misinterpretation ahead

    by Javier Diaz

    @Andy sorry, but you are from another generation and the land down under, where prostitution is legal (sorry for the clichés). Here, on the other side, the world is pretty much as Guillaume describes (actually it is much worse ...). Just substitute Sw Engineering by commercial or enterprise development and things start to fit into shape. The fact that Sw Engineering got co-opted by enterprisey snake oil in the late eighties should be enough for a senior like you to realize what this is all about (as you probably neither have any methodology book hidden anywhere). I was fed faux methodology by the educational machinery, I was informed by the commercial world that we are a commodity ... In my country ACM is a magazine subscription service, nothing more. My degree is worth zilch, unions recognize me as a "Metal" worker and the professional categories of sw are from the 60s at the latest. I live in Europe, by the way ...

    Mixing this with whether you use paper, a blackboard or an IDE to develop your thoughts has ZERO to do with it: just accept that TIMTOWTDI. Just speaking from the perspective of someone who started using computers in his infancy (about 30+ years ago).

    I hope that you also see this as a gross exageration ...

  4. Back to top

    Answers in Blogs

    by Gael Fraiteur

    I commented on this talk on my blog at www.sharpcrafters.com/blog/post/Why-Should-We-C....

    Robert Martin answered on thecleancoder.blogspot.com/2010/10/danger-softw....

Educational Content

Eventually Consistent HTTP with Statebox and Riak

Bob Ippolito explains how to solve concurrent update conflicts with Statebox, an open source library for automatic conflict resolution, running on top of Riak.

Java.next

Erik Onnen attempts to demonstrate that Java is still the best programming language for the JVM if simplified idioms are used along with proper tooling.

Evolution in Data Integration From EII to Big Data

Approaches to integrating data are changing with emergence of cloud computing.

Winning Hearts and Minds: How to Embed UX from Scratch in a Large Organization

Michele Ide-Smith presents the lessons learned in the process of introducing UX principles and techniques into a large organization through a series of small steps.

LMAX Disruptor: 100K TPS at Less than 1ms Latency

Dave Farley and Martin Thompson discuss solutions for doing low-latency high throughput transactions based on the Disruptor concurrency pattern.

Thoughts on Test Automation in Agile

Rajneesh Namta shares his thoughts, experiences, and some of the critical lessons learned while implementing software test automation on a recent Agile project.

Actor Interaction Patterns

Dale Schumacher presents several patterns of actor interaction that can be used in collaborative programs written in any language.

Scalaz: Functional Programming in Scala

Rúnar Bjarnason discusses Scalaz, a Scala library of pure data structures, type classes, highly generalized functions, and concurrency abstractions to perform functional programming in Scala.