Another reason not to hire software craftsmen

From this:

“While I love software, I love code more. If you ask my past employers and customers, they will tell you that I can get stuff done, too. However, I often code just to learn. This is an aspect of Software Craftmanship that is sometimes overlooked: Yes, we want to ship working software. However, we must always strive to become better at our craft, and that means practice. That means writing code for code's sake. That means obsessing over details.”

And when are you going to write code for code’s sake?  On my time or yours?

And how are you going to determine when you are becoming better?  Based on your own whims?  The whims of whatever the latest obsession is?

And what else could you be doing?  Talking with the business and learning more and more about the domain on which you are tasked to work, perhaps?

By all means, people should strive to get better at what they do, but not in some dogmatic, unthinking, wasteful way.

Dan North said it well (and read the whole thing, if you do and still think you should unit test properties, you are part of the problem, not the solution):

“I would love to see someone rewrite the Software Craftsmanship Manifesto in terms of getting results and delighting customers. I don’t want “steadily adding value,” I want “amazing their customers every day!” Software craftsmen should be egoless, humble, with a focus on the outcome rather than the code or the process. I’d like a call to arms to stop navel-gazing and treat programming as the skilled trade that it is.

No-one wants your steenking software – they want the capabilities it gives them, and they want those yesterday.”


posted on Monday, March 11, 2013 12:41 PM Print
No comments posted yet.

Post Comment

Title *
Name *
Comment *  
Please add 5 and 3 and type the answer here: