this is for holding javascript data
Matteo Cantiello edited We_are_scientist_We_are__.tex
about 9 years ago
Commit id: 8839ddbbcd8e96c2d8979584cfc604aa925fb250
deletions | additions
diff --git a/We_are_scientist_We_are__.tex b/We_are_scientist_We_are__.tex
index 308fb83..b66e38f 100644
--- a/We_are_scientist_We_are__.tex
+++ b/We_are_scientist_We_are__.tex
...
The idea for Authorea came because we were writing scientific papers and we wanted to improve the way it is done. While Authorea has big plans for the paper of the future, in this post I want to focus on the here and now. When I talk about the platform to my colleagues, by far the most common question I get is "Why should I use Authorea to write my paper?" Here's why.
Let me start by saying that, 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've done it in many different ways: \latex with and without bibtex, sending n-tarballs via email (sic),
having the paper
version controlled version-controlled with cvs or svn, and
more recently with of course I've been using Authorea. I have written papers with 2 or 42 collaborators. I know from first hand experience that the pain can be real and I am truly interested in
describing to sharing with colleagues
what are my experience on the pros and cons of the different approaches.