Challenge 3: A Reflection Across All Three Courses — Possible Solution
====================================================================

(This is a personal-reflection challenge — there's no single correct
answer. Below is one reasonable example response.)

FROM RUST FUNDAMENTALS (COURSE 1): Ownership (Chapter 3) was the most
valuable single idea in the entire track — the realization that a
value having exactly ONE owner, checked at compile time, is what
allows memory to be freed deterministically with no garbage collector
at all. It changed how I think about passing data around even outside
Rust: I now notice, in any language, exactly WHO is responsible for a
piece of data at any given moment, rather than assuming "someone" will
eventually clean it up.

FROM RUST INTERMEDIATE (COURSE 2): Traits (Chapter 2), specifically
Rust's EXPLICIT impl Trait for Type requirement, contrasted against
Go's implicit structural interfaces. It reshaped how I think about API
design generally: making a type's capabilities a deliberate, visible
declaration rather than an accidental byproduct of matching method
names makes intent explicit in the code itself, not just in
documentation or convention.

FROM RUST ADVANCED (COURSE 3): The precise definition of "zero-cost
abstraction" (Chapter 5) — "what you don't use, you don't pay for;
what you do use, you couldn't hand-code any better." This gave me a
genuinely useful LENS for evaluating any abstraction in any language,
not just Rust: does this convenience actually cost something at
runtime, and if so, is that cost being paid consciously or hidden from
me? That question is worth asking regardless of which language I'm
actually writing in.