This repository has been archived by the owner on Jan 3, 2018. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 381
/
Copy pathintroduction.tex
123 lines (108 loc) · 4.89 KB
/
introduction.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
\chapter{Introduction}\label{introduction}
Here's the dream:
\begin{quote}
Computers have revolutionized research, and that revolution is only
beginning. Every day, scientists and engineers all over the world use
them to study things that are too big, too small, too fast, too slow,
too expensive, too dangerous, or just too hard to study any other way.
\end{quote}
\noindent
Now here's the reality:
\begin{quote}
Every day, scientists and engineers all over the world waste time
wrestling with computers. Tasks that should take a few moments take
hours or days, and many things never work at all. And even when things
\emph{do} work, most scientists have no idea how reliable their results
are.
\end{quote}
Most of the pain that researchers feel stems from not knowing how to
develop software systematically, how to tell if their programs are
working correctly, how to share their work with others (except by
mailing files to one another), or how to keep track of what they've
done. This sorry state of affairs persists for four reasons:
\begin{swcitemize}
\item
\emph{No room, no time.} Everybody's curriculum is full---there's
simply not space to add more about computing without dropping
something else.
\item
\emph{No standards.} Reviewers and granting agencies don't check
whether software is correct, ask how long it took to write, or count
it toward tenure, so there's no incentive for scientists to do better.
\item
\emph{The blind leading the blind.} Senior researchers can't teach the
next generation how to do things that they don't know how to do
themselves.
\item
\emph{The cult of big iron.} Attention and funding mostly goes to
things that politicians and university presidents can brag about on
opening day, rather than to the basic skills that almost everyone
uses.
\end{swcitemize}
Our goal is to show scientists and engineers how to do more in less
time and with less pain. Our lessons have been used by more than five
thousand people in over a hundred and fifty two-day workshops since
the spring of 2010. Here's how they can help:
\begin{swcitemize}
\item
If you've ever spent hours typing the same commands over and over
again, we'll show you how to automate those tasks using simple
scripts.
\item
If you've ever overwritten the wrong file, we'll show you how to use
version control.
\item
If you've ever spent an afternoon trying to figure out what the
program you wrote last week actually does, we'll show you how to break
your code into modules that you can read, debug, and improve piece by
piece.
\item
If you've ever spent days copying and pasting data in text files and
spreadsheets, we'll show you how a database can do the work for you.
\end{swcitemize}
\subsection{About Us}
Software Carpentry is an open source project. Our instructors are
volunteers, and all of our lessons are freely available under the
\urlfoot{http://creativecommons.org/licenses/by/3.0/}{Creative Commons -
Attribution License}, so you can re-use and re-mix them however you want
so long as you cite us as the original source.
Like all volunteer projects, Software Carpentry needs your help to grow.
If you find a bug, please file a report in
\urlfoot{https://github.com/swcarpentry/bc/}{our GitHub repo}. If you would
like to host a workshop, please
get in touch; if you'd like
to teach, we run an
\urlfoot{http://teaching.software-carpentry.org}{instructor training
course}; and if you'd like to write lessons or exercises, please
let us know.
And to find out more, please visit the
\urlfoot{Software Carpentry web site}{http://software-carpentry.org}
or read
\urlfoot{http://www.plosbiology.org/article/info\%3Adoi\%2F10.1371\%2Fjournal.pbio.1001745}{these}
\urlfoot{http://arxiv.org/abs/1307.5448}{papers}.
\newpage
\subsection{Acknowledgments}
Software Carpentry has been made possible by the generous support of:
\begin{tabular}{ll}
Continuum Analytics & http://continuum.io \\
Enthought & http://enthought.com \\
Indiana University & http://www.indiana.edu \\
Lawrence Berkeley National Laboratory & http://www.lbl.gov \\
Los Alamos National Laboratory & http://www.lanl.gov \\
MathWorks & http://www.mathworks.com \\
Michigan State University & http://www.msu.edu \\
Microsoft & http://www.microsoft.com \\
MITACS & http://www.mitacs.ca \\
The Mozilla Foundation & http://mozillafoundation.org \\
The Python Software Foundation & http://www.python.org/psf \\
Queen Mary University of London & http://www.qmul.ac.uk \\
Scimatic Software & http://www.scimatic.com \\
SciNet & http://www.scinet.utoronto.ca \\
SHARCNET & http://www.sharcnet.ca \\
The Alfred P. Sloan Foundation & http://www.sloan.org \\
The Space Telescope Science Institute & http://www.stsci.edu \\
The UK Meteorological Office & http://www.metoffice.gov.uk \\
The University of Alberta & http://www.ualberta.ca \\
The University Consortium for Atmospheric Research & http://www.ucar.edu \\
The University of Toronto & http://www.utoronto.ca \\
\end{tabular}