The Software Carpentry Foundation seeks to hire a new Executive Director to build relations with partners, oversee the development of our curriculum, be Software Carpentry's spokesperson, and work with the Steering Committee to set our future direction. The successful candidate will initially be co-Executive Director, and will job-share with the current Executive Director during a brief transition period, after which they will become the new ED.
To apply, please send email to firstname.lastname@example.org by July 31, 2015 with "Co-Executive Director" in the subject line, and include:
A brief resume or CV (approximately two pages).
A brief statement (approximately two pages) of what you would hope to accomplish in your first year as Executive Director. Please also include a paragraph about any work you may have done with Software Carpentry in the past and another about your experience working with other volunteer organizations.
We will begin interviews immediately after July 31, and hope to have someone in place no later than the end of August....read more
With Software Carpentry's rapid growth over the past couple of years, the combined responsibilities of being the Executive Directory and running the instructor training program have become more than a single person can manage. And after five years of working to grow Software Carpentry into the world-wide community it has become, I'd like to spend more time with my family.
The Software Carpentry Foundation is therefore hiring a new Executive Director. I will transition to running instructor training so that the new ED can devote themselves to building relations with partners, overseeing the development of our curriculum, being Software Carpentry's spokesperson, and working with the Steering Committee to set our future direction. Our new hire will initially be co-Executive Director, and will job-share with me during a brief transition period, after which they will become the new ED.
This is the next logical step in Software Carpentry's evolution, and one that we have been working toward for more than a year. As with the election of the Steering Committee in January, it's a sign that Software Carpentry is here to stay, and nothing could make me prouder....read more
June 29 - July 06, 2015: Research Software Engineers, Not Changing Lesson Build Tools, and Moving to Python3.By Anelda van der Walt / 2015-07-06
- Do you know what a Research Software Engineer is or why we desperately need to recognise the role RSEs are playing in research? Read about the history of RSEs and a fellowship programme available for RSEs in the UK.
- Version 5.4 of our lessons will be released at the end of November, rather than mid-August, and lesson build tools will remain unchanged until then. Most importantly we'll be changing the Python lessons to run on Python 3.
- Are you looking for other ways to contribute to Software Carpentry? Visit our Projects page to see an exciting list of opportunities for you to get involved.
A week ago, we posted a proposal to use Jekyll to build our lessons rather than Pandoc. The immediate reaction was almost uniformly positive, but in the days since, people have pushed back on two fronts:...read more
By now, many people in the UK (well, many of the sort who read this blog) will have heard the term Research Software Engineer, but what exactly is an RSE, and what effect will the creation of this title have? To understand, we need to go back to the Software Sustainability Institute's Collaborations Workshop in early 2012 (summarized in these blog posts and others). Those discussions led to this position paper at Digital Research 2012, whose authors argued that:...read more
June 17-28, 2015: A Lesson on Make, AMY 0.4 Released, Opportunities to Contribute, Practical Tips for Running Workshops, and Appointing a Program Coordinator.By Anelda van der Walt / 2015-06-28
- Software Carpentry is hiring a Program Coordinator. Please see the blog post for more information.
- A new lesson on Make has been added to the Software Carpentry repertoire.
- AMY 0.4 was released. New features are listed in the blog post.
- Would you like to contribute by recycling previously submitted assessment excercises and adding the best ones to our lessons? It can now easily be done by visiting the newly created repo of submitted MCQs and exercises.
- Learner assessment has been receiving a lot of attention over the past months. A first draft of the new feedback survey is now available. We're looking forward to your comments/contributions.
- Should we change our lesson templates to make use of Jekyll rather than Pandoc? Please contribute to the discussion to help us make an informed decision.
- Greg Wilson summarised lessons learned from teaching instructors. There is again an opportunity for you to contribute to the direction instructor training takes in future. Let us hear from you?
- Splitting the terminal window allows the instructor to display recent commands while continueing with the lesson at the same time. Read the post by Raniere Silva to see how it's done.
The mentoring subcommmittee hosted instructor debriefings on 23 June 2015 to discuss recently completed workshops. We are delighted that so many new instructors are joining us at these sessions as a way to prepare for upcoming workshops, and welcome anyone else interested to attend as well. Below we highlight a few discussion points from our sessions, including issues with lesson pacing and Python installation, as well as tips on using the etherpad and GitHub organizations. A more in-depth synopsis of a recent workshop can be found in this fantastic post on Raniere Silva's blog....read more
I wrote about our experiments with the format of instructor training back in May. At that time, we had run the class as:
- a multi-week online class,
- an in-person two- or three-day class, and
- a mixed mode with the trainees physically together for two days with the trainer coming in via teleconference.
We have since tried the mixed mode twice with the trainees at three different sites (three universities in Arizona for one run, and universities in Cape Town, Sheffield, and Ann Arbor for the other). We've also gathered a lot of feedback on what people want from instructor training and what its prerequisites should be. Here's what we've learned....read more
At the beginning of June Rémi Emonet, Kwasi Kwakwa, and Chelsea Chisholm ran a workshop at CERN. Rémi has just posted a review. It went well, and there are a lot of good ideas in his write-up—from using a whiteboard for diagrams to the IPython Notebook's successor (Jupyter) and some semi-improvised intermediate material....read more
A recurring complaint about our lesson template is that it requires authors to commit generated HTML files to their repositories as well as their Markdown source files. This is necessary because we use Pandoc to convert Markdown to HTML, but GitHub will only run Jekyll.
There were a bunch of reasons for using Pandoc instead of Jekyll, but it is now clear that the simplicity of only committing Markdown—i.e., of using GitHub pages the way they're meant to be used—is more important. We have therefore created a prototype of a Jekyll-based template (which is rendered here). The most important changes are:...read more
Our sibling organization Data Carpentry teaches basic concepts, skills, and tools for working more effectively with data.
July 6-7, 2015
Jul 6-7, 2015
Jul 9-10, 2015
West Vancouver Memorial Library, Welsh Hall
July 9-10, 2015
University of Queensland
Jul 13-14, 2015
University of Melbourne
Jul 13-15, Jul 17 2015
University of Nebraska - Lincoln
Jul 15-16, 2015
SAP Headquarters near London Heathrow
Jul 15-17, 2015
University of Cape Town
Jul 16-17, 2015
Hospital For Sick Children
July 16-17, 2015
|See all upcoming workshops...|