Deployed 7f10cfe with MkDocs version: 0.15.3

This commit is contained in:
Isaac Slavitt
2016-04-28 18:14:27 -05:00
parent 84e1f4ffa3
commit ac656d6e1e
2 changed files with 4 additions and 4 deletions
+2 -2
View File
@@ -177,7 +177,7 @@
<li>Feel confident in the conclusions at which the analysis arrives</li>
</ul>
<p>A good example of this can be found in any of the major web development frameworks like Django or Ruby on Rails. Nobody sits around before creating a new Rails project to figure out where they want to put their views; they just run <code>rails new</code> to get a standard project skeleton like everybody else. Because that default project structure is <em>logical</em> and <em>reasonably standard across most projects</em>, it is much easier for somebody who has never seen a particular project to figure out where they would find the various moving parts.</p>
<p>Another great example is the <a href="https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard">Filesystem Hierarchy Standard</a> for Unix-like systems. The <code>/etc</code> directory has a very specific purpose, as does the <code>/tmp</code> folder, and everybody (more or less) agrees to honor that social contract. That means an Red Hat user and an Ubuntu user both know roughly where to look for certain types of files, even when using each other's system — or any other standards-compliant system for that matter!</p>
<p>Another great example is the <a href="https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard">Filesystem Hierarchy Standard</a> for Unix-like systems. The <code>/etc</code> directory has a very specific purpose, as does the <code>/tmp</code> folder, and everybody (more or less) agrees to honor that social contract. That means a Red Hat user and an Ubuntu user both know roughly where to look for certain types of files, even when using each other's system — or any other standards-compliant system for that matter!</p>
<p>Ideally, that's how it should be when a colleague opens up your data science project.</p>
<h3 id="you-will-thank-you">You will thank you</h3>
<p>Ever tried to reproduce an analysis that you did a few months ago or even a few years ago? You may have written the code, but it's now impossible to decipher whether you should use <code>make_figures.py.old</code>, <code>make_figures_working.py</code> or <code>new_make_figures01.py</code> to get things done. Here are some questions we've learned to ask with a sense of existential dread:</p>
@@ -372,5 +372,5 @@ from preprocess.build_features import remove_invalid_data
<!--
MkDocs version : 0.15.3
Build Date UTC : 2016-04-28 23:13:35.632752
Build Date UTC : 2016-04-28 23:14:27.721868
-->
File diff suppressed because one or more lines are too long