Awesome

// tl:dr
let RustyCS = CS.iter().zip(Rust.iter())

Contents

• Contents
• Why Learn Computer Science
• Why Learn Rust
• Why This Curriculum
• How To Use
• Contribution and Community
• Acknowledgment
• Curriculum
  • Prerequisites
  • Introduction
  • Programming Languages
  • Discrete Structures
  • Systems Fundamentals
  • Algorithms
  • Architecture and Organization
  • CS Tools
  • Information Management
  • Networking and Communications
  • Operating Systems
  • Distributed Computing and Advanced Databases
  • Compilers and Interpreters
  • Information Assurance and Security
  • Software Engineering
• Rust Handy references
  • Managing your project
• Blogs
• Channels
• Rust Community
• Jobs

Why Learn Computer Science

From Teachyourselfcs.com:

There are 2 types of software engineer: those who understand computer science well enough to do challenging, innovative work, and those who just get by because they’re familiar with a few high level tools. Both call themselves software engineers, and both tend to earn similar salaries in their early careers. But Type 1 engineers progress toward more fulfilling and well-remunerated work over time, whether that’s valuable commercial work or breakthrough open-source projects, technical leadership or high-quality individual contributions. Type 1 engineers find ways to learn computer science in depth, whether through conventional means or by relentlessly learning throughout their careers. Type 2 engineers typically stay at the surface, learning specific tools and technologies rather than their underlying foundations, only picking up new skills when the winds of technical fashion change. Currently, the number of people entering the industry is rapidly increasing, while the number of CS grads is relatively static. This oversupply of Type 2 engineers is starting to reduce their employment opportunities and keep them out of the industry’s more fulfilling work. Whether you’re striving to become a Type 1 engineer or simply looking for more job security, learning computer science is the only reliable path.

Why Learn Rust

There are a lot of reasons why one would want to learn Rust, but I'm going to mention just what I think are the killer features: Rust is a low-level programming language with direct access to hardware and memory, giving you the same power that C and C++ do with a greater focus on memory safety. Rust also makes it easier to write concurrent programs by preventing data races at compile time. Another great thing about Rust is that Rust is a low-level language with abstractions from higher-level languages without any performance sacrifices (zero-cost abstraction). Rust is general-purpose and can be used for almost anything from embedded systems, building operating systems to running on the browser via webassembly. The possibilities are endless.

Why This Curriculum

At first, I made a CS curriculum based on the ACM & IEEE Computer Science Curricula 2013 guidelines to make up for the low learning quality in the university where I study. Then I found out about Rust and fell in love with it. I wanted to jump in right away, but I had my CS courses to finish first, later I had this idea about spreading some Rust over my CS curriculum, this way I can learn them both at the same time, plus Rust being a system programming language it's almost imperative to have a strong CS background first before you can use it effectively.

How To Use

This is a Computer Science curriculum first and foremost, <del>designed to mimic an undergraduate Computer Science degree</del> focused on systems programming and provides high-quality learning content from top-notch universities adhering to the ACM & IEEE Computer Science Curricula 2013 guidelines.

You may follow this curriculum even if you are not interested in learning Rust by skipping Rust sections. For those who are here to learn both CS and Rust, the way to go is to study the material in the given order. Each section contains the academic course(s) and the relevant Rust implementation(s). you start with the academic part and then move to the applicative Rust part if found.

Make sure that you satisfy the prerequisites before starting any course.

Contribution and Community

Everyone is welcome to contribute to this curriculum. For broken/missing links, spelling errors, and language refactoring, please create a pull request with the fixes. If you think that there is an issue with the curriculum, like missing or wrong prerequisites, wrong order of courses, inaccurate or a better description of courses and sections, better alternatives to the suggested courses, please open an issue stating what's wrong and your suggestion to fix it.

Acknowledgment

Although this was an original idea, I consider The OSSU and Teachyourselfcs curriculums prior arts. This project borrowed a lot from them in terms of courses recommendations and organizations, even quotes. Many thanks to them.

Curriculum

Prerequisites

The below material assumes that you have already finished high school. If not, you can study the needed math and physics course at Khan Academy. Additionally, some courses require Calculus as a prerequisite. You can either go through the courses and learn the required calculus part when needed or take a complete calculus course such as the one on Khan Academy or MIT-Open Learning Library.

Additionally, the curriculum starts with How to Code courses as introductory courses. These courses may be somewhat challenging. Initially, the curriculum suggested starting with Python for Everybody but later removed to reduce the number of introductory materials, and the idea of learning python where comers expect to learn Rust may be unappealing to most. However, feel free to take it if you struggle with these courses. It's a good starting point for those who never wrote a line of code before.

Introduction

CS Part: <br> Start here. These two courses will teach you general ways of thinking about programming and how to write programs even if you have experience. the knowledge that you will learn here will serve you forever and you will use them in literally everything.

Check these summeries to get a sneak peak of what is coming ahead in your CS journey here and here.

Rust Part: <br> After finishing the above courses, you should be able to read the book, in addition to the official book, another small book with a gentler introduction to some concepts is provided. And while you're at it, solve the exercises and questions below to help retain the knowledge. There is no particular order to go through the materials except of course reading the book.

• Book-The Rust Programming Language Book The offcial book of the language will give you an overview of the language from first principles.
• Track-Rustlings
• Track-Rust By Practice
• Project-PNGme - An Intermediate Rust Project.
• Project-Triangle From Scratch - draw a triangle using Win32, but no external crates

Programming Languages

In addition to learning programming languages, learning about programming languages will benefit you tremendously.

Discrete Structures

CS Part: <br>

This course covers the most important parts of mathematics relevant to Computer Science, which are needed later in areas like Algorithms and Sytems studies. My official recommendation is Discrete Mathematics with Applications by Susanna S. Epp, it provides a gentler introduction, and the material is explained in a very good way. Sadly the book is not free. As an alternative, you can work through the Trefor Bazett course on Youtube, it has decent quality and is accompanied by a free book. Make sure to check How to Solve it book, a unique guide to general problem solving.

Rust part:<br> These resources are not related to this section, but they are included here to keep your memory sharp and to be able to switch between doing the course and practicing Rust so you don't get bored.

• Track-Rust Exercism
• Track-Rust Practice Questions
• Project-Build your own JIRA with Rust - A test-driven workshop to learn Rust building your own JIRA clone!
• Book-Rust Programming by Example
• Book-Creative Projects for Rust Programmers

Systems Fundamentals

CS Part: <br>

The best course to learn how computers work and how to build one. This course will prepare you for the upcoming courses about computer architectures and operating systems.

Algorithms

CS part:<br> Familiarity with common algorithms and data structures is one of the most empowering aspects of a computer science education. This is also a great place to train one’s general problem-solving abilities, which will pay off in every other area of study. How to Solve it book will also be usefull here.

Rust part:<br> Solving problems with the language that you are trying to learn is the best way to learn it. Go ahead and solve as most as you can. Check more problems at leetcode.com, Hackerrank, Codewars, etc...

• Book-Hands-On Data Structures and Algorithms with Rust
• Repo-Rust Gym: Leetcode, AoC, Googe..
• Playlist-Rust Advent of Code 2019 - Brian Myers
• Repo-ProjectEulerRust
• Repo-Algorithm Cookbook in Rust
• Book-Learning Rust With Entirely Too Many Linked Lists

Architecture and Organization

Learning what is going on under the hood of a computer system is what makes the difference between a programmer and a good programmer. Understand computer systems will let you write faster, more efficient and more reliable software.

CS Tools

CS part:<br> This course will teach you the general tools that you may need and make it easier for you to create programs like the shell and Git.

Rust Part: <br> These resources are not related to this section, but they are included here to keep your memory sharp and to be able to switch between doing the course and practicing Rust so you don't get bored.

• Rust Quiz

Information Management

It's necessary to learn how databases work. You will find yourself dealing with them in almost all fields of programming. Don't be intimidated by the number of courses, they are short.

Networking and Communications

CS part:<br> From teachyourselfcs.com: Given that so much of software engineering is on web servers and clients, one of the most immediately valuable areas of computer science is computer networking. Our self-taught students who methodically study networking find that they finally understand terms, concepts and protocols they’d been surrounded by for years.

Rust part:<br> A reimplementation of what you learned about networks in Rust. This will be of great value in your future projects.

• Course-TIKV Practical Networked Applications in Rust
• Book-Network Programming with Rust
• Project-Building a DNS server in Rust
• Course-Low-Level Academy

Operating Systems

CS part:<br> So what happens when a program runs?

Rust part:<br>

• Book-Rust in Action
• Blog-Writing a file system from scratch in Rust
• Blog Series-Writing an OS in Rust
• Book-The Theseus OS Book
• News Letter-OSDev,Operating System Development in Rust
• Book-intermezzOS OS

Distributed Computing and Advanced Databases

CS part:<br> “It’s typical now for even very small applications to run across multiple machines. Distributed systems is the study of how to reason about the trade-offs involved in doing so.”

Rust part:<br>

• Book-Async Raft - the Raft distributed consensus protocol in async Rust
• TIKV Training program in Distributed Systems this course focuses on implementing important distributed algorithms, including the Raft consensus algorithm, and the Percolator distributed transaction protocol.

Compilers and Interpreters

“If you don't know how compilers work, then you don't know how computers work”. The first two courses cover the same topic, choose one. CS part:<br>

Rust part:<br>

• Playlist-Rust Ports of Carfting interpreters
• Project-Writing Interpreters in Rust: a Guide
• Project-Make a Lisp - Joel Martin
• Project-Cross-platform Brainfuck Interpreter implementation in Rust
• Blog Series-Why and how we wrote a compiler in Rust
• Project-Build a language VM
• Intro to the Architecture of LLVM

Information Assurance and Security

todo()! //Inshallah

Software Engineering

todo()! //Inshallah

Rust Handy references

These are useful resources but are not meant to be read cover to cover. Instead, use them every time you are developing a project. you'll find references for some features that you may have a hard time understanding or help you when you are wondering what's the best way to read a file or parse an argument.

• Cheat Sheets:
  • Rust Cheat Sheet
  • Another Cheat sheet
  • Rust Types Methods Cheat sheet
  • Another Rust Types Methods Cheat sheet
  • The Periodic Table of Rust Types
  • Rust Ownership Cheat sheet
  • Iterator Cheat Sheet
  • Rust Container Cheat Sheet
• References:
  • Book-Rust for Rustaceans - Covers how to design reliable, idiomatic, and ergonomic Rust programs based on best principles.
  • Book-Programming Rust
  • Official Ressources
    • Standard Library
    • Cargo Book
    • Rust doc Book
    • Rustc Book
    • Clippy
    • Compiler Error Index
    • The Rust Reference
• Guidelines and Idioms:
  • Rust by Example A community driven collection of example code which follow Rust best practices.
  • Rust Cook Book a collection of simple examples that demonstrate good practices to accomplish common programming tasks.
  • Rust API guidelines An extensive list of recommendations for idiomatic Rust APIs.
  • Rust Design Patterns A catalogue of design patterns in Rust.
  • Effective Rust - Rust guidelines
  • Rust Programming Tipz A collection of software engineering techniques for effectively expressing intent with Rust.
  • The Rust Performance Book
  • Secure Rust Guidelines
  • stdx: Learn these crates first as an extension to std
  • Common Newbie Mistakes and Bad Practices in Rust: Bad Habits
  • Hexagonal architecture in Rust
• Debugging:
  • explaine.rs
  • Compiler Explorer
  • Pernos demo
• Compiling
  • How to speed up the Rust compiler in March 2023
  • rust-cross, Everything you need to know about cross compiling Rust programs! - Jorge Aparicio
• Benchmark and Fuzzing:
  • Benchmarking programs in Rust
  • Criterion.rs Benchmark
  • Rust verification tools
  • Rust Fuzz Book Fuzz testing
• Cargo:
  • Most useful Rust cargo tools
• Tools:
  • Awesome Rust: Development Tools
  • Awesome Rust: Libraries
  • Caniuse.rs - Rust feature search
• CI/CD:
  • Great Rust CI

Managing your project

• Keeping Rust projects' README.md code examples up-to-date
• Guide on how to write documentation for a Rust crate - Writing good documentation with rustdoc including many examples.
• Building an open source project?
  • TP 101: Introduction to open source software
  • TP 102: How to use Git and GitHub
  • TP 103: Build a welcoming community

Blogs

• Home – Read Rust
• Hackr.io: most upvoted Rust ressources
• Morioh
• Awesome Rust, A curated list of Rust code and resources.
• Idiomatic Rust
• AreWeRustYet
• Lobsters.rs
• Rust official Blog
• This Week in Rust
• Dev.to Rust
• Llogiq on stuff
• Niko Matsakis
• Endler
• Lucas Palmieri
• Michael Gattozzi
• MICHAEL-F-BRYAN
• Faster Than Lime
• Ralf's Ramblings (ralfj.de)
• Antoyo's Blog
• Blogs - Without boats, dreams dry up
• Sylvain Kerkour
• matklad
• Yoshua Wuyts
• Possible Rust A blog for intermediate Rust programmers exploring real-world code and design patterns.

Channels

• Awesome Rust Streaming
• Manning Publications Rust channel
• Gamozolabs
• Jon Gjengset

Rust Community

• The Rust Programming Language Forum
• Stackoverflow Rust questions
• Rust Mentors
• Rustacean Station
• Rust-Saar
• Rust Programming Language Community Discord Server
• Rust Programming Language Official Discord Server
• Rustacean Station Discord Server
• Rust بالعربي Discord Server
• zulip chat

Jobs

• RustJobs.com
• RustJobs.dev
• Companies that use Rust