Learning and Teaching Rust

Published on 2 min read

    A new series of posts

    Our Ferrous Systems team has spent the past five years helping people to learn Rust, either as members of the community, or in the context of paid training services. (Yes, we have been doing this before the company even began to exist!)

    In this time, we've trained folks in dozens of companies and across a number of industries, including the automotive industry, cloud platform providers, open source projects, people building embedded systems, and even engineers at Mozilla - where Rust was first developed!

    Over the years, we've noticed a few recurring themes:

    • People say that Rust is a hard language to learn.
    • People say that they are often "fighting" the compiler, or even specific parts of the compiler (e.g., the borrow checker).
    • People say that Rust as a language is "too big" or "too complex" to learn.

    As a company that offers Rust trainings, we have to take these struggles seriously, address their root causes, and ultimately help people succeed. But how do we do that?

    In a new series of posts, we will talk about how we teach Rust and how we address these struggles:

    • We'll talk about difficulties that people encounter in the learning process.
    • We'll show how we help teams all around the world take their first steps in Rust.
    • We'll introduce our training material, our teachers, and our methods.
    • We'll provide insight into learning strategies that students have found to be helpful.

    … because in the end, despite the struggles that can emerge, Rust has become developers' most-loved language over the past four years. As Rust trainers, we're here to spread this enthusiasm and we want you to be part of it!

    We hope you will enjoy reading these posts! In the meantime, please consider signing up for our newsletter or enlisting us as trainers for your team.


    1. Mindsets and Expectations