Open DamienIrving opened 4 years ago
The research computing community is so ready for a book like ours, since they're so used to seeing suboptimal research software. CaRCC is really active right now.
There are a bunch of Research Software Engineer Associations around the world that have mailing lists, slack channels, conferences, etc:
Data science bootcamps, e.g.:
Master's programs:
Talk Python To Me podcast: https://talkpython.fm/
(I was on it a few years ago, so I could reach out to the host.)
: delurks : I help organize the CaRCC research-facing track, so I could easily try to get this on the agenda. :grin:
I'd also be willing to help organize a Carpentries discussion session about this.
I'm giving a talk to the Data Intensive Studies Center at Tufts University. Here's the abstract I put together in case others need abstracts in future:
Research Software Engineering with Python
Most researchers pick up enough coding to get their own work done. Whether through an undergraduate introduction to programming course, Carpentries workshop, online tutorial and/or training opportunity provided by their institution or professional society, they cobble together enough Python or R to clean, analyze and plot their research data. Given that writing code for yourself has emerged as an indispensable skill over the past couple of decades, it seems inevitable that writing code for others will become equally important in coming decades. Journals are (slowly) moving towards requiring code to be made available with research papers, and it's increasingly important for researchers to know how to package and release software for use by team members and the wider research community. With this skills progression in mind, a group of data science educators from a variety of different research backgrounds have teamed up to write Research Software Engineering with Python, a ready-to-go university semester course (or self study guide) aimed at helping researchers go from writing code for themselves, to creating tools that help their entire field advance. In this talk I'll take a look at the topics we decided to include (and not include) in the book, which will hopefully help researchers and educators figure out what to learn and teach next.
+1 to @ChristinaLK's idea of a Carpentries discussion session.
I guess the topic of the discussion could be "delivering Software Carpentry as a university semester course" because we really want some people to take the book and actually use it to deliver a semester course?
We should also write a general blog post about the book for the Carpentries blog and try and get it linked in the Carpentries Clippings newsletter.
We should also try and get a news item on the Software Sustainability Institute website which can be used in their weekly news and blog digest.
It would be good if one of us presented at a PyCon somewhere so we have a video recording about the book to share. Most relevant is probably the education and training summit at PyConUS. We've missed the 2021 summit but could aim for 2022.
@DamienIrving let me know what timing might be good for you/the group (both general date ranges + time of day) and I can try to get the discussions on the calendar.
Kidding... but we should start a list of places to advertise the book (blogs, conferences, mailing lists, podcasts, etc).