<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Naupaka Zimmerman on The Carpentries</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/author/naupaka-zimmerman/</link><description>Recent content in Naupaka Zimmerman on The Carpentries</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 Nov 2024 10:51:28 -0500</lastBuildDate><atom:link href="https://deploy-preview-705--carpentries-website.netlify.app/blog/author/naupaka-zimmerman/index.xml" rel="self" type="application/rss+xml"/><item><title>Hand-crafted relational databases for fun and science</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2016/12/hand-crafted-databases/</link><pubDate>Mon, 05 Dec 2016 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2016/12/hand-crafted-databases/</guid><description>&lt;p>&lt;strong>This post originally appeared on the &lt;a href="https://datacarpentry.org">Data Carpentry website&lt;/a>&lt;/strong>&lt;/p>
&lt;p>I&amp;rsquo;m a microbial ecologist that is primarily interested in
understanding the ecological causes and consequences of plant-microbe
interactions. Like many ecologists these days, my research spans the
gamut from field to lab to laptop. Often the work involves collecting
some leaves from plants in the field or from plants in a greenhouse,
and then culturing from those leaves the fungi that live
asymptomatically within them (a.k.a. endophytic fungi). Sometimes
studying these communities relies on culturing the organisms in Petri
dishes, and sometimes on directly extracting the DNA or RNA from the
samples and sequencing that. One of the hardest things for me has been
simply keeping track of what samples came from where, when, and who
did what to which samples. To give an example: Let&amp;rsquo;s say I&amp;rsquo;ve got a
fungal culture growing in a Petri dish, and I want to know how many
times it has been subcultured (that is, regrown from an existing
culture), when those subculturing events happened, what kind of plant
tissue the original progenitor culture came from, and where that plant
tissue itself came from out in the field. Oh and then downstream, I
also want to know something about all the other such fungi that came
out of that same plant and all their metadata as well. And I want to
be able to get all of that programmatically.&lt;/p></description></item><item><title>Teaching to the Workflow</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2015/09/teaching-to-the-workflow/</link><pubDate>Tue, 15 Sep 2015 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2015/09/teaching-to-the-workflow/</guid><description>&lt;p>&lt;b>This post originally appeared on the &lt;a href="https://software-carpentry.org/">Software Carpentry website.&lt;/a>&lt;/b>&lt;/p>
&lt;p>
 "Teaching to the test" has a deservedly bad reputation,
 but what about "teaching to the workflow"?
 A group of us came together at the
 &lt;a href="http://nceas.github.io/open-science-codefest/">NCEAS Open Science Codefest&lt;/a>
 last year and put together
 &lt;a href="http://www.esajournals.org/doi/abs/10.1890/ES14-00402.1">a paper on open science in ecology&lt;/a>.
 In it,
 we sketch three examples of possible open science workflows
 (Figure 2 in the paper).
 In response,
 I was asked what Software Carpentry should teach
 to prepare people for working in those ways.
 My top three things are (in order):
&lt;/p></description></item></channel></rss>