Many Days Later
I owe you an apology. I said I was going to document my journey learning Rust daily… Yeah… that didn’t happen 😅 Life happened. Work happened. Overthinking happened. But I didn’t stop learning. And...

Source: DEV Community
I owe you an apology. I said I was going to document my journey learning Rust daily… Yeah… that didn’t happen 😅 Life happened. Work happened. Overthinking happened. But I didn’t stop learning. And honestly, that’s what matters. So here we are — many days later. Quick Recap Last time, we: Installed Rust Built a simple guessing game Learned basic syntax (let, mut, match, use) At that point, Rust felt… “Not that scary.” But then I kept going. And I finally met the thing everyone warns you about: Ownership The Project Before we dive in, let me make this real. I’m not just learning Rust for fun. I’m building something. A ride sharing app. Think: requesting rides matching drivers tracking trips handling payments (eventually) Why this? Because it’s complex enough to force me to actually understand Rust, not just play with syntax. So… What is Ownership? Let me explain this in the simplest way possible. Ownership is basically: Who owns a piece of data in your program And Rust is VERY strict ab