TITLE: "Doing research is therefore writing software."
AUTHOR: Eugene Wallingford
DATE: June 28, 2012  4:13 PM
DESC: 
-----
BODY:
The lede from
<A HREF="http://faculty.chicagobooth.edu/matthew.gentzkow/research/ra_manual_coding.pdf">
   RA Manual: Notes on Writing Code</A>,
by Gentzkow and Shapiro:

<BLOCKQUOTE><EM>
Every step of every research project we do is written in code,
from raw data to final paper.  Doing research is therefore
writing software.
</EM></BLOCKQUOTE>

The authors are economists at the University of Chicago.  I
have only skimmed the beginning of the paper, but I like
what little I've seen.  <B>They take seriously the writing
of computer programs</B>.
<UL>
<LI> "This document lays out some broad principles we should
     all follow."  </LI>
<LI> "We encourage you to invest in reading more broadly
     about software craftsmanship, looking critically at your
     own code and that of your colleagues, and suggesting
     improvements or additions to the principles below."  </LI>
<LI> "Apply these principles to every piece of code you check
     in without exception."  </LI>
<LI> "You should also take the time to improve code you are
     modifying or extending even if you did not write the code
     yourself."  </LI>
</UL>

<EM>...every piece of code you check in...</EM>  Source code
management and version control?  They are a couple of steps up
on many CS professors and students.

Thanks to
<A HREF="http://marginalrevolution.com/marginalrevolution/2012/06/how-should-economists-write-code.html">
   Tyler Cowen</A>
for the link.
-----