<p><div><div><div><div data-width="100" data-show-faces="false" data-send="true" data-layout="button_count" data-height="21" data-href="https://www.r-bloggers.com/producing-software-for-money-andor-recognition/"></div></div><div><a data-url="https://www.r-bloggers.com/producing-software-for-money-andor-recognition/" data-counturl="https://www.r-bloggers.com/producing-software-for-money-andor-recognition/" data-count="horizontal" data-text="Producing software for money and/or recognition" class="twitter-share-button" data-via="rbloggers" href="https://twitter.com/share"></a></div><div></div></div><div></div></div>
<div>
(This article was first published on <strong><a href="http://shape-of-code.coding-guidelines.com/2016/10/24/producing-software-for-money-andor-recognition/"> The Shape of Code » R</a></strong>, and kindly contributed to <a rel="nofollow" href="https://www.r-bloggers.com/">R-bloggers)</a> </div>
<p>In the commercial environment money makes the world go around, while in academia recognition (e.g., number of times your work is cited, being fawned over at conferences, impressive job titles) is the coin of the realm (there are a few odd balls who do it out of love for the subject or a desire to understand how things work, but modern academia is a large bureaucracy whose primary carrot is recognition).</p>
<p>There is an incentive problem for those writing software in academia; software does not attract much, if any, recognition.</p>
<p>Does the lack of recognition for writing software matter? Surely what counts are the research results, not the tools used to get there (be they writing software or doing mathematics).</p>
<p>A <a target="_blank" rel="nofollow" href="https://arxiv.org/abs/1610.03159">recent paper bemoans</a> the lack of recognition for the development of <a target="_blank" rel="nofollow" href="http://astropy.org/">Python packages for Astronomy</a> researchers. Well, its too late now, they have written the software and everybody gets to make perfect copies for free.</p>
<p>What the authors of Astropy want, is for researchers who use this software to include a citation to it in any published papers. Do all 162 authors deserve equal credit? If a couple of people add a new package, should they get a separate citation? What if a new group of people take over maintenance, when should the citation switch over from the old authors/maintainers to the new ones? These are a couple of the <a target="_blank" rel="nofollow" href="https://www.force11.org/">thorny questions that need to be answered</a>.</p>
<p>R is perhaps the most widely used academic developed software ecosystem. A small dedicated group of people has invested a lot of their time over many years to make something special. A lot more people have invested effort to create a wide variety of add-on packages.</p>
<p>The base R library includes the <a target="_blank" rel="nofollow" href="http://stat.ethz.ch/R-manual/R-devel/RHOME/library/utils/html/citation.html"><code>citation</code> function</a>, which returns the <a target="_blank" rel="nofollow" href="https://en.wikipedia.org/wiki/BibTeX">BibTeX</a> information for a given package; ready to be added to a research papers work flow.</p>
<p>Both commercial and academic producers need to periodically create new versions to keep ahead of the competition, attract more customers and obtain income. While they both produce software to obtain ‘income’, commercial and academic software systems have different incentives when it comes to support for end users of the software.</p>
<p>Keeping existing customers happy is the way to get them to pay for upgrades and this means maintaining compatibility with what went before. Managers in commercial companies make sure that developers don’t break backwards compatibility (<a target="_blank" rel="nofollow" href="https://news.ycombinator.com/item?id=12472505">developers hate</a> having to code around what went before and would love to throw it all away).</p>
<p>In the academic world it does not matter whether end users upgrade, as long as they cite the package, the version used is irrelevant; so there is a lot less pressure to keep backwards compatibility. Academics are supposed to create new stuff, they are researchers after all, so the incentives are pushing them to create brand new packages/systems to be seen as doing new stuff (and obtain a whole new round of citations). A good example is <a target="_blank" rel="nofollow" href="http://hadley.nz/">Hadley Wickham</a>, who has created some great R packages, who seems to be continually moving on, e.g., reshape -> reshape2 -> tidyr (which is what any good academic is supposed to do).</p>
<p>The run-time performance of a system is something end users always complain about, but often get used to. The reason is invariably that there is little or no incentive to address this issue (for both commercial and academic systems). <a target="_blank" rel="nofollow" href="http://blog.zorinaq.com/i-contribute-to-the-windows-kernel-we-are-slower-than-other-oper/">Microsoft Windows is slower</a> than it need be and the R interpreter could go a lot faster (the design of the interpreter looks like something out of the 1980s; I’m seeing a lot of packages in R only, so the idea that R programs spend all their time executing in <a target="_blank" rel="nofollow" href="https://www.openhub.net/p/r_project/analyses/latest/languages_summary">C/Fortran libraries</a> may be out of date. Where is the incentive to <a target="_blank" rel="nofollow" href="https://www.amazon.co.uk/Virtual-Machines-Versatile-Platforms-Architecture/dp/1558609105">use post-2000 designs?</a>)</p>
<p>How many new versions of a software package can be produced before enough people stop being willing to pay for an update? How many different packages solving roughly the same problem can academics produce?</p>
<p>I don’t think producing new packages for income has a long term future.</p>
<p><div><div><div><div data-width="55" data-show-faces="false" data-send="true" data-layout="box_count" data-height="62" data-href="https://www.r-bloggers.com/producing-software-for-money-andor-recognition/"></div></div><div><a data-url="https://www.r-bloggers.com/producing-software-for-money-andor-recognition/" data-counturl="https://www.r-bloggers.com/producing-software-for-money-andor-recognition/" data-count="vertical" data-text="Producing software for money and/or recognition" class="twitter-share-button" data-via="rbloggers" href="https://twitter.com/share"></a></div><div></div></div><div></div></div>
<div>
<div>To <strong>leave a comment</strong> for the author, please follow the link and comment on their blog: <strong><a href="http://shape-of-code.coding-guidelines.com/2016/10/24/producing-software-for-money-andor-recognition/"> The Shape of Code » R</a></strong>.</div>
<hr>
<a rel="nofollow" href="https://www.r-bloggers.com/">R-bloggers.com</a> offers <strong><a rel="nofollow" href="https://feedburner.google.com/fb/a/mailverify?uri=RBloggers">daily e-mail updates</a></strong> about <a title="The R Project for Statistical Computing" rel="nofollow" href="https://www.r-project.org/">R</a> news and <a title="R tutorials" rel="nofollow" href="https://www.r-bloggers.com/?s=tutorial">tutorials</a> on topics such as: <a title="Data science" rel="nofollow" href="https://www.r-bloggers.com/?s=data%20science">Data science</a>, <a title="Big Data" rel="nofollow" href="https://www.r-bloggers.com/?s=Big%20Data">Big Data, <a title="R jobs" rel="nofollow" href="https://www.r-users.com/">R jobs</a>, visualization (<a title="ggplot and ggplot2 tutorials" rel="nofollow" href="https://www.r-bloggers.com/?s=ggplot2">ggplot2</a>, <a title="Boxplots using lattice and ggplot2 tutorials" rel="nofollow" href="https://www.r-bloggers.com/?s=boxplot">Boxplots</a>, <a title="Maps and gis" rel="nofollow" href="https://www.r-bloggers.com/?s=map">maps</a>, <a title="Animation in R" rel="nofollow" href="https://www.r-bloggers.com/?s=animation">animation</a>), programming (<a title="RStudio IDE for R" rel="nofollow" href="https://www.r-bloggers.com/?s=RStudio">RStudio</a>, <a title="Sweave and literate programming" rel="nofollow" href="https://www.r-bloggers.com/?s=sweave">Sweave</a>, <a title="LaTeX in R" rel="nofollow" href="https://www.r-bloggers.com/?s=LaTeX">LaTeX</a>, <a title="SQL and databases" rel="nofollow" href="https://www.r-bloggers.com/?s=SQL">SQL</a>, <a title="Eclipse IDE for R" rel="nofollow" href="https://www.r-bloggers.com/?s=eclipse">Eclipse</a>, <a title="git and github, Version Control System" rel="nofollow" href="https://www.r-bloggers.com/?s=git">git</a>, <a title="Large data in R using Hadoop" rel="nofollow" href="https://www.r-bloggers.com/?s=hadoop">hadoop</a>, <a title="Web Scraping of google, facebook, yahoo, twitter and more using R" rel="nofollow" href="https://www.r-bloggers.com/?s=Web+Scraping">Web Scraping</a>) statistics (<a title="Regressions and ANOVA analysis tutorials" rel="nofollow" href="https://www.r-bloggers.com/?s=regression">regression</a>, <a title="principal component analysis tutorial" rel="nofollow" href="https://www.r-bloggers.com/?s=PCA">PCA</a>, <a title="Time series" rel="nofollow" href="https://www.r-bloggers.com/?s=time+series">time series</a>, <a title="finance trading" rel="nofollow" href="https://www.r-bloggers.com/?s=trading">trading</a>) and more...
<img height="1" alt="" width="1" src="http://feeds.feedburner.com/~r/RBloggers/~4/MIXII9SXgig"></a></div>