Incubator Lesson Spotlight: Programming with Julia

Get involved in the community’s development of a new lesson to teach Julia to novices.

The Incubator Lesson Spotlight highlights a lesson under development by our community in The Carpentries Incubator. In this edition, we look at the progress being made on the Programming with Julia lesson, and hear from the authors about how The Carpentries community can get involved with the ongoing development of this lesson.

Lesson Profile

  • Title: Programming with Julia
  • Lesson Pages: https://carpentries-incubator.github.io/julia-novice/
  • Lesson Repository: https://github.com/carpentries-incubator/julia-novice

Learning Objectives

  • using the Julia REPL
  • get comfortable with the package manager and environments
  • learn syntax for common tasks (types, control flow, functions & methods, modules)
  • finding, using and creating packages
  • writing tests

Target Audience

People with some programming experience that are new to Julia. Particularly people doing scientific computing.

Lesson Progress

The lesson is in the pre-alpha stage at its first iteration and has yet to be taught.

How You Can Help Develop This Lesson

We are looking for people

  • reviewing the lesson
  • teaching the lesson
  • adding content (e.g. multiple dispatch)
  • providing more visuals and interactive content

Join the juliaswc channel in The Carpentries Slack workspace or open an issue on the lesson repository on GitHub


About This Series

Incubator Lesson Spotlight is a regular feature in The Carpentries blog and Carpentries Clippings newsletter, highlighting the great work our community is doing to develop new lessons in The Carpentries Incubator. Developers of any lesson in the Incubator are encouraged to submit details about their material for inclusion in the series. If you would like to increase the visibility of your lesson and encourage Carpentries community members to contribute to its ongoing development, fill in this short form.

Dialogue & Discussion

Comments must follow our Code of Conduct.

Edit this page on Github