A step-by-step onboarding plans and related materials for beginners.
Suppose a new team member joins the company. This person used a different programming language in his previous company, so needs to learn a new programming language that fits company's technology stack. 🤔
I think we should write an onboarding plan for this member to work with us. Let's share various scenarios with collective intelligence to help many people. 🤗
Don't feel overwhelmed! Also, always ask questions if you don't know anything! It's your first time learning. 😀
If you think that these can be improved in any way, please do suggest.
- Week 1 ~ 2: Learn base knowledge (Rust programming language)
- Week 1
- Day 1 (Official Tutorial 1 ~ 3)
- Setup environments (The Rust Toolchain only)
- Run first Rust code
- Understand Rust basics
- Day 2 (Official Tutorial 4 ~ 6)
- Understand ownership, borrowing, and pattern matching
- Practice simple exercises and code review
- Day 3 (Official Tutorial 7 ~ 9)
- Understand the relationship among packages, modules, and crates
- Understand basic collections such as
Vec
,String
andBTreeMap
- Understand basic error handling
- Practice simple exercises and code review
- Day 4 (Official Tutorial 10 ~ 12)
- Understand generics and traits
- Understand how to write and run test code
- Practice simple exercises and code review
- Day 5 (Official Tutorial 13 ~ 15)
- Understand iterators and closures
- Understand smart pointers such as
Box<T>
,Rc<T>
andRefCell<T>
- Practice simple exercises and code review
- Day 1 (Official Tutorial 1 ~ 3)
- Week 2
- Day 1 (Official Tutorial 16 ~ 18)
- Understand concurrency in Rust using
Mutex<T>
andArc<T>
- Understand OOP in Rust
- Practice simple exercises and code review
- Understand concurrency in Rust using
- Day 2 (Official Tutorial 19 ~ 20)
- Understand advanced features in Rust such as unsafe and macros
- Practice simple exercises and code review
- Day 3
- Practical project #1: Rectangles
- Practical code review
- Day 4
- Practical project #2: Circular Buffer
- Practical code review
- Day 5
- Practical project #3: Doubly Linked List
- Practical code review
- Day 1 (Official Tutorial 16 ~ 18)
- Week 1
- Week 3: Utilize code by using various crates (tokio, serde, prost, rxRust)
- Day 1 (tokio)
- tokio: A runtime for writing reliable asynchronous applications with Rust
- Practice simple exercises and code review: TCP chat
- Day 2 (serde)
- serde: Serialization framework for Rust
- Practice simple exercises and code review: JSON RPC
- Day 3 (prost)
- prost: a Protocol Buffers implementation for the Rust Language
- Practice simple exercises and code review: Protobuf RPC
- Day 4 (rxRust #1)
- rxRust: Rust implementation of Reactive Extensions
- Understand ReactiveX
- Understand rxRust basics
- Practice simple exercises and code review
- Day 5 (rxRust #2)
- rxRust: Rust implementation of Reactive Extensions
- Understand rxRust internals
- Practice simple exercises and code review
- Day 1 (tokio)
- Week 4: Collaborate with cross-platform (iOS and WebAssembly)
- Day 1 (Rust with iOS #1)
- Setup environments (iOS related)
- Practice Building and Deploying a Rust library on iOS
- Day 2 (Rust with iOS #2)
- Practical exercises and code review
- Rust with iOS + tokio
- Rust with iOS + prost
- Rust with iOS + rxRust
- Practical exercises and code review
- Day 3 (Rust with WebAssembly #1)
- Setup environments (WebAssembly related)
- Practice Conway's Game of Life
- Day 4 (Rust with WebAssembly #2)
- Practical exercises and code review
- Rust with WebAssembly + tokio
- Rust with WebAssembly + prost
- Rust with WebAssembly + rxRust
- Practical exercises and code review
- Day 5 (Cross-platform)
- How to make a core engine to support cross-platforms
- Practical exercise and code review
- Consider cross-platform compatibility
- Using tokio, prost and rxRust
- Day 1 (Rust with iOS #1)
- Beginner
- Intermediate
- Advanced
- Other resources
If you think any of the onboarding plans can be improved, please do open a PR with any updates and submit any issues. Also, I will continue to improve this, so you might want to watch/star this repository to revisit.
Contributions are always welcome, either reporting issues/bugs or forking the repository and then issuing pull requests when you have completed some additional coding that you feel will be beneficial to the main project.
- Open pull request with improvements
- Discuss ideas in issues
- Spread the word
- Reach out to me directly at utilforever@gmail.com or
The class is licensed under the MIT License:
Copyright © 2022 Chris Ohk.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.