I'd like to apologize

Just before the weekend, I did something stupid and hurtful, and I'd like to make it right.

For the last few weeks, I've been getting e-mails about a book under development over at O'Reilly called Software Craftsmanship—from Apprentice to Journeyman. People kept pointing out that the main title was the same as Pete McBreen's book (for which I wrote the foreword), and that the overall structure of the title was similar to that of The Pragmatic Programmer.

After a while, this started to get under my skin. I wasn't so much concerned about the “journeyman” bit, but the duplication of the title just seemed wrong to me—I really liked Pete's book, and I didn't want to see it getting eclipsed. I complained about this to a senior editor at O'Reilly, and he said he'd bring it up with the book's editor, who worked for him. I heard nothing back.

So, at the end of a tiring week, I wrote a blog post, complaining about the title.

That was wrong of me.

It was wrong for a number of reasons.

• I could, and probably should, have bypassed etiquette and contacted the authors directly, even though they write for a rival publisher.
• It really wasn't any of my business.
• But, most importantly, it took something which was a kind of intellectual annoyance and turned it into something that made the authors of the book feel bad. And for that, I apologize.

This year, I've been the target of some cruel blog posts. Most readers of these posts viewed them as fine sport. But as the recipient of the criticism, I'm here to tell you that it hurts. It doesn't matter whether it is based on truth or whether it isn't. It doesn't matter whether the person writing them knows you or is a total stranger. It hurts. Public attacks like this are virtually impossible to defend against, and that is a cruel violation. It's cruel when it is done to you, and it's cruel when you do it to others.

So, I of all people should have known better. I should have had the common sense to realize that my comments, aimed at a book, were going to be hurtful to the authors. It's kind of obvious, really.

I wasn't thinking straight, and I messed up.

So, Dave and Ade, I'm sorry for any distress I caused.

Good luck with your book.

Comments

[Dick Davies]

Good on you, Dave.

I'm prone to shooting my mouth off now and then too, and I know it's not always easy to retract things afterwards. Equally hard not to rise to someone elses trolling (if you know who I mean) and you seem to have taken care of that too :)

[choonkeat]

I raised an eyebrow when I first read it, but I was glad to find the post quickly taken down.

[Rob Kaufman]

Good call Dave! Lashing out in your blog is an easy to fall into trap, and acknowledging it when you fall in sets you a big step above the rest. As a consumer of Pragmatic products and a member of the Ruby community, I really appreciate seeing someone take the way we treat each other online up a notch.

[jdbartlett]

Kudos, Dave.

I'm with Rob. Let's all of us knock the humanity up a notch--bam!

[josh]

Nicely done. In the age of "I'm sorry you feel that way" non-apologies, it's always refreshing to see someone who can do an apology right. Keith Olbermann has nothing on you. Thanks for keeping things civil.

[Jeff]

Dave...I think most people know you are a good guy. I doubt there will be any hard feelings in the end.

[Herr Ziffer]

I'm sorry about the mean things I've blogged about you, too, Dave. We've all been naughty boys. No hard feelings.

By the way, can I borrow your title for my upcoming book, The Naughty Programmer -- From Impish to Perverse?

--Ziff

[John Gorman]

Dave, that is so human, and so sweet of you!

BTW, your book got me into Ruby back in 2001 so I want to thank you for that and for all of your involvement since.

- john

[Anticube]

Why was your original post a personal attack, for which you should feel contrite? If indeed this other book is an unabashed copy of something else, what is so wrong about saying that? What makes saying that a personal attack on the authors? Surely they are aware of the book that preceded them, the book whose title they and their publisher are borrowing from, not to mention the content they are (at the least) "informed by" in writing their following book? What is to pretend about here? The reason the second book is being written is because of the first one, and everybody knows this.

Aren't we all adults here? Must we have such thin skin that obvious truths like this can't be spoken?

There is a world of difference between uncalled for personal attacks and what you wrote in your original post. That one book is (obviously) imitating another.

[Fred Polgardy]

Actually, Anticube, the Apprenticeship patterns book is not an imitation of the above books. It certainly draws on those books for the metaphor of software development as a craft; but its unique focus is on the personal and professional (i.e., non-technical) aspects of beginning one's career as a software craftsman.

[trunkated]

+1 to "Good move Dave" :)

Now...when are the Prags going to start writing a book called "Pragmatic Version Control with git"?

[David Vydra]

Dave,

Having made similar mistakes myself, I appreciate your example of how to handle it.

[Dave Hoover]

I agree with David Vydra, you are setting a great example with this apology.

Here are my latest thoughts on the title: http://softwarecraftsmanship.oreilly.com/news/2008/3/31/considering-a-title-change

[David Fendley]

I have an all new respect for you. It takes courage to humble yourself like you just have, and your words have spoken volumes of wisdom to me.

Thank you so much for being an example by doing the right thing.

[Michael]

Dave,
Regarding your comment: "This year, I've been the target of some cruel blog posts".

I agree that you have. There has been an awful lot of bashing of your books, and I just wanted to say that I still regard your books as the best Ruby and best Rails books currently available for actually learning Ruby or Rails. I have read a bunch of others, some of which are written by people who bash your books, and in my opinion (for what it's worth) yours are still at the top of the heap.

Also, I think that "The Pragmatic Programmer" is such a good book that I buy a new copy for every person that I hire.

Keep it up!

[dennis wilson]

I appreciate the public apology.

I would like to thank you for your publishing efforts. I own quite a few of your books and the quality has always been great. These books are some of the most relevant to me as a developer and analyst. I hope you continue.

Thanks !!!

[dennis wilson]

I appreciate the public apology.

I would like to thank you for your publishing efforts. I own quite a few of your books and the quality has always been great. These books are some of the most relevant to me as a developer and analyst. I hope you continue.

Thanks !!!

[Rajesh Duggal]

Humility is a rare trait amongst the software community.
Your ability to introspect and assess your actions shows great strength and maturity of character.

Much respect to you Dave.

http://www.agilemodeling.com/values.htm#Humility

Cheers,
Rajesh Duggal

[Amjith PS]

Good move dave. :-)