Don't get me wrong, the learning curve is real!
However Python devs have a head start โ you already think in types, you already care about elegance + clean code.
Which tip would've helped you most? Or any other ones?
The full agenda is now on our website ๐ฅ
๐ Visit https://www.rustikon.dev/agenda for all the details!
Don't have your ticket yet? Grab it here: https://www.rustikon.dev/tickets
We can't wait to see you in Warsaw this March!
100 Quiz To Learn Rust (Rust MCQ 2026)
Attempt 100 Rust quiz questions to test your knowledge and improve your Rust skills. This Rust MCQ 2026 quiz helps beginners and learners practice important Rust concepts like ownership, borrowing, traits, lifetimes, Option, Result, error handling, etc.
๐ฆ https://codeforgeek.com/100-rust-quiz-mcq/
#rust #rustlang #coding #code #learnrust #learncoding #ownership #borrowing #traits #lifetimes #Option #Result #error #handling #quiz
Rust unit testing: basic HTTP testing
Real-world application testing - Beginning with Axum
๐ฆ https://jorgeortiz.dev/posts/rust_unit_testing_basic_http_srvr/
#rust #rustlang #axum #http #testing #dev #web #realworld #beginner #srv #learnrust #beginnerfriendly #webdev #apptesting
Day 42 of learning Rust as a C# dev:
Rust didnโt just teach me a new language; it taught me to think differently.
Ownership, safety, simplicity... and some hard compiler love.
Final reflections here:
https://woodruff.dev/final-reflections-what-rust-taught-me-as-a-c-dev/
Day 42, and here we are. Six weeks of learning Rust from the perspective of a C# developer. We covered the basics, wrestled with ownership, danced with traits and lifetimes, and shipped a working CLI app. Along the way, there were moments of frustration, lightbulb moments, and more than a few โwhy is this so hardโ conversations with the compiler. This final reflection is about stepping back and asking the big questions. What did Rust really teach me? What am I taking back to my C# projects? What might be next?
Day 41 of learning Rust as a C# dev:
I finally ran the performance tests.
Rust starts faster, uses less memory, and feels... sharp.
It doesnโt just run. It flies.
Hereโs what I found:
https://woodruff.dev/performance-check-does-rust-really-fly/
Welcome to Day 41, and we are almost done! Today, we are putting Rustโs performance reputation to the test. Rust has a reputation for being fast. But how fast? If you have been living in the C# world where the JIT and garbage collector handle things for you this is a good chance to see how Rust stacks up when it comes to raw speed.
Day 40 of learning Rust as a C# dev:
Packaging and releasing a CLI tool with Cargo is way easier than I expected.
One config file. One command. Done.
Hereโs how it works:
https://woodruff.dev/packaging-and-releasing-a-rust-cli-tool/
Day 40, and today we are looking at how to package and release your Rust CLI app. You have written the code, added argument parsing, handled the logic, and even written tests. Now it is time to get that shiny CLI tool into the hands of others. This process will feel familiar if you have worked with .NET global tools. Rustโs cargo makes it easy to build, release, and share your command-line apps.
Day 39 of learning Rust as a C# dev:
Writing tests in Rust is simple, fast, and built right in.
No frameworks, no fluff, just #[test] and cargo test.
Hereโs how it compares to .NET:
https://woodruff.dev/writing-tests-in-rust-familiar-and-fast/
Onward to Day 39. Today, we're discussing testing in Rust. If you are a C# developer, you have probably spent time with xUnit, NUnit, or MSTest. You know the usual [TestMethod] or [Fact] attributes and Assert.Equal calls. Rustโs testing system is going to feel pretty familiar with a bit of Rust flair.
I'm creating a #RustLang tutorial, and I asked #ChatGPT and #Gemini which should come first: functions or math.
Gemini says functions should come before math.
ChatGPT says the exact opposite.
So I went to Grok to break the tie:
"For a Rust tutorial, teach functions first. Functions are a core concept in Rust, foundational for structuring code and understanding syntax like fn, parameters, and return types...
Agree?
Day 38 of learning Rust as a C# dev:
Reading, writing, and creating files and directories. Rust lends a sense of cleanliness and deliberation.
No magic, just std::fs, ?, and a lot of compiler support.
Hereโs what I learned:
https://woodruff.dev/working-with-files-and-the-filesystem-in-rust/
Welcome to Day 38. Today, we're getting our hands dirty with file I/O. Reading and writing files is one of those tasks every app must perform at some point. If you have written C# code using System.IO this is going to feel familiar but with a Rust twist.
Bob Belderbos
Rustikon
๐๐๐๐๐โ๐๐ก๐๐
Chris Woody Woodruff
Peter Beens 
