Skip to content

Latest commit

 

History

History
19 lines (12 loc) · 1.32 KB

swc-conclusion.md

File metadata and controls

19 lines (12 loc) · 1.32 KB

Conclusion

Most people feel a little overwhelmed at the end of a bootcamp. 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 bootcamp
  • 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. In other words, you now know what you don't know, which is a very important first step (this blog post gives a nice summary of why this is so important)

Getting help

The best way get help after a bootcamp is by interacting with other researchers who write code. There are a number of ways to do this:

  • If you're in Melbourne, come along to our weekly meet-up (known as Hacky Hour)
  • Follow and post questions to the Mozilla Science Lab forum
  • Most programming languages/packages also have their own mailing lists, user groups, support forums and/or conferences (e.g. PyConAu).