<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Justin Kitzes on The Carpentries</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/author/justin-kitzes/</link><description>Recent content in Justin Kitzes 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/justin-kitzes/index.xml" rel="self" type="application/rss+xml"/><item><title>Further Thoughts on Building Better Teachers</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2014/09/further-thoughts-on-better-teachers/</link><pubDate>Wed, 10 Sep 2014 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2014/09/further-thoughts-on-better-teachers/</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>
 On Greg's recommendation, I just finished
 reading &lt;a href="http://www.amazon.com/Building-Better-Teacher-Teaching-Everyone/dp/0393081591/">&lt;em>Building
 a Better Teacher&lt;/em>&lt;/a> - it was an interesting book, and a well-written
 story. It turns out that I completely agree
 with &lt;a href="building-better-teachers.html">Greg's assessment&lt;/a>
 of the book's lessons and the challenges facing Software Carpentry,
 but I very much disagree with his proposed solutions!
&lt;/p></description></item><item><title>Collaborative Lesson Development - Why Not?</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2014/03/collaborative-lesson-development/</link><pubDate>Fri, 14 Mar 2014 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2014/03/collaborative-lesson-development/</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>
 A few weeks ago, Greg Wilson asked me:
&lt;/p>

&lt;blockquote>
 Why is there so little open, collaborative development of lesson plans and curricula?
 Is there something that makes teaching different from coding (e.g., open source software)
 and from writing (e.g., Wikipedia)?
&lt;/blockquote>

&lt;p>
 A dozen emails later, I can't claim that we're much closer to a definitive 
 answer, but we have come up with a working hypothesis. 
 We'd be very interested in feedback.
&lt;/p></description></item><item><title>Feedback from UC Berkeley</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2013/04/ucb-feedback/</link><pubDate>Tue, 16 Apr 2013 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2013/04/ucb-feedback/</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>Last weekend we held a bootcamp at the University of California, Berkeley, that was targeted
 for environmental scientists and ecologists. We had a great group of attendees (31 registered,
 28 at start, and 24 at end) and instructors/helpers, and, as a major bonus, had no major technical or
 logistical emergencies to deal with (but see below for some minor ones).&lt;/p>

&lt;p>
 Before the workshop, we had participants fill out a brief pre-workshop survey that we set up
 on Google Drive. The idea was to gather some initial impressions that would help us tailor
 the workshop content. We learned a few particularly useful tidbits from this exercise. First, about
 half the attendees had tried Python before and half had never used it. Second, nearly a third had
 used some form of version control before (big surprise), and half of these had used Git. Third, the
 most requested topics, by far, were related to importing and manipulating different types of data
 and to integrating Python with R and/or ArcGIS.&lt;/p></description></item><item><title>Second Round at Lawrence Berkeley</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2013/03/second-round-at-lawrence-berkeley/</link><pubDate>Wed, 13 Mar 2013 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2013/03/second-round-at-lawrence-berkeley/</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>Last week we finished up our second workshop at Lawrence Berkeley Lab. This 
time around, we tried a more free-form version of the feedback exercise in 
which students live-typed their feedback into an &lt;a href="http://etherpad.mozilla.org">Etherpad&lt;/a>
at the end of each day. This went very well, as 
it gave us time to gather unique comments, get a rough idea of the amount of 
support for each comment, and to respond to some of the comments in real time. 
We asked three questions: what was good, what was bad/confusing, and what we 
didn't do or talk about that we should have.&lt;/p></description></item></channel></rss>