<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Writing on DataLeaf</title><link>https://dataleaf-642346.gitlab.io/tags/writing/</link><description>Recent content in Writing on DataLeaf</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 21 Apr 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://dataleaf-642346.gitlab.io/tags/writing/index.xml" rel="self" type="application/rss+xml"/><item><title>What a research notebook is for</title><link>https://dataleaf-642346.gitlab.io/posts/what-a-research-notebook-is-for/</link><pubDate>Fri, 21 Apr 2023 00:00:00 +0000</pubDate><guid>https://dataleaf-642346.gitlab.io/posts/what-a-research-notebook-is-for/</guid><description>&lt;p&gt;Laboratory scientists learn early that an experiment not written down did not happen. The bound notebook, with numbered pages and dated entries in ink, is one of the oldest instruments of experimental science, and it survives because it does something no other record does: it captures what the experimenter knew and intended at the moment of acting.&lt;/p&gt;&#10;&lt;p&gt;Computational work has inherited the experiments but not, in most places, the notebook. A modern analysis leaves behind a repository full of code, a directory full of outputs, and perhaps a commit history. It is easy to believe that this is a complete record. It is a record of what was done. It is almost never a record of why.&lt;/p&gt;</description></item></channel></rss>