|
It may be a journalist's job to probe, but it is a fellow human's job to have empathy. raganwald is perfectly correct in distinguishing between _why as a public figure, and the man behind _why as a private one. The man behind _why clearly wished to remain private; why are his wishes not being respected? I think that you are being dismissive when you say, "a few phone calls". From the article, the author tried: asking RubyConf attendees, asking people he had been known to have a working relationship with, wrote him a letter, called his home phone, contacted a former employer, searched patent records to discover his current employer, and contacted his current employer, not to mention in the process naming his wife's Twitter account, publishing his real name, and publishing the name of his current employer. That's pretty poor form, and I don't think that "journalism" is an appropriate excuse. Like raganwald, I really liked every other aspect of the article. It's well written and I enjoyed taking the time to sit down and read it with a cup of hot chocolate. But -- and this is a big "but", one that eclipses everything in the article that I enjoyed -- I was tremendously disappointed at seeing the private man behind _why outed as he was in the article. |
I'm completely receptive to the criticism of my treatment of the public persona / private person question -- as I wrote before, I expected it and appreciate everyone's insightful comments here.
But I'd just like to push back on the idea that my reporting somehow constituted harassment, rather than straightforward reporting on a public figure – and one who had unfortunately already been outed and whose offline identity was widely known.
We're talking about a phone message, an email forwarded from his office's receptionist, and a note, spaced over the course of a few months. I don’t think that constitutes harassment. My central objective was just making sure he had the opportunity to respond, if he wanted to, and would not be surprised when the piece came out.
I did extensive interviewing among Rubyists and other programmers for the piece, and would often ask them about _why's work, his guide's influence, his work's influence on them, etc. A bunch delightedly brought up old war stories about him, some of which made it into the piece. The back channeling about his offline identity came, unsolicited actually, from those conversations.
At any rate, I do appreciate all of the comments and criticisms of how I treat it in the piece. And am very appreciative of everyone’s compliments of the article as well.