Brian Anderson

There's a section in project 3 that intends to replace `fn main() -> Result` with custom error reporting, explain about error context chaining, and discuss error serialization for network error...

As noted in project 2, I don't want to use failure for this project. Come up with a new strategy. I have some ideas, but not fully formed, and I'm...

There's a commented out "aside" on error handling history in Rust in project 2. Finish this.

There's a commented-out section in project 2 about basic database architecture. Either fill this in, find a building blocks reading for it, or deleted it. Related to https://github.com/pingcap/talent-plan/issues/206

There's a commented-out section in project 1 about digging into `rustup component` while also introducing `rg`. Fill this section out. Might also introduce https://rust-lang-nursery.github.io/rust-toolstate/ and https://rust-lang.github.io/rustup-components-history/

Between project 2/3/4 we introduce writing to disk, the index, and returning a response over the network, and parallel updates. There's not really any discussion about what it means for...

Somewhere there should be a note that the course is not developed on Windows, the example code may or may not work, and students will probably have an easier time...

As the course gets bigger it would be nice to have an index of topics that link directly to the places in the course they are discussed.

It's been suggested to me that, to be applicable to a wide audience, I should actually list a variety of domains that the knowledge in this course does or should...

Right now the only concrete way for students to know how they are doing on the course is to pass the test suite. Not all of the course is even...