<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
   <channel>
      <title>Making Light :: How to lose a war :: comments</title>
      <link>http://nielsenhayden.com/makinglight/archives/011707.html#comments </link>
      <description>Language, fraud, folly, truth, history, and knitting. Et cetera.</description>
      <language>en</language>
      <lastBuildDate>Fri, 25 Dec 2009 06:36:59 -0500</lastBuildDate>
      <generator>http://www.sixapart.com/movabletype/?v=4.261</generator>
      
      <item>
      <title>How to lose a war</title>
      <description>Commenting on the Washington Post's new &quot;guidelines&quot; for their employees' use of services like Twitter and Facebook, New York Times...</description>
      <content:encoded>Commenting on the Washington Post's new "guidelines" for their employees' use of services like Twitter and Facebook, New York Times...</content:encoded>
      <link>http://nielsenhayden.com/makinglight/archives/011707.html</link>
      </item>

      
      <item>
         <title>How to lose a war -- comment #1 from Chris</title>
         <description>comment from Chris on 29.Sep.09</description>
         <content:encoded><![CDATA[<p>Curious, does Tor censor it's Internet connections?</p>]]>
	 &lt;p&gt;Posted September 29, 2009 12:44 PM by Chris&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#371977</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#371977</guid>
         <pubDate>Tue, 29 Sep 2009 12:44:43 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #2 from Michael Roberts</title>
         <description>comment from Michael Roberts on 29.Sep.09</description>
         <content:encoded><![CDATA[<p><i>the remaining 0.1% is large enough to absorb anyone’s attention full-time for the rest of their life</i></p>

<p>Oh, that is just so damned true.  It's the ultimate monkey trap.</p>

<p>I have to say, though, your experiment with serializing Cory Doctorow is really working on this monkey, at least.  I'd like to put in my vote for more of that, please.</p>]]>
	 &lt;p&gt;Posted September 29, 2009  1:23 PM by Michael Roberts&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#371989</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#371989</guid>
         <pubDate>Tue, 29 Sep 2009 13:23:41 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #3 from John Mark Ockerbloom</title>
         <description>comment from John Mark Ockerbloom on 29.Sep.09</description>
         <content:encoded><![CDATA[<p>"I’ve been to Google’s New York City offices. They don’t tell their employees what they may and may not do with social media tools..."</p>

<p>Based on numerous interactions with folks who work for Google, I'm pretty sure Google is rather specific and strict about what they may and may not say in public about what they're doing at Google.</p>

<p>Which includes what they say using social media tools.  Google's staff are tech-savvy enough that they might not need to be reminded specifically about that medium, but folks in less tech-savvy groups might.</p>

<p>I don't find it objectionable per se that certain organizations, including newspapers, might impose limits on the public statements of their staff.  (For instance, some news reporters are prohibited from endorsing candidates for offices they might cover, to avoid the appearance of a conflict of interest.)  I haven't seen the full set of the Post guidelines, but general guidelines for news reporters to avoid taking political sides in public aren't unheard of.  (It varies by publication, of course; what might be appropriate for a reporter for a partisan weekly might not be for the anchor of a national general-interest news program.)</p>

<p>Trying to control what you can *read* online, as opposed to *say* online, is more dubious, but I didn't see any sign that the Post was doing that.  If your employer is doing this, my sympathies.</p>

<p><br />
</p>]]>
	 &lt;p&gt;Posted September 29, 2009  2:43 PM by John Mark Ockerbloom&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372000</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372000</guid>
         <pubDate>Tue, 29 Sep 2009 14:43:56 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #4 from Kelley Wegeng</title>
         <description>comment from Kelley Wegeng on 29.Sep.09</description>
         <content:encoded><![CDATA[<p>I understand Ockerbloom's point but because I agree with Patrick's premise that the internet is the main competition for traditional media I cannot help but question whether a traditional media outlet has any business employing anyone who is not tech-savvy enough to responsibly understand the repercussions of the actions they take on social networking sites. If an employee doesn't understand their industry why would anyone pay them to be a part of it? </p>]]>
	 &lt;p&gt;Posted September 29, 2009  2:53 PM by Kelley Wegeng&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372003</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372003</guid>
         <pubDate>Tue, 29 Sep 2009 14:53:04 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #5 from Patrick Nielsen Hayden</title>
         <description>comment from Patrick Nielsen Hayden on 29.Sep.09</description>
         <content:encoded><![CDATA[<p>That was pretty much David Carr's final point.</p>]]>
	 &lt;p&gt;Posted September 29, 2009  3:00 PM by Patrick Nielsen Hayden&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372005</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372005</guid>
         <pubDate>Tue, 29 Sep 2009 15:00:54 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #6 from Hank Roberts</title>
         <description>comment from Hank Roberts on 29.Sep.09</description>
         <content:encoded><![CDATA[<p>> running out of interesting things to read <br />
> is completely a thing of the past. </p>

<p>Yeah, but I'm afraid that may just be because my personal standards are so low compared to the very best attention that can be paid by the people on whose shoulders I'd really rather be standing, so I can see what they see.  </p>

<p>I suspect they're not reading the advertisements, for example, or most blogs.</p>

<p>Monkey trap, yes.<br />
</p>]]>
	 &lt;p&gt;Posted September 29, 2009  3:18 PM by Hank Roberts&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372010</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372010</guid>
         <pubDate>Tue, 29 Sep 2009 15:18:48 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #7 from Evan</title>
         <description>comment from Evan on 29.Sep.09</description>
         <content:encoded><![CDATA[<p>a-MEN!</p>

<p>It's all just an extension of literacy.  Why is that so hard for people to understand?</p>]]>
	 &lt;p&gt;Posted September 29, 2009  3:28 PM by Evan&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372014</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372014</guid>
         <pubDate>Tue, 29 Sep 2009 15:28:50 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #8 from Larry</title>
         <description>comment from Larry on 29.Sep.09</description>
         <content:encoded><![CDATA[<p>It's not just media companies.  Any company that restricts access to information an employee may need to do their job is shooting themselves in the foot.</p>

<p>The insane worry of HR problems is a big driving force, that and PR issues.  I've found that the companies that seem to be doing the best are the ones that are trying to work with the new stuff, not destroy it.</p>

<p>Regarding twitter though, I agree with some of what John stated.  I can understand a newspaper wanting their reporters to avoid taking political stances on stories if they aim to be neutral reporting sources.  </p>

<p>If you have a public voice there is, imho, a responsibility to use it wisely.  I think the following quote really nails it though.</p>

<p>"There will be stumbles and missteps on the way to a hybrid future, but if you can’t trust the women and men who put out your newspaper to use their keyboards wisely regardless of platform, what are they doing working for you?"</p>

<p>You should be able to trust your people, and these guidelines?  They are there so they can fire someone with cause if they say something.</p>]]>
	 &lt;p&gt;Posted September 29, 2009  3:33 PM by Larry&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372017</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372017</guid>
         <pubDate>Tue, 29 Sep 2009 15:33:14 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #9 from Evan</title>
         <description>comment from Evan on 29.Sep.09</description>
         <content:encoded><![CDATA[<p><strong>Larry @ 8<strong><br />
"... so they can fire someone ..."</strong></strong></p>

<p>Ah, yes.  Whenever an organization does something that doesn't quite make sense, it's usually about reinforcing the power structure.  In favor of the powerful.</p>

<p>How could I forget that rule of thumb?  Has years of reading paranoid Sci-Fi taught me nothing!?</p>]]>
	 &lt;p&gt;Posted September 29, 2009  3:38 PM by Evan&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372018</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372018</guid>
         <pubDate>Tue, 29 Sep 2009 15:38:36 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #10 from David Harmon</title>
         <description>comment from David Harmon on 29.Sep.09</description>
         <content:encoded><![CDATA[<p>Reading the article, it looks like the <i>Post</i> had a quite reasonable complaint about one of their editors going public with a political position, and "he ain't supposed to do that".  Even the restrictions quoted in the article (I haven't read the guidelines themselves) seem pretty reasonable, amounting to not publicizing the paper's internal business.  (Remember the squabbles over "hot news"?  Still an issue.)  The <i>Times</i> apparently <a href="http://www.observer.com/2009/media/twitter-culture-wars-itimesi" rel="nofollow">did pretty well</a> too, when some reporters got overexcited and tweeted an internal meeting.  (Carr <i>is</i> a little smug about that.)</p>

<p>So, who's "gagging" their workers?</p>]]>
	 &lt;p&gt;Posted September 29, 2009  4:26 PM by David Harmon&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372033</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372033</guid>
         <pubDate>Tue, 29 Sep 2009 16:26:55 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #11 from Rick York</title>
         <description>comment from Rick York on 29.Sep.09</description>
         <content:encoded><![CDATA[<p>This demonstrates a classic conflict which the internet has exacerbated.  Every organization wants to control its image and message.  WaPo is no exception.  Easy access to social networking tools has heightened many organizations' anxiety.  Anyone can basically say whatever they want about any thing or person.</p>

<p>Remember the stories in the late 90's and early 00's about idiots using their company email accounts to attack fellow employees and supervisors?  You don't hear much about that anymore.  Darwin at work.  You either learn to use the new media with discretion or, you lose your job.</p>

<p>Restricting access to parts of the web is foolish.  You are limiting the tools available to your employees.  But, use of that access to say something inappropriate is equally foolish.</p>

<p>Every organization should give its employees unrestricted access to the Web.  But, the organization needs to establish guidelines for using the Web and insure that their employees understand them.</p>

<p>In the end, Darwin always wins.  And, the battle for free speech never ends.</p>]]>
	 &lt;p&gt;Posted September 29, 2009  5:00 PM by Rick York&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372040</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372040</guid>
         <pubDate>Tue, 29 Sep 2009 17:00:44 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #12 from Joel Polowin</title>
         <description>comment from Joel Polowin on 29.Sep.09</description>
         <content:encoded><![CDATA[<p>The day I was laid off, the workplace's firewall/nanny software started blocking access to sites identified as "humour".  The first sign of this, of course, was that people couldn't look at "Dilbert" to start their day as usual.</p>

<p>We were assured that it was a bug or glitch and definitely just a coincidence.</p>

<p>I'm told that the blocking was moderated within a day or two.<br />
</p>]]>
	 &lt;p&gt;Posted September 29, 2009  6:28 PM by Joel Polowin&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372059</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372059</guid>
         <pubDate>Tue, 29 Sep 2009 18:28:06 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #13 from James D. Macdonald</title>
         <description>comment from James D. Macdonald on 29.Sep.09</description>
         <content:encoded><![CDATA[<p>[Deleted by JDM.  Repeated a link that had already been posted.]</p>]]>
	 &lt;p&gt;Posted September 29, 2009  8:58 PM by James D. Macdonald&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372088</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372088</guid>
         <pubDate>Tue, 29 Sep 2009 20:58:29 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #14 from Earl Cooley III</title>
         <description>comment from Earl Cooley III on 29.Sep.09</description>
         <content:encoded><![CDATA[<p>Joel Polowin #12: <em>The day I was laid off, the workplace's firewall/nanny software started blocking access to sites identified as "humour". The first sign of this, of course, was that people couldn't look at "Dilbert" to start their day as usual.</em></p>

<p>Back when I did Win95 support at Unisys, cube decoration was restricted, but Dilbert comic strips were specifically mentioned as allowed in the employee handbook.</p>]]>
	 &lt;p&gt;Posted September 29, 2009 10:02 PM by Earl Cooley III&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372098</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372098</guid>
         <pubDate>Tue, 29 Sep 2009 22:02:32 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #15 from Avram</title>
         <description>comment from Avram on 29.Sep.09</description>
         <content:encoded><![CDATA[<p>I can't find a link to the <i>WaPo</i>'s actual guidelines, but I'm guessing they only apply to employees. The owners are presumably free to say whatever they want, even though I suspect that the biases of the owners affect news coverage at least as much as those of employees. </p>

<p>According to <a href="http://www.editorandpublisher.com/eandp/search/article_display.jsp?vnu_content_id=1004005805" rel="nofollow">this <i>Editor & Publisher</i> article</a>, the <i>WaPo</i> guidelines do include the claim "we don't use new media to get into verbal fisticuffs with rivals or critics, or to advance personal agendas." No, of course not. That's what the old media are for. Anyone else remember the '96 presidential race, when Bob Dole said something nasty about the <i>NY Times</i>, and in response the paper started printing Dole's words verbatim, without the usual editorial smoothing process (taking out verbal missteps and false starts, "uhms" and "ahs", that kind of thing). </p>]]>
	 &lt;p&gt;Posted September 29, 2009 10:02 PM by Avram&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372099</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372099</guid>
         <pubDate>Tue, 29 Sep 2009 22:02:38 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #16 from Marilee</title>
         <description>comment from Marilee on 30.Sep.09</description>
         <content:encoded><![CDATA[<p><b>Avram</b>, #15, Katharine Weymouth, the current <a href="http://www.washpost.com/gen_info/history/publish1.shtml" rel="nofollow">publisher</a>, has made some really awful mistakes where she's had to apologize on close-to-the-front pages.  You'd think her uncle, Donald Graham, would have trained her better before she got the position.</p>]]>
	 &lt;p&gt;Posted September 30, 2009 12:27 AM by Marilee&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372117</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372117</guid>
         <pubDate>Wed, 30 Sep 2009 00:27:17 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #17 from bryan</title>
         <description>comment from bryan on 30.Sep.09</description>
         <content:encoded><![CDATA[<p>but I thought the only way to lose a war was by having insufficient will to win it. </p>]]>
	 &lt;p&gt;Posted September 30, 2009  3:45 AM by bryan&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372129</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372129</guid>
         <pubDate>Wed, 30 Sep 2009 03:45:54 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #18 from Charlie Stross</title>
         <description>comment from Charlie Stross on 30.Sep.09</description>
         <content:encoded><![CDATA[<p>Back in the early 90s, when working for the software corporation that has now been reincarnated as a litigation zombie (so I shall not name it), we could <em>always</em> tell when members of the board were visiting, because our managers would be scurrying around the cubicle farm the day before, taking down all the Dilbert strips.</p>

<p>Cynicism, it seems, has always been an offense against corporate correctness -- and being seen to be too cynical in public is probably a career-limiting move, hence the lack of folks willing to talk about this lunacy on the record.</p>

<p>(Patrick is clearly right in his assessment of the situation, in my opinion: old-media operations that ban their employees from engaging with new media are like buggy-whip manufacturers who ban their employees from driving automobiles.)<br />
</p>]]>
	 &lt;p&gt;Posted September 30, 2009  6:11 AM by Charlie Stross&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372154</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372154</guid>
         <pubDate>Wed, 30 Sep 2009 06:11:09 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #19 from mjfgates</title>
         <description>comment from mjfgates on 30.Sep.09</description>
         <content:encoded><![CDATA[<p>Newspapers banning access to most of the Web for their employees? Why not? It can't make them collapse any faster, and it might hamper the employees' searches for other jobs. Sure, it's stupid, but they're already chest-deep in tar pit.</p>]]>
	 &lt;p&gt;Posted September 30, 2009 12:00 PM by mjfgates&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372209</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372209</guid>
         <pubDate>Wed, 30 Sep 2009 12:00:15 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #20 from Kip W</title>
         <description>comment from Kip W on 30.Sep.09</description>
         <content:encoded><![CDATA[<p>This fits with what I've been saying for a few years: "Television is a vast wonderland. There is not enough time in a day to watch even just the good stuff."</p>

<p>One reason for that is that the good things on TV come in large increments: just a few chunks will fill up your day -- use tape or a DVR, and the remaining chunks are filled.</p>

<p>The internet, insidiously, comes in blocks of every size, from five seconds to forever, and the odds are good that any given block will tell you where to find at least one similar block.</p>]]>
	 &lt;p&gt;Posted September 30, 2009 12:33 PM by Kip W&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372217</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372217</guid>
         <pubDate>Wed, 30 Sep 2009 12:33:52 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #21 from Kip W</title>
         <description>comment from Kip W on 30.Sep.09</description>
         <content:encoded><![CDATA[<p>(Very much like reading a dictionary, looking up a word that's in the definition you just read, and so on, and so on. Used to work with encyclopedias, too. You kids out there can Google "encyclopedia.")</p>]]>
	 &lt;p&gt;Posted September 30, 2009 12:35 PM by Kip W&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372218</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372218</guid>
         <pubDate>Wed, 30 Sep 2009 12:35:52 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #22 from Terry Karney</title>
         <description>comment from Terry Karney on 30.Sep.09</description>
         <content:encoded><![CDATA[<p><i>Anyone else remember the '96 presidential race, when Bob Dole said something nasty about the NY Times, and in response the paper started printing Dole's words verbatim, without the usual editorial smoothing process (taking out verbal missteps and false starts, "uhms" and "ahs", that kind of thing).</i></p>

<p>When I was in college we had an English professor who tried to make a mockery of us. The paper's policy was to print letters as sent; no editing; save to remove libels.  This prevented people from saying we had twisted their words (as the college had several longstanding feuds going on, about newsworthy issues, the lettercol was a heated place of invective filled debate).</p>

<p>So this prof sent us a letter. We handed it to Elaine, who set it, verbatim.  It had a couple of errors.  The Prof send us a nasty letter; addressed, formatted as a "letter to the editor".  We, of course, printed it.  It was sent to the opinion editor, etc.  In form and manner it was no different from any other letter.  </p>

<p>It was very embarrassing to the prof; as it basically said, "I am an incompetent typist, and don't check my work for errors of grammar, <i>you were supposed to do that for me as a courtesy</i>.</p>

<p>We appended an addendum, explaining that the policy was clearly printed in the "How to submit a letter to the editor, and no one got special treatment.</p>

<p>And the prof upped the ante.  Sent us a handwritten mess, so far as we could tell intentionally wretched.  Setting it would have been a nightmare.  So we ran a halftone image.</p>

<p>Not the nicest thing, and one of the few we actually ran past the advisors for serious feedback (we wanted to make sure we were being more than petty).  That was the end of it.</p>]]>
	 &lt;p&gt;Posted September 30, 2009  2:38 PM by Terry Karney&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372260</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372260</guid>
         <pubDate>Wed, 30 Sep 2009 14:38:04 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #23 from Bruce E. Durocher II</title>
         <description>comment from Bruce E. Durocher II on 30.Sep.09</description>
         <content:encoded><![CDATA[<p>Charlie Stross: <em>we could always tell when members of the board were visiting, because our managers would be scurrying around the cubicle farm the day before, taking down all the Dilbert strips.</em></p>

<p>One of the largest venture capitalists in the state did a brief interview some years ago.  When they asked about how he screened companies to decide if he'd invest he said he looked for Dilbert cartoons--if he visited a company and there weren't any, or if there were several hundred stuck up in two or three places, he took a nice long look at the books.  I used to think about this every time I walked through the IT area of a past employer who had a wall that was over <em>12 feet</em> of daily Dilberts.</p>]]>
	 &lt;p&gt;Posted September 30, 2009  7:38 PM by Bruce E. Durocher II&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372349</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372349</guid>
         <pubDate>Wed, 30 Sep 2009 19:38:37 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #24 from Bill Stewart</title>
         <description>comment from Bill Stewart on 30.Sep.09</description>
         <content:encoded><![CDATA[<p>My company has the typical "only the PR department or executives can speak to the press on our behalf" policy.  Internet pundit Bill Stewart can say pretty much anything he wants under his own name, but $Corporation employee Bill Stewart is supposed to refer the press to the PR department.  </p>

<p>And over the last 30 years, we've gone from not having censorship on our uucp connections (but computer games being turned off before 5pm) to an HR-driven panic that they might get sued* if employees look at inappropriate pictures at work to occasionally-overly-aggressive set of internet censorship that sometimes interferes with real work.  Perhaps they're blocking livejournal because of its questionable content or perhaps because it can turn into an all-day time-sink.  On the other hand, blocking computer security sites that have "hacking tools" or "criminal skills" can be counterproductive for my current project developing firewalls.  </p>

<p>(*We're a big company, we get sued for lots of things, but we got our ass handed to us in the 70s for discrimination and they really don't ever want that to happen again, as well as actually caring about diversity these days.  On the other hand, the first internet censorship I saw at one part of the company was that web page requests for www.playboy.com got redirected to www.disney.com; I think that bothered the trademark lawyers far more than the HR people...)</p>]]>
	 &lt;p&gt;Posted September 30, 2009  9:12 PM by Bill Stewart&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372366</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372366</guid>
         <pubDate>Wed, 30 Sep 2009 21:12:39 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #25 from Shalanna Collins</title>
         <description>comment from Shalanna Collins on  1.Oct.09</description>
         <content:encoded><![CDATA[<p>Why would any corporation limit access to the WWW and the 'net in general?  I suspect they're simply terrified that some employee will be "not doing work" while on-the-clock.  It doesn't matter if the limitation makes the job tougher, because their major concern is that no one gets away with goofing off (although they do anyway.)</p>

<p>Everywhere I've worked, management has been convinced that everyone sat around all day trying to goof off or figure out more ways to goof off, and this sent them into a micromanaging panic.  Even though we had to do daily status reports telling what we had spent the day doing, and we had to meet the milestones set in the schedules (meaning we had to do something on the work every day in order to make the schedule), and they made the rounds to look over your shoulder regularly, they were still suspicious that somebody was Getting Away With Something.</p>

<p>I don't feel that a salaried employee who checks his/her horoscope, the weather, the headlines, or something like that has sinned against the company for spending a few minutes looking at that.  Yet I can kind of see how someone surfing the 'net and reading LiveJournal for several hours during the corporate workday would be frowned upon.  The problem is that people don't have the sense to know the difference, or they're not taught right from birth and usually think, "What is the right action?  Whatever you can get away with."  So maybe people at those companies WERE wasting the day looking at flickr sets of people's vacations or borderline porn (!), reading "Overheard In New York," or writing to their friends on Facebook.  The companies didn't want the time to be taken away from what the company was paying them for.</p>

<p>After all, many of my cohorts when I worked as a software engineer did netsurf in addition to using the 'net as a resource for finding upgrades, free code, fixes, and so forth.  There was some time wasted.  I chalked it up to mental health and a feeling that the Man was not breathing down their necks; I also saw the same employees working late and spending extra time whenever they were asked to.  It was a trade-off.  Nobody went overboard surfing.</p>

<p>But they COULD have.  So I can see where management (which is generally concerned that someone is Getting Away With Something Right Under Their Noses, remember) might be paranoid and nanny away too many places.  It's simply as case of not trusting reporters and writers to do their jobs instead of goofing off, I guess.</p>

<p>I understand cutting off the access to LJ, Facebook, Amazon, IMDB, the Sudoku site, and the like, because they are too tempting for the employees with little self-control or sense of responsibility.  Employees will play, unless you play the nanny, would be the idea.</p>

<p>Or am I missing something?<br />
</p>]]>
	 &lt;p&gt;Posted October  1, 2009 12:30 PM by Shalanna Collins&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372506</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372506</guid>
         <pubDate>Thu, 01 Oct 2009 12:30:53 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #26 from David Harmon</title>
         <description>comment from David Harmon on  1.Oct.09</description>
         <content:encoded><![CDATA[<p>Shalanna Collins #25:  The problem is, that can rapidly descend into "the whippings will continue until morale improves!"</p>

<p>Also, that sort of micromanagement represents a gross failure of genuine management -- cheap brute-force constraints, instead of actually paying attention to your people.</p>]]>
	 &lt;p&gt;Posted October  1, 2009  2:49 PM by David Harmon&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372548</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372548</guid>
         <pubDate>Thu, 01 Oct 2009 14:49:05 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #27 from Mycroft W</title>
         <description>comment from Mycroft W on  1.Oct.09</description>
         <content:encoded><![CDATA[<p>At my first job, I was in the lunch room reading the comics page, and the VP Marketing came in and asked what I was laughing at.  I said, "Dilbert is particularly funny today"  He replied, "You techs really seem to enjoy that.  I don't see what's so funny."</p>

<p>And he really couldn't.  And, of course, that's what was so funny.  There's a reason that project was only not Deathmarch because a) it finished (350% late) and b) with people still at the company (about 1/3 of the size it was when I started, but).</p>]]>
	 &lt;p&gt;Posted October  1, 2009  2:52 PM by Mycroft W&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372550</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372550</guid>
         <pubDate>Thu, 01 Oct 2009 14:52:27 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #28 from Joel Polowin</title>
         <description>comment from Joel Polowin on  1.Oct.09</description>
         <content:encoded><![CDATA[<p>Shalanna Collins @ 25: One reason for restricting employees' use of the net is if the organization's bandwidth is limited, or is paid for by usage.  I've heard of cases where some people's work-related net usage was bogged down by too many people using streaming media, or otherwise doing non-work-related high-bandwidth stuff.  (And of cases where poorly-implemented restrictions, intended to limit the non-work usage, messed up the work-related usage.)<br />
</p>]]>
	 &lt;p&gt;Posted October  1, 2009  3:49 PM by Joel Polowin&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372564</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372564</guid>
         <pubDate>Thu, 01 Oct 2009 15:49:42 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #29 from Bruce Cohen (SpeakerToManagers)</title>
         <description>comment from Bruce Cohen (SpeakerToManagers) on  1.Oct.09</description>
         <content:encoded><![CDATA[<p>The last company I worked for was primarily manufacturing; most of the employees were hourly, not exempt professionals, and it was felt that the internet needed to be screened because otherwise they'd waste all those hours the company was paying them for.</p>

<p>It didn't seem to bother anyone that the two engineers who were developing IT software couldn't get to half the sites we needed to (they used an especially brain-damaged netnanny).  Of course, we just used another internet gateway that didn't have a filter on it, but it was annoying because of the lower bandwidth (it was actually a separate physical connection).</p>]]>
	 &lt;p&gt;Posted October  1, 2009  9:54 PM by Bruce Cohen (SpeakerToManagers)&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372622</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372622</guid>
         <pubDate>Thu, 01 Oct 2009 21:54:56 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #30 from P J Evans</title>
         <description>comment from P J Evans on  1.Oct.09</description>
         <content:encoded><![CDATA[<p>The company where I work sends out reminders, every few months, that we're not supposed to be surfing the 'net, or using streaming media, while at work. People ignore the notices. I assume that they can see what I do, so I try to limit the places I go.  (There is nannyware that blocks some sites, but it seems to be mostly looking for racist/sexist stuff. The suits take equality and diversity seriously.)</p>]]>
	 &lt;p&gt;Posted October  1, 2009 10:12 PM by P J Evans&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372623</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372623</guid>
         <pubDate>Thu, 01 Oct 2009 22:12:27 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #31 from Kevin Marks</title>
         <description>comment from Kevin Marks on  2.Oct.09</description>
         <content:encoded><![CDATA[<p>John #3<br />
As someone who recently left Google, I can confirm that employees net connections aren't filtered (a colleague who used to work on net censorship checked here entire list of blocked-somewhere URLs there on her first day and got to all of them), and that employees are encouraged to blog, twitter etc.</p>

<p>That said, because Google is so open internally with information that all employees are subject to SEC quiet periods, and that anything written in public becomes "Google said" people can be wary of speaking or writing online, and the weekly company meetings where L,S+E speak frankly are explicitly called out as "don't discuss".</p>

<p>The other thing to remember is that WaPo employees are professional writers - telling them they can't write online is like telling Google engineers not to work on Open Source projects (which would be completely antithetical to SV culture).<br />
</p>]]>
	 &lt;p&gt;Posted October  2, 2009  7:31 PM by Kevin Marks&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372826</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372826</guid>
         <pubDate>Fri, 02 Oct 2009 19:31:09 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #32 from Charlie Stross</title>
         <description>comment from Charlie Stross on  3.Oct.09</description>
         <content:encoded><![CDATA[<p>Here's what I see as the issue:</p>

<p>It's usually the job of HR to monitor employee performance, and there are two general strategies for assessing employee performance in any organization -- focus on employee inputs, or employee outputs.</p>

<p>Inputs are easy: you just measure bum-in-chair time, clock-punching, and assume outputs are averaged overall.</p>

<p>Outputs are easy to monitor in unskilled or semi-skilled roles, but very hard to assess in professional or technical roles because the assessor needs to be able to understand what they're looking at. How does an HR person look at two programmers, both of whom produced 1000 lines of code in the preceding six months, and determine which of them is performing better? (Law of programming: more lines of code != better software. Indeed, frequently less is more.)</p>

<p>So there's a tendency to just look at the inputs, and to an HR person doing time-and-motion on the staff, seeing someone spend four hours a day on blogs or web surfing is a red flag. (HR can't tell the difference between a programmer staying abreast of the latest technologies by reading widely, and a programmer who's goofing off or looking at employee-wanted ads.)</p>

<p>This is where the impulse to censor internet access at work comes from (aside from the liability sock-puppet, which is waved wildly because it's convenient and much less likely to be challenged than an admission that the censorship regime is being imposed because the censors are clueless about what their employees are really doing).</p>]]>
	 &lt;p&gt;Posted October  3, 2009 10:03 AM by Charlie Stross&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#372921</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#372921</guid>
         <pubDate>Sat, 03 Oct 2009 10:03:29 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #33 from Martin Wisse</title>
         <description>comment from Martin Wisse on  5.Oct.09</description>
         <content:encoded><![CDATA[<p>Why all this is not so black and white as we might wish it was and why <a href="http://www.bynkii.com/archives/2009/08/its_that_time_of_year.html" rel="nofollow">Farhad Manjoo is an idiot</a>:</p>

<p><i><br />
Can you guarantee that the content of such IMs would never contain confidential patient data that could be seen by someone else on the same IM program on that network that has no need, and therefore no authorization to see that data? Can you guarantee that the IM program you want to use would allow for multiple levels of security and access restriction? Do they support SSL and/or Kerberos? Can they tie into LDAP? Do you even know what some of the data leakage issues are for IM in a medical situation, and the time, work, and money required to properly handle them so they don’t get reamed by a HIPAA audit? Does any of that even exist in your world, or is this yet something else you know nothing about, and therefore think there’s no difference between what you do at home, and what is required of the network that doctors and nurses use at a hospital?<br />
</i></p>

<p></p>

<p><br />
</p>]]>
	 &lt;p&gt;Posted October  5, 2009  9:26 AM by Martin Wisse&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#373262</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#373262</guid>
         <pubDate>Mon, 05 Oct 2009 09:26:47 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #34 from Marilee</title>
         <description>comment from Marilee on  5.Oct.09</description>
         <content:encoded><![CDATA[<p>In yesterday's WashPost, the ombudsman comments on this <a href="http://www.washingtonpost.com/wp-dyn/content/article/2009/10/02/AR2009100202888.html" rel="nofollow">topic</a>.  He also talks about it on his <a href="http://voices.washingtonpost.com/ombudsman-blog/2009/10/social_media_guidelines_renew.html" rel="nofollow">blog</a>.</p>]]>
	 &lt;p&gt;Posted October  5, 2009  8:37 PM by Marilee&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#373343</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#373343</guid>
         <pubDate>Mon, 05 Oct 2009 20:37:21 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #35 from [spam deleted]</title>
         <description>comment from [spam deleted] on 25.Dec.09</description>
         <content:encoded><![CDATA[<p>[posted from 188.187.3.70]</p>]]>
	 &lt;p&gt;Posted December 25, 2009  3:52 AM by [spam deleted]&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#390803</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#390803</guid>
         <pubDate>Fri, 25 Dec 2009 03:52:41 -0500</pubDate>
      </item>
      
      <item>
         <title>How to lose a war -- comment #36 from Cadbury Moose spots spam on Regarding Ads</title>
         <description>comment from Cadbury Moose spots spam on Regarding Ads on 25.Dec.09</description>
         <content:encoded><![CDATA[<p>This moose is suspicious of post 35 </p>

<p>It appears to be a twitter bot page.</p>]]>
	 &lt;p&gt;Posted December 25, 2009  6:36 AM by Cadbury Moose spots spam on Regarding Ads&lt;/p&gt;</content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/011707.html#390812</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/011707.html#390812</guid>
         <pubDate>Fri, 25 Dec 2009 06:36:59 -0500</pubDate>
      </item>
      
   </channel>
</rss>