this is for holding javascript data
Matteo Cantiello edited Scientists_are_re_busy_people__.tex
about 9 years ago
Commit id: b2f67025928fba4b68455a29ef75f12f4aae6a61
deletions | additions
diff --git a/Scientists_are_re_busy_people__.tex b/Scientists_are_re_busy_people__.tex
index e6cf5e4..995945f 100644
--- a/Scientists_are_re_busy_people__.tex
+++ b/Scientists_are_re_busy_people__.tex
...
\item Include your data and code in the paper. Allow transparency and reproducibility.
\item Export to any journal format with just a click
\item Powerful commenting system (for internal or even external review)
\item No endless emails threads
\end{enumerate}
\section{Disclaimer}
As chief scientist at Authorea, I am obviously a biased party. This said I am an active researcher and I've been writing papers for several years. I wrote papers in \latex, with and without bibtex, sending tens of revisions as tar files via email (sic), having the paper version-controlled with cvs and svn. And of course I've been using Authorea. I published papers in collaborations ranging from 1 to 42 co-authors. I know from first-hand experience that the pain can be real and I am truly interested in sharing with colleagues my experience on the pros and cons of the different approaches.