<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Everyday Scientist</title>
	<atom:link href="http://blog.everydayscientist.com/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://blog.everydayscientist.com</link>
	<description>remarking on the unremarkable</description>
	<lastBuildDate>Sat, 06 Feb 2010 21:27:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>New Rule</title>
		<link>http://blog.everydayscientist.com/?p=2070</link>
		<comments>http://blog.everydayscientist.com/?p=2070#comments</comments>
		<pubDate>Sat, 06 Feb 2010 10:10:58 +0000</pubDate>
		<dc:creator>kendall</dc:creator>
				<category><![CDATA[conferences]]></category>
		<category><![CDATA[literature]]></category>

		<guid isPermaLink="false">http://blog.everydayscientist.com/?p=2070</guid>
		<description><![CDATA[Ubiquitous subjects are ubiquitous in chemistry.  If a compound, protein, reaction, etc. really is ubiquitous, then it is likely widespread enough that you don&#8217;t have to inform everyone of its ubiquity.
]]></description>
			<content:encoded><![CDATA[<p>Ubiquitous subjects are ubiquitous in chemistry.  If a compound, protein, reaction, etc. really is ubiquitous, then it is likely widespread enough that you don&#8217;t have to inform everyone of its ubiquity.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.everydayscientist.com/?feed=rss2&amp;p=2070</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>hard-core sugar balls</title>
		<link>http://blog.everydayscientist.com/?p=2064</link>
		<comments>http://blog.everydayscientist.com/?p=2064#comments</comments>
		<pubDate>Fri, 05 Feb 2010 23:53:47 +0000</pubDate>
		<dc:creator>sam</dc:creator>
				<category><![CDATA[literature]]></category>
		<category><![CDATA[nerd]]></category>

		<guid isPermaLink="false">http://blog.everydayscientist.com/?p=2064</guid>
		<description><![CDATA[Andrew alerted me to this awesome title:

Wow.
]]></description>
			<content:encoded><![CDATA[<p>Andrew alerted me to this awesome <a href="http://dx.doi.org/10.1039/b924103e">title</a>:</p>
<p style="text-align: center;"><a href="http://blog.everydayscientist.com/wp-content/uploads/sugar-balls.jpg"><img class="aligncenter size-large wp-image-2065" title="sugar-balls" src="http://blog.everydayscientist.com/wp-content/uploads/sugar-balls-450x400.jpg" alt="" width="450" height="400" /></a></p>
<p>Wow.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.everydayscientist.com/?feed=rss2&amp;p=2064</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>enormously large!</title>
		<link>http://blog.everydayscientist.com/?p=2049</link>
		<comments>http://blog.everydayscientist.com/?p=2049#comments</comments>
		<pubDate>Fri, 22 Jan 2010 01:30:10 +0000</pubDate>
		<dc:creator>sam</dc:creator>
				<category><![CDATA[literature]]></category>
		<category><![CDATA[nerd]]></category>

		<guid isPermaLink="false">http://blog.everydayscientist.com/?p=2049</guid>
		<description><![CDATA[Now here is an exciting title:
&#8220;Enormously large (approaching 14 eV!) electron binding energies of [HnFn+1]– (n=1-5,7,9,12) anions&#8221;
I just love exclamation points in titles.
]]></description>
			<content:encoded><![CDATA[<p><a href="http://dx.doi.org/10.1016/j.cplett.2010.01.022   ">Now here is an exciting title</a>:</p>
<p>&#8220;<strong>Enormously large (approaching 14 eV!) electron binding energies of [H</strong><sub><strong>n</strong></sub><strong>F</strong><sub><strong>n+1</strong></sub><strong>]</strong><sup><strong>–</strong></sup><strong> (n=1-5,7,9,12) anions</strong>&#8221;</p>
<p>I just love exclamation points in titles.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.everydayscientist.com/?feed=rss2&amp;p=2049</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>stanford grad students are NOT eligible for worker&#8217;s comp</title>
		<link>http://blog.everydayscientist.com/?p=2043</link>
		<comments>http://blog.everydayscientist.com/?p=2043#comments</comments>
		<pubDate>Thu, 21 Jan 2010 00:36:26 +0000</pubDate>
		<dc:creator>sam</dc:creator>
				<category><![CDATA[grad life]]></category>

		<guid isPermaLink="false">http://blog.everydayscientist.com/?p=2043</guid>
		<description><![CDATA[According to this official document, Stanford graduate researchers are not covered by worker&#8217;s compensation. If we get injured on the job, we have to pay using our private insurance. Well that sucks. I can&#8217;t see any reason that a postdoc working in lab should be covered but a grad student doing the exact same thing is [...]]]></description>
			<content:encoded><![CDATA[<p>According to <a href="http://blog.everydayscientist.com/wp-content/uploads/Incident-Reporting-Procedures_Workers-Comp.doc">this official document</a>, Stanford graduate researchers are not covered by worker&#8217;s compensation. If we get injured on the job, we have to pay using our private insurance. Well that sucks. I can&#8217;t see any reason that a postdoc working in lab should be covered but a grad student doing the exact same thing is not.</p>
<p>Students at <a href="http://graduateschool.nd.edu/policies-and-forms/financial-information#Workers-Compensation-Insurance">Notre Dame</a>, <a href="http://gsa.rice.edu/guide/workers-comp">Rice</a>, <a href="http://www.grad.illinois.edu/current/compensation_accidents.htm">UIUC</a>, and <a href="http://hr.caltech.edu/Benefits/workerscomp.htm#Program">Caltech</a> are covered. Why aren&#8217;t we?</p>
<p>This means that we graduate students should be more vigilant at demanding safe working environments, refusing to even enter an area that is at all questionable, refusing to work with or around unsafe individuals, and asking postdocs or professors to perform all strenuous or risky tasks (such as heavy lifting or working in the machine shop).</p>
<p><strong>UPDATE:</strong> I&#8217;ve heard of two cases of graduate students getting injured while in lab, and Stanford refuses to pay the workers comp. In one case, the student&#8217;s private insurance paid. In the other, the Stanford-branded health insurance (<a href="http://www.stanford.edu/group/vaden/insurance/cardinalcare.html">Cardinal Care</a>) also refused to pay, because the injury occurred at work; that student got a hospital bill for nearly $2000. Something is <em>wrong</em> here!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.everydayscientist.com/?feed=rss2&amp;p=2043</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Murphy&#8217;s Law of Water Titrametrics</title>
		<link>http://blog.everydayscientist.com/?p=2039</link>
		<comments>http://blog.everydayscientist.com/?p=2039#comments</comments>
		<pubDate>Mon, 18 Jan 2010 01:47:48 +0000</pubDate>
		<dc:creator>kendall</dc:creator>
				<category><![CDATA[grad life]]></category>

		<guid isPermaLink="false">http://blog.everydayscientist.com/?p=2039</guid>
		<description><![CDATA[It will ALWAYS be raining whenever you need to do Karl-Fischer titration in another building.
Corollary:
El Nino sucks.
]]></description>
			<content:encoded><![CDATA[<p>It will ALWAYS be raining whenever you need to do Karl-Fischer titration in another building.</p>
<p>Corollary:</p>
<p>El Nino sucks.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.everydayscientist.com/?feed=rss2&amp;p=2039</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>go get your own alligator!</title>
		<link>http://blog.everydayscientist.com/?p=2037</link>
		<comments>http://blog.everydayscientist.com/?p=2037#comments</comments>
		<pubDate>Fri, 15 Jan 2010 21:16:12 +0000</pubDate>
		<dc:creator>sam</dc:creator>
				<category><![CDATA[literature]]></category>
		<category><![CDATA[science community]]></category>

		<guid isPermaLink="false">http://blog.everydayscientist.com/?p=2037</guid>
		<description><![CDATA[&#8220;They cannot argue with this data,&#8221; she said. &#8220;I have three lines of evidence. If they don&#8217;t believe it, they need to get an alligator and make their own measurements.&#8221;
(via Randy and Eric.)
]]></description>
			<content:encoded><![CDATA[<p>&#8220;They cannot argue with this data,&#8221; she said. &#8220;I have three lines of evidence. If they don&#8217;t believe it, <a href="http://www.msnbc.msn.com/id/34867991/ns/technology_and_science-science/">they need to get an alligator and make their own measurements</a>.&#8221;</p>
<p>(via Randy and Eric.)</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.everydayscientist.com/?feed=rss2&amp;p=2037</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Biophysics Meeting</title>
		<link>http://blog.everydayscientist.com/?p=2029</link>
		<comments>http://blog.everydayscientist.com/?p=2029#comments</comments>
		<pubDate>Thu, 07 Jan 2010 23:26:25 +0000</pubDate>
		<dc:creator>ilya</dc:creator>
				<category><![CDATA[conferences]]></category>

		<guid isPermaLink="false">http://blog.everydayscientist.com/?p=2029</guid>
		<description><![CDATA[Give a big shout-out if you&#8217;re heading for the Biophysics Meeting in a few months.
On a related note, this here video summarizes why biology is so friggin&#8217; cool!

]]></description>
			<content:encoded><![CDATA[<p>Give a big shout-out if you&#8217;re heading for the Biophysics Meeting in a few months.</p>
<p>On a related note, this here <a href="http://www.youtube.com/watch?v=eTvmpn467q0">video</a> summarizes why biology is so friggin&#8217; cool!</p>
<p><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="425" height="344" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/eTvmpn467q0&amp;hl=en_US&amp;fs=1&amp;" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="425" height="344" src="http://www.youtube.com/v/eTvmpn467q0&amp;hl=en_US&amp;fs=1&amp;" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.everydayscientist.com/?feed=rss2&amp;p=2029</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>acronym fail</title>
		<link>http://blog.everydayscientist.com/?p=2023</link>
		<comments>http://blog.everydayscientist.com/?p=2023#comments</comments>
		<pubDate>Wed, 06 Jan 2010 17:10:08 +0000</pubDate>
		<dc:creator>sam</dc:creator>
				<category><![CDATA[literature]]></category>

		<guid isPermaLink="false">http://blog.everydayscientist.com/?p=2023</guid>
		<description><![CDATA[Strange choice for the name of the fluorescent probe.

The &#8220;SS&#8221; stands for the disulfide bond; the &#8220;A&#8221; for acetylnaphthalene. I think. Fortunately, the authors never used the phrase &#8220;ASS probe&#8221; in the paper.
]]></description>
			<content:encoded><![CDATA[<p>Strange choice for the name of the fluorescent probe.</p>
<p style="text-align: center;"><a href="http://dx.doi.org/10.1021/ja9090676"><img class="aligncenter size-large wp-image-2024" title="ass-TOC" src="http://blog.everydayscientist.com/wp-content/uploads/ass-TOC-450x256.jpg" alt="" width="450" height="256" /></a></p>
<p>The &#8220;SS&#8221; stands for the disulfide bond; the &#8220;A&#8221; for acetylnaphthalene. I think. Fortunately, the authors never used the phrase &#8220;<a href="http://blog.everydayscientist.com/?p=626">ASS probe</a>&#8221; in the paper.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.everydayscientist.com/?feed=rss2&amp;p=2023</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>liquid oxygen</title>
		<link>http://blog.everydayscientist.com/?p=2011</link>
		<comments>http://blog.everydayscientist.com/?p=2011#comments</comments>
		<pubDate>Tue, 05 Jan 2010 01:37:40 +0000</pubDate>
		<dc:creator>sam</dc:creator>
				<category><![CDATA[science and the public]]></category>
		<category><![CDATA[stupid technology]]></category>

		<guid isPermaLink="false">http://blog.everydayscientist.com/?p=2011</guid>
		<description><![CDATA[Not a good idea:

I don&#8217;t think putting liquid oxygen on your tongue is so smart. Fortunately, it&#8217;s not really liquid O2, it&#8217;s just salt water:
&#8220;The chemical components in Liquid Oxygen are distilled water, sodium chloride, dissolved oxygen and essential and trace minerals. The species of oxygen found in Liquid Oxygen include O2, and O4. The [...]]]></description>
			<content:encoded><![CDATA[<p>Not a good idea:</p>
<p style="text-align: center;"><img class="aligncenter size-medium wp-image-2012" title="liquid-oxygen" src="http://blog.everydayscientist.com/wp-content/uploads/liquid-oxygen-252x300.png" alt="" width="252" height="300" /><img class="aligncenter size-medium wp-image-2013" title="liquid-oxygen-drops" src="http://blog.everydayscientist.com/wp-content/uploads/liquid-oxygen-drops-252x300.png" alt="" width="252" height="300" /></p>
<p>I don&#8217;t think putting liquid oxygen on your tongue is so smart. Fortunately, it&#8217;s not really liquid O2, <a href="http://www.o2spabar.com/liquid_oxygen_scientific_facts.php">it&#8217;s just salt water</a>:</p>
<blockquote><p>&#8220;The chemical components in Liquid Oxygen are distilled water, sodium chloride, dissolved oxygen and essential and trace minerals. The species of oxygen found in Liquid Oxygen include O2, and O4. The active ingredient in Liquid Oxygen is a relatively stable nascent molecule of oxygen in the form of O4. All other oxygen type supplements bond their active oxygen to salt molecules forming oxychlorine or oxy-halogen compounds driving up the pH to levels that could be dangerous to the skin and delicate membranes in the oral cavity if taken improperly. In addition, additional stomach acid activity is required to break these molecules down to release the oxygen.&#8221;</p></blockquote>
<p>Huh?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.everydayscientist.com/?feed=rss2&amp;p=2011</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>tebow celebrates my PhD defense</title>
		<link>http://blog.everydayscientist.com/?p=2017</link>
		<comments>http://blog.everydayscientist.com/?p=2017#comments</comments>
		<pubDate>Sat, 02 Jan 2010 03:35:17 +0000</pubDate>
		<dc:creator>sam</dc:creator>
				<category><![CDATA[grad life]]></category>

		<guid isPermaLink="false">http://blog.everydayscientist.com/?p=2017</guid>
		<description><![CDATA[In the Sugar Bowl tonight, Florida&#8217;s Tim Tebow kindly reminded the world that I&#8217;ll be defending my PhD Dissertation on February 8, 2010.

That&#8217;s nice of him.
]]></description>
			<content:encoded><![CDATA[<p>In the Sugar Bowl tonight, Florida&#8217;s Tim Tebow kindly reminded the world that I&#8217;ll be defending my PhD Dissertation on February 8, 2010.</p>
<p style="text-align: center;"><a href="http://www.huffingtonpost.com/2010/01/01/ephesians-2-8-10-tim-tebo_n_409193.html"><img class="size-large wp-image-2018 aligncenter" title="tebow" src="http://blog.everydayscientist.com/wp-content/uploads/tebow-450x303.jpg" alt="" width="450" height="303" /></a></p>
<p>That&#8217;s nice of him.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.everydayscientist.com/?feed=rss2&amp;p=2017</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>lobsters chelate</title>
		<link>http://blog.everydayscientist.com/?p=1995</link>
		<comments>http://blog.everydayscientist.com/?p=1995#comments</comments>
		<pubDate>Tue, 29 Dec 2009 06:51:25 +0000</pubDate>
		<dc:creator>sam</dc:creator>
				<category><![CDATA[crazy figure contest]]></category>

		<guid isPermaLink="false">http://blog.everydayscientist.com/?p=1995</guid>
		<description><![CDATA[As a Mainer, I appreciate this table-of-contents artwork:

Cute.
]]></description>
			<content:encoded><![CDATA[<p>As a Mainer, I appreciate this table-of-contents artwork:</p>
<p style="text-align: center;"><a href="http://dx.doi.org/10.1021/jz900272u"><img class="aligncenter size-full wp-image-1996" title="lobster-chelating" src="http://blog.everydayscientist.com/wp-content/uploads/lobster-chelating.jpg" alt="lobster-chelating" width="450" height="410" /></a></p>
<p>Cute.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.everydayscientist.com/?feed=rss2&amp;p=1995</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>to be unpublished</title>
		<link>http://blog.everydayscientist.com/?p=2001</link>
		<comments>http://blog.everydayscientist.com/?p=2001#comments</comments>
		<pubDate>Wed, 23 Dec 2009 19:53:33 +0000</pubDate>
		<dc:creator>sam</dc:creator>
				<category><![CDATA[history]]></category>
		<category><![CDATA[literature]]></category>

		<guid isPermaLink="false">http://blog.everydayscientist.com/?p=2001</guid>
		<description><![CDATA[Footnote 20 is great.

Lipscomb, W. N. J. Chem. Phys. 1954, 22, 985-988. (Thanks Mike.)
]]></description>
			<content:encoded><![CDATA[<p>Footnote 20 is great.</p>
<p style="text-align: center;"><a href="http://dx.doi.org/10.1063/1.1740319"><img class="aligncenter size-large wp-image-2002" title="to-be-unpublished" src="http://blog.everydayscientist.com/wp-content/uploads/to-be-unpublished-450x215.jpg" alt="" width="450" height="215" /></a></p>
<p><a href="http://dx.doi.org/10.1063/1.1740319">Lipscomb, W. N. </a><em><a href="http://dx.doi.org/10.1063/1.1740319">J. Chem. Phys.</a></em><a href="http://dx.doi.org/10.1063/1.1740319"> </a><strong><a href="http://dx.doi.org/10.1063/1.1740319">1954,</a></strong><a href="http://dx.doi.org/10.1063/1.1740319"> </a><em><a href="http://dx.doi.org/10.1063/1.1740319">22,</a></em><a href="http://dx.doi.org/10.1063/1.1740319"> 985-988</a>. (Thanks Mike.)</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.everydayscientist.com/?feed=rss2&amp;p=2001</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>check out this cool link</title>
		<link>http://blog.everydayscientist.com/?p=2005</link>
		<comments>http://blog.everydayscientist.com/?p=2005#comments</comments>
		<pubDate>Sun, 20 Dec 2009 07:29:33 +0000</pubDate>
		<dc:creator>sam</dc:creator>
				<category><![CDATA[nerd]]></category>
		<category><![CDATA[science community]]></category>
		<category><![CDATA[wild web]]></category>

		<guid isPermaLink="false">http://blog.everydayscientist.com/?p=2005</guid>
		<description><![CDATA[Check it out here. I promise you won&#8217;t be rickroll&#8217;d.
]]></description>
			<content:encoded><![CDATA[<p>Check it out <a href="http://www.youtube.com/watch?v=zXDYZ8RgGOU#t=40s">here</a>. I promise you won&#8217;t be rickroll&#8217;d.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.everydayscientist.com/?feed=rss2&amp;p=2005</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>how to respond to referees</title>
		<link>http://blog.everydayscientist.com/?p=1969</link>
		<comments>http://blog.everydayscientist.com/?p=1969#comments</comments>
		<pubDate>Tue, 15 Dec 2009 18:42:18 +0000</pubDate>
		<dc:creator>sam</dc:creator>
				<category><![CDATA[how-to]]></category>
		<category><![CDATA[literature]]></category>
		<category><![CDATA[science community]]></category>

		<guid isPermaLink="false">http://blog.everydayscientist.com/?p=1969</guid>
		<description><![CDATA[Now that I&#8217;ve listed some pointers on how to write a referee report, I want to discuss how to respond to reviews of your own manuscript. Again, I&#8217;m still a novice at this, so I&#8217;d love input from the audience!

Try not to be offended. It&#8217;s hard not to, but try not to hate the reviewer [...]]]></description>
			<content:encoded><![CDATA[<p>Now that I&#8217;ve <a href="http://blog.everydayscientist.com/?p=1968">listed some pointers on how to write a referee report</a>, I want to discuss how to <em>respond</em> to reviews of your own manuscript. Again, I&#8217;m still a novice at this, so I&#8217;d love input from the audience!</p>
<ol style="padding-left: 30px; ">
<li><strong>Try not to be offended.</strong> It&#8217;s hard not to, but try not to hate the reviewer when they criticize your manuscript. Usually, I get one referee who says the paper is great and another who says it&#8217;s crap. It&#8217;s hard not to want to hurt that latter type. Bad. But they might be partially right, so correct the issues they find that have merit, and defend your original manuscript against the foolish criticisms.</li>
<li><strong>Organize your response.</strong> I like to make tables with one row being the referee&#8217;s comment and the other being my response, with each comment on a separate row. Any way you do it, respond to each referee point-by-point. In your cover letter to the editor, summarize the major requests by the referees and the main changes in the revised manuscript.</li>
<li><strong>Stand your ground when you&#8217;re right.</strong> Don&#8217;t make changes that make your manuscript worse. If the referee is wrong about something, say so (gently). Your goal is the editor seeing that you are right. If you&#8217;re too rude in your response to an incorrect referee, the editor may think you protest too much and become suspicious.</li>
<li><strong>&#8230;but don&#8217;t pull an </strong><a href="http://physicsandphysicists.blogspot.com/2009/10/einstein-versus-physical-review.html"><strong>Einstein</strong></a><strong>.</strong> Sometimes referees find a problem with your science or reasoning that, no matter how much it pains you, is worth seriously considering. Referees can make your papers much better, so it is important to listen to them.</li>
</ol>
<p>Number 1 is the one I have the most problems with. I don&#8217;t understand why some referees have to be so unreasonable and wrong when writing their reports. I usually draft very snarky responses, only to replace them with polite disagreement before sending my revisions to the editor. And complain to friends a lot. Not sure if that helps me or keeps me angry.</p>
<p>Others?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.everydayscientist.com/?feed=rss2&amp;p=1969</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>how to referee a paper</title>
		<link>http://blog.everydayscientist.com/?p=1968</link>
		<comments>http://blog.everydayscientist.com/?p=1968#comments</comments>
		<pubDate>Fri, 11 Dec 2009 16:55:55 +0000</pubDate>
		<dc:creator>sam</dc:creator>
				<category><![CDATA[how-to]]></category>
		<category><![CDATA[literature]]></category>
		<category><![CDATA[science community]]></category>

		<guid isPermaLink="false">http://blog.everydayscientist.com/?p=1968</guid>
		<description><![CDATA[Here are some pointers about how to referee a scientific journal article. I&#8217;ve picked these up both from having refereed papers myself (with my PIs) and more importantly from reading referee reports (good and bad) of my own manuscripts.

Be timely. Editors often proceed with the publication process after getting back only two (or sometimes one) [...]]]></description>
			<content:encoded><![CDATA[<p>Here are some pointers about how to referee a scientific journal article. I&#8217;ve picked these up both from having refereed papers myself (with my PIs) and more importantly from reading referee reports (good and bad) of my own manuscripts.</p>
<ol style="padding-left: 30px;">
<li><strong>Be timely.</strong> Editors often proceed with the publication process after getting back only two (or sometimes one) review. If yours is the third to come back, it may be too late. I&#8217;ve learned the hard way that, if you take too long to submit your review, your hard work might be all for naught. Of course, it is totally inappropriate to sit on a review purposefully to give yourself time to scoop a competitor.</li>
<li><strong>Be positive.</strong> Authors will be more willing to make the changes you suggest if you &#8220;<a href="http://bitesizebio.com/2009/07/16/delivering-effective-criticism/">sandwich</a>&#8221; the constructive criticism between positive comments about the manuscript. It&#8217;s easy as a reviewer to only see the bad and forget that the science and writing took a lot of effort from the authors.</li>
<li><strong>Organize your criticisms.</strong> At minimum, split the changes you&#8217;re asking for into <em>essential</em> and <em>minor</em>. For instance, don&#8217;t bury a serious problem you found among a bunch of nit-picky points. First list the essential changes that need to be made in order to make the manuscript publishable, then you may list typos and minor points if you wish. This way, the authors (and editors) will immediately understand your assessment of the paper, and not get offended by what feels like an endless list of complaints. Remember: you&#8217;re a referee of the science, not an editor. <strong>UPDATE:</strong> Also, as MRW says in the comments, write your report so it can be responded to point-by-point.</li>
<li><strong>Do unto others&#8230;</strong> Remember what you appreciate in a review of your own manuscripts (and what drove you mad), and go from there. The authors are not your enemies&#8212;even though some of them torture you with their unclear writing and lackluster science&#8212;treat them like you would want to be treated.</li>
<li><strong>But be a good filter.</strong> Don&#8217;t let fatally bad science into the literature.</li>
</ol>
<p>The best referees are the ones that help the authors make the paper <em>better</em>. Try to be that kind of referee. The worst are the ones that don&#8217;t read the manuscript closely enough, then unfairly criticize it. The just plain unhelpful are the ones who just say &#8220;publish as is.&#8221;</p>
<p>I&#8217;m sure I have a lot more to learn, but these are some things I&#8217;ve picked up so far. Others?</p>
<p>(Later, I&#8217;ll talk about <a href="http://blog.everydayscientist.com/?p=1969">how to respond to referee reports</a> of your own manuscripts.)</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.everydayscientist.com/?feed=rss2&amp;p=1968</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>
