this is for holding javascript data
John Blischak added introduction.tex and commented: "Describe problem of having multiple copies of the same code."
about 9 years ago
Commit id: 1fde935d0f89fdc598fb0b80f903ca896700de7d
deletions | additions
diff --git a/introduction.tex b/introduction.tex
new file mode 100644
index 0000000..ff5a18f
--- /dev/null
+++ b/introduction.tex
...
\subsection{Introduction to version control}
A few key problems arise when writing large amounts of code. First, you often need to experiment with new ideas, such as adding new features or increasing the speed of a bottleneck, but you don't want to risk breaking the currently working code. The simplest solution is to copy the script before making new edits. However, this can quickly become a problem because it clutters your filesystem with uniformative filenames, e.g. \verb|analysis.sh|, \verb|analysis_02.sh|, \verb|analysis_final_03.sh|, etc. It is difficult to remember the differences between the version of the code, and more importantly which version you used to produce specific results, especially if you return to the code months later.
