DaleSchool

Congratulations! What's Next?

Intermediate⏱ 10min

Learning Objectives

  • ✓Summarize what you learned and explain it in your own words
  • ✓Identify the next learning topics in the Rust ecosystem
  • ✓Leverage communities, resources, and project ideas to continue learning

You Made It

  • In Phase 1 you picked up syntax, Cargo, and project basics.
  • In Phase 2 you internalized ownership, borrowing, and lifetimes — Rust's core philosophy.
  • In Phase 3 you wrote "idiomatic Rust" with Option/Result, traits, generics, and iterators.
  • In Phase 4 you gained experience with testing, file I/O, CLI tools, and project design.

You can now confidently answer "Can you build a CLI tool in Rust?" with a firm "Yes."

Next Steps Guide

| Topic | Recommended Resources | When You Need It | | ---------------------- | -------------------------------------------- | ---------------------------------------------- | | Async / Networking | async/await, tokio, reqwest, axum | API servers, bots, high-performance networking | | Web & WASM | leptos, yew, wasm-pack | Frontend in Rust or WebAssembly modules | | Data / Systems | sqlx, polars, tantivy | Data processing, search services | | Embedded | embedded-hal, nrf-hal, RTIC | MCU, IoT, firmware development | | Language Deep Dive | unsafe, Pin, macro_rules!, proc macros | Advanced libraries, performance tuning | | Engines / Graphics | bevy, wgpu, nannou | Games, interactive art |

Pick one topic and create a focused 2–4 week learning plan. Small wins stacked over time last far longer than trying everything at once.

Get Involved in the Community

  1. Write a retrospective on your blog or notes about the project you built. Focus on "what you learned, what errors you hit, and how you solved them."
  2. Join forums — Rust Korea Slack/Discord, r/rust, users.rust-lang.org. Ask questions and share answers.
  3. Subscribe to This Week in Rust to stay up to date with the ecosystem.
  4. Contribute to open source — Search for "good first issue" labels on projects like Cargo, Clippy, and Tauri.

Portfolio Tips

  • Add a Demo GIF, installation instructions, and key features card to your GitHub README.
  • Include a "Try it" section like cargo run -- sample so recruiters can quickly understand the project.
  • Set up GitHub Actions for test badges, cargo fmt, and cargo clippy.
  • Tag releases and keep branch history to show your growth over time.

Recommended Resources

  • Docs: The Rust Programming Language (a.k.a. The Book), Rust by Example, Rustlings
  • Courses: "Practical Networked Applications in Rust", "Zero To Production in Rust"
  • Videos: Jon Gjengset's "Crust of Rust" series, Ryan Levick's Rust live coding
  • Tooling: cargo-watch, cargo-expand, cargo-udeps, just (task automation)

Build Your Own Roadmap

  1. Goal — Set a measurable target like "Complete a tokio-based HTTP server tutorial in 8 weeks."
  2. Milestones — Plan concepts and projects on a weekly basis.
  3. Feedback loop — Use weekly logs, code reviews, and community questions.
  4. Celebrate — Reward yourself at each milestone. Sustained learning is powered by enjoyment.

Final Checklist

  • [ ] Updated Rustup and Cargo to the latest version (rustup update)
  • [ ] Organized syntax notes in a personal repo or blog
  • [ ] Published the Phase 4 project on GitHub (README + license included)
  • [ ] Picked the next learning topic and scheduled it on the calendar
  • [ ] Joined a community channel or study group

You've already moved beyond "Rust beginner." Now, as a Rust developer, go find new problems and solve them. Come back to this curriculum whenever you need a refresher, or recommend it to others.

Once again, congratulations on completing the course. See you in the next chapter!

← PreviousStarting a Real Project