Normally, I’d relish a mention on InfoQ
This article on InfoQ bothers me. It seems to draw only from Dave Nicolette’s blog post [now lost due to the defacement of his old blog] and the subsequent comments. Dave’s post is similar, in my mind, to a trip report that someone might give to an organization after a class or conference. He goes into some detail about what happened at the first ever Certified Scrum Developer course, and muses about what he learned. The bulk of the comments are an interchange between Dave and Tobias Mayer where, it appears to me, Tobias doesn’t think that the course comes up to the standard of the CSM course. This is, of course, based on Dave’s description, as Tobias wasn’t present at the course.
The InfoQ article mentions me by name, but doesn’t mention other participants other than Dave. It also misquotes Dave [now edited without any indication of doing so], and implies that the learnings that Dave got out of our retrospective conversation after the course was a list agreed upon by both of us. There was apparently no fact checking done on this article. Certainly no one spoke with Ron Jeffries or with me about it. I find the article misleading enough that I need to respond.
I had planned to write about the course, but this isn’t the article I’d planned.
On Twitter, [a person who now wishes to be anonymous] took exception to Ron Jeffries’ comments on InfoQ and on Twitter about the article failing basic tenets of journalism. [He] is an editor at InfoQ, but thinks that he (and Vikas) are not journalists. Ryan Slobojan, Chief Editor at InfoQ, expressed a similar opinion in an email to me.
I have no formal training as an editor, I’m not a journalist, and before I became Chief Editor in August 2009 I was doing it on the side in addition to my full-time job – this is a common pattern for all of our editors, and it’s how we end up with a diverse team of experts from (literally) all over the world.
I have important information for both [Anonymous] and Ryan. They are journalists, whether they have trained to be, or think of themselves as journalists, or not. They are participating in the business of “the collection and editing of news for presentation through the media.” The fact that they do not realize that’s what they do, that they have not trained themselves in the basics of journalism, and that they sometimes do it badly, doesn’t change the fact that they are journalists.
In a way, that brings us full-circle on the developer training/certification/craftsmanship issue. It’s not only developers that can benefit from a certification class to give them some basic knowledge. When Ron mentioned “Journalism 101” he was talking about that very thing. Neither Ron (I checked my facts) nor I have a degree or certificate in journalism. Clearly, though, we both think that there are some journalistic standards that should be observed.
The difference between our viewpoint and that of [Anonymous] and Ryan reminded me of Jerry Weinberg’s classification of software development organization cultures (taken from page 9 of Quality Software Management: First Order Measurement)
0. Oblivious: “We don’t even know that we’re performing a process.”
1. Variable: “We do whatever we feel like at the moment.”
2. Routine: “We follow our routines (except when we panic).”
3. Steering: “We choose among our routines by the results they produce.”
4. Anticipating: “We establish routines based on our past experience with them.”
5. Congruent: “Everyone is involved in improving everything all the time.”
It occurs to me that these same levels can be applied to individual software developers, to journalists, and to publishers. [Anonymous] and Ryan are journalists at level 0; they don’t know they’re performing journalism. I’m perhaps at level 1 or 2 in journalism. Perhaps that’s enough for the depth of my involvement with journalism.
Software developers sometime do not realize that’s what they are, also. Consider the case of the businessman who tweaks his spreadsheet. He’s writing software, but doesn’t think of it that way.
In Ron and Chet’s CSD class premier, I would expect that everyone who participated generally operates at level 4 or 5. Even such knowledgeable and experienced practitioners, however, can panic under time pressure. It takes time to calmly evaluate a situation and make a decision. It takes more time to do so as a team. If you fail to take that time, your decisions will suffer from the lack of evaluating enough of the situation. I think that’s one of the many things that was going on in that class.
As I said, this is not the article I’d intended to post about the class. That article will have to be written another day. I think this one has some value, too–value far beyond the disclaimer that Vikas Hazrati’s article is not a valid representation of the CSD class.
I’ll still try to find the time to write that article. In the mean time, if you’re writing software, I think you’ll find value in the CSD class. If you’re reporting the news, I think you’ll find value in learning a little about journalism.