Archive

Posts Tagged ‘learning’

No, I’m not a mason

October 27th, 2010 8 comments

“Danger! Software Craftsmen at Work”

Now that’s a great title! I wish I could have used that for this post. Instead, that’s the title of the QCon 2010 David Harvey presentation that is the foundation of this blog entry.

In his talk Mr Harvey places the “Software Craftsman” ideas and practices somewhere between distracting and dangerous, and claims these ideas builds a wall between developers, organisations and customers.

I claim he exaggerates the dangers, but I welcome the stirring in the pot and I do agree in parts of what he says, mainly regarding the emotional associations of the metaphors used by the Software Craftsmanship movement.

I agree with Uncle Bob‘s views on “The Empty Manifesto“, “Engineering vs. Craftsmanship” as well as “The Craftsman Connotation“, the last one being the one I’m expanding upon here. Plus, he sums the whole thing up nicely, so if you haven’t yet, please read that one first. (Yes, you may read Gael Fraiteur’s post too if you must, but please then leave a trail of breadcrumbs so you find your way back here.)

A masonry brick wall

So, on to David’s talk:

My first issue is with his first analogy; why would wearing a white T-shirt with printed instructions make it any worse walking into the lion’s cage? …ok sorry, that’s not the point. And, to give hime some credit, the print was in fresh blood and lions tend to like that, so fair enough, I’ll let it slide. After all, he was standing inside the lion’s cage saying it.

And thanks for putting yourself in that cage, David. It was refreshing to see an alternate slash controversial view presented on this subject.

My biggest issue

My biggest issue, however, is that he picks on a great movement with the noble goals of achieving a larger recognition of software development as a profession and to “raise the bar of professional software development”. Why would anyone want to do that? That’s just mean.

Or, is it? He is, after all, a developer himself…

Please, let me shine some light on an important point he makes, one that I’ve brought up before: We should be careful with our wording! We are already perceived as loners, nerds, Storm Troopers sleeping in line for Star Wars premiers. We don’t need to enforce that perception.

For me the timing of watching this presentation was great. It aligned perfectly with a conversation I had the other day:

The conversation

I was sitting out on the lawn, (re)reading a book* about apprenticeship and craftsmen, when my neighbour approached me.

-Are you working?
-Yep, reading up on some important professional elements.
He shot a quick look at the cover.
-But aren’t you in IT?

I began explaining, but it wasn’t until I started using words like professional instead of craftsman and mentoring instead of apprenticeship and that the book was really about learning and improving that the coin really dropped and the conversation took off. Turns out he, being an ambulance driver (amazingly enough, the very one that drove me and my wife to the hospital six months ago, when our bub #4 decided he wanted out in the middle of the night), knew and practiced many of these patterns. New ambulance drivers work with experienced ones to pick up on the large part of that profession consisting of working in the field, in an often critical atmosphere.

-They have to. Can’t read that in a book.
-So ok, you do that too, he said, I get it. Cool. But what with all the old guild talk? You’re not a mason, are you?

Touché!

So, why do we fight so hard for recognition?

Well, for one, it’s still a fairly young profession, but I also think some of it has to do with our characteristics. Software developers are smart, analytical people, lacking the social and communicative skills required for many other professions. (Generalising. Trying to make a point here. Moving on.)

I don’t care if you’re socially inept, as long as you can code. It’s actually better that way, since you’re going to spend most your waking hours in the basement anyway.

This has changed, greatly and quickly, and we are now in contact with the users, the business, no longer sitting in the basement. But even so, to the outside world that’s still us, the loners.

We see all that – we’re smart and analytical remember – and we’re tired of standing back to the sports jocks from the school yard, now turned corporate leaders. And we just don’t understand why people have such a hard time seeing the complexity, the necessity, the importance of what we do, just because it’s not tangible.

So, maybe we get a little bit too eager to get that recognition and forget there’s a gap that needs bridging first. (…and now, also a brick wall to tear down. See, we’re not making it easy on ourselves.)

Bridging the gap

That gap will be brigded though, sooner or later, through continously working on doing what we should do and doing it well. I agree with David’s advice; developers, stick to what Kent Beck described as the four basic activities of XP:

-Listening
-Testing
-Coding
-Designing

Do them well and stop worrying so much about recognition and acknowledgement. And by all means, use whatever names and metaphors you want for learning and improving, but do it internally. On the outside, make sure our organisations and customers understand what we’re doing too.

And anyone suggesting writing software is not hard, not a real profession, is welcome to come and give it a go…

* Not just “a book”, ladies and gentlemen. The Book! Apprenticeship Patterns – Guidance for the Aspiring Software Craftsman, by Dave Hoover and Adewale Oshineye. Read it. Please do. For your own sake.

(Photo courtesy of Shutterstock)

Mastering a new skill

April 15th, 2010 No comments

They have a game here in Australian schools called Handball. No, it has nothing whatsoever to do with the Olympic sport Handball. So, what is it then? I’ll tell you in a minute…

I have two school kids (so far). This particular story will include my son who is six. Moving here to Manly late January and starting school just six days later, we where quite eager to see how they would cope, especially him knowing hardly any English, but for a few words. We weren’t particularly worried though; he’s a smart kid and also quite confident and secure. Plus, he loooves anything sports. That always helps a young guy at school.

It didn’t take long to see that handball was the thing at school. The kids play it every recess as well as before and after school. Baltazar wanted to know right away how to play it so I asked a couple of kids to teach him.

So, without further due, please let me introduce the rules of handball:

BigFooty: Who used to play handball (aka four-square) back in school?

Too much for you? I understand completely. It’s a complicated game in all its apparent simplicity. Add to the above rules some Manly(?) specific features like Skillage, Rollings, Grabs, Poison etc. – most of them being dynamic, i.e. dictated by the owner of the ball and/or the current King – and you have an intricate, fast paced game that I for one have trouble understanding even after all these hours of watching and even playing myself.

So, how can a poor six year old kid from the cold north learn this in such a short time without even knowing the language?

…actually, he hasn’t just learnt it; he masters it. He was just unofficially crowned the Best Year 1 Player at Manly West Public School, among 120+ year 1 students (not all of them playing handball of course, but still…)

I’ll tell you why:

  • Because he has passion!
  • Because he’s not afraid to go up against the best in the field.
  • Because he has stamina – he’s not giving up.
  • Because he has fun.
  • Because he’s entering the task with an open mind.
  • Because he just jumps right into it, he doesn’t waste too much time on theory.
  • Because he wants to improve, he wants to be the best!
  • (And of course; because he’s got talent.)

These qualities that come so easy and naturally to a six-year-old; how come we adults find them so hard?

Mastering a new skill is scary business; we tend to focus too much on the vast distance separating ourselves from the current masters. But as with any other seemingly insurmountable obstacle, it helps to break it down into smaller parts.

So, that’s what I’m going to do.

My intentions are to examine these attributes a little closer to try to map out an understanding of how to be great at something and have fun while you’re doing it.

Stay tuned…

Tags: ,