Danger! Software Craftsmen at Work
Recorded at:
Danger ! Manifesto misinterpretation ahead
by
Guillaume L
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.
Re: Danger ! Manifesto misinterpretation ahead
by
Andy Dent
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)
Re: Danger ! Manifesto misinterpretation ahead
by
Javier Diaz
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 ...
Answers in Blogs
by
Gael Fraiteur
Robert Martin answered on thecleancoder.blogspot.com/2010/10/danger-softw....




Hello stranger!
You need to Register an InfoQ account or Login to post comments. But there's so much more behind being registered.Get the most out of the InfoQ experience.
Tell us what you think