sc != SC
software craftsmanship is not the same thing as Software Craftsmanship (TM)
The act of writing code in software development…

…occurs on but one card occupying a single position on the Kanban board.

posted @ Sunday, January 16, 2011 4:15 PM | Feedback (0)
Response to Mark Nijhof about Software Craftsmanship

Due to the previous post about moderation issues here, I missed a comment that Mark Nijhof made which I think is important, so I want to repost his comment and my response, and then add to it. Mark said: “In my definition a Software Craftsman finds delivering value the biggest reason to deliver quality, because he knows that stuff will change and these changes will be easier to deal with in quality deliverables (not just code). The continues learning is because he knows that in order to succeed in the above taks he needs to know his options...

posted @ Thursday, December 16, 2010 8:25 PM | Feedback (2)
Devops–A good thing

The fact that it talks about a ‘movement’ makes me a bit wary (“manifesto” anyone?), but there’s this thing called Devops that falls into my “freaking obviously good” category enough that I’m willing to ignore that. I’ve talked about this sort of stuff a lot (though am way too busy/lazy to link all the relevant posts), but let me talk about a typical non-Devops example. Separation of Duties Working the last few years for all sorts of those “too big to fail” type companies, one of the standard things that you run into is “Separation of Duties.” ...

posted @ Sunday, November 14, 2010 4:21 PM | Feedback (1)
Judging Cost vs. Risk in Testing

Derick Bailey has a good post about determining the cost vs. value of doing testing.  No one who’s read this blog will be surprised that I particularly like this: “There is a cost associated with a test-first approach. If you put in 100% unit test coverage, and 100% integration test cover and 100% end-to-end functionality test coverage, then you end up with 300% coverage of your system. Is the cost of maintaining 300% coverage worth it in your system? “ It’s a good read, check it out.

posted @ Thursday, November 11, 2010 10:04 PM | Feedback (0)
Favoring Value over Quality

Davy Brion has a good post up about how you should favor adding value in software development over that ephemeral ‘Quality’ that can lead to a never-ending drive for the never actually achievable perfection: “So focusing on the quality of your code and design is a good thing, right? Of course it is, as long as it doesn’t prevent you from actually delivering your software to the people who are supposed to use it in a timely fashion. At some point, you are going to have to accept that you can’t spend all that extra time and money to...

posted @ Thursday, November 11, 2010 9:24 PM | Feedback (0)
Software Developers aren’t Doctors, and they shouldn’t play one on TV

Continuing on the theme that David Harvey talked about, where one can and should be in favor of ‘craftsmanship’ while being skeptical of Software Craftsmanship (TM pending), I’ve created a category to that effect, and want to continue the discussion here. Jan Van Ryswyck (hope I spelled that right, he doesn’t have an easy last name like “Nuechterlein”, further mentioned as “JVR”) has a post up on Elegant Code where, inspired by a tweet, he discusses the division of software developers between laborers and professionals.  As I’m going to paraphrase the hell out of it, so you might want...

posted @ Thursday, November 04, 2010 9:28 PM | Feedback (2)