Most people feel a little overwhelmed at the end of a Software Carpentry workshop. The two most important things to note are:
- You don't have to incorporate everything you've learned into your daily workflow right away. In fact, it's not uncommon for people have items like "start using version control" or "add assertions to my code" on their to-do list for a number of months after a workshop
- Don't stress if you didn't master all the content. The most important thing is that you are no longer ignorant to the well-established best practices in computational research.
The best way get help after a workshop is by interacting with other researchers who write code. There are a number of ways to do this:
- Data Science Hobart (Friday mornings 9:15 - 10:15, IMAS)
- Local Python and R user groups
- Most programming languages/packages also have their own mailing lists, user groups, support forums and/or conferences (e.g. PyConAu)