aboutsummaryrefslogtreecommitdiffstats
path: root/journal/16jan2009.html
diff options
context:
space:
mode:
Diffstat (limited to 'journal/16jan2009.html')
-rw-r--r--journal/16jan2009.html45
1 files changed, 45 insertions, 0 deletions
diff --git a/journal/16jan2009.html b/journal/16jan2009.html
new file mode 100644
index 0000000..8ec2681
--- /dev/null
+++ b/journal/16jan2009.html
@@ -0,0 +1,45 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head><title>bnewbold thesis</title></head>
+<body style="margin: 25px; font-family: helvetica;">
+<h1 style="border-bottom: 2px solid;">
+Journal: Jan 16, 2009</h1>
+<i>Bryan Newbold, <a href="mailto:bnewbold@mit.edu">bnewbold@mit.edu</a></i><br />
+<i><a href="http://web.mit.edu/bnewbold/thesis/">
+http://web.mit.edu/bnewbold/thesis/</a></i>
+<br /><br />
+<!-- ================================================================ -->
+<!-- ================================================================ -->
+
+Today I setup a git repository (for source code management); it's backed up
+to my personal webspace with a web interface at
+<a href="http://git.bryannewbold.com/?p=8thesis.git">git.bryannewbold.com</a>.
+I'll also copy these journal entries to my
+<a href="http://web.mit.edu/bnewbold/thesis/">athena locker</a>. As an aside,
+keeping notes in a git repository is a great way to maintain scientific
+integrity. We're taught in our lab classes to carefully keep all of our
+notes and printouts of data in notebooks with numbered and dated pages and
+even to sign/initial the corner of each page when it's full to certify it as
+our own work. This makes omissions (missing page numbers) and changes
+(which should be indicated, dated, and signed) stand out. Checkins to git
+repositories are dated and anoted with the author's email address, and can
+even be cryptographically signed. Each commit is hashed with both its contents
+and its parent's hash, so the hash of any commit down the line can be verified
+against the entire chain of commits leading to it; if any files have been
+tampered with it will be obvious, though of course this assurance is only as
+good as the hash algorithms used ;)
+<br />
+<br />
+For the past two weeks or so i've mostly been teaching myself scheme using
+The Little Schemer and The Seasoned Schemer. My notes on those books are
+<a href="http://bryannewbold.com/k/books/littleschemer">here</a> and
+<a href="http://bryannewbold.com/k/books/seasonedschemer">here</a>; my
+notes on scheme itself are
+<a href="http://bryannewbold.com/k/software/scheme">here</a> (note: last link
+temporarily broken?).
+
+<!-- ================================================================ -->
+<!-- ================================================================ -->
+</body>
+</html>