You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The projects themselves do not attempt to explain how to write them, just what to write, along with hints, suggestions, and tradeoffs.
They are intended to be accompanied by lessons and also external "readings". The lessons are on hold for the first iteration of the course, which makes the readings essential.
One of the purposes of this project is to expose new Rust programmers to resources they might know about, so the best material is often going to be blog posts from experts. One of the per-requisites for the entire course is to read The Rust Book, so we can provide the most value by providing readings that are not from the book, often time blog posts by experts. In some cases though individual book chapters are worth linking to. For example, error handling is such a tricky topic that just reading the book's chapter on error handling is not enough - we might link it, but we would definitely link to other resources as well.
Read through the text, identify the problems being solved, find single-page resources that contain potential answers to those problems and add them to the project.
There's currently no section of the project's devoted to this, so add one.
The text was updated successfully, but these errors were encountered:
The projects themselves do not attempt to explain how to write them, just what to write, along with hints, suggestions, and tradeoffs.
They are intended to be accompanied by lessons and also external "readings". The lessons are on hold for the first iteration of the course, which makes the readings essential.
One of the purposes of this project is to expose new Rust programmers to resources they might know about, so the best material is often going to be blog posts from experts. One of the per-requisites for the entire course is to read The Rust Book, so we can provide the most value by providing readings that are not from the book, often time blog posts by experts. In some cases though individual book chapters are worth linking to. For example, error handling is such a tricky topic that just reading the book's chapter on error handling is not enough - we might link it, but we would definitely link to other resources as well.
Read through the text, identify the problems being solved, find single-page resources that contain potential answers to those problems and add them to the project.
There's currently no section of the project's devoted to this, so add one.
The text was updated successfully, but these errors were encountered: