why rust changed the way i think

i picked up rust because everyone said it was hard. i wanted to know if that was true or if it was just gatekeeping. turns out it's both.

the borrow checker is annoying until the moment it isn't. there's a specific day - i remember mine - where you stop fighting it and start thinking in its terms. your mental model shifts. you start seeing ownership in other languages too, even when they don't surface it.

what surprised me most wasn't the performance. it was the clarity. rust forces you to answer questions that other languages let you defer. who owns this? for how long? what happens when it goes away? these are good questions. in python or javascript, you can pretend they don't exist. in rust you cannot.

i think that's the real lesson. not memory safety as a feature, but honesty as a discipline. the type system isn't a cage. it's a mirror.

i still write python. i still write typescript. but i read both differently now. i see the deferred decisions, the implicit assumptions, the places where something could go wrong and nobody made you think about it. rust made me a more suspicious reader of code.