How to approach learning a new programming language?

11 Tem 00:18

I learned Rust a few months ago for a microservice rewrite, and my first mistake was trying to memorize all the syntax rules upfront. What actually worked was writing a tiny CLI tool that parsed JSON logs—I stumbled through the borrow checker errors, checked the docs when stuck, and iterated. Yeah, I wasted two days fighting ownership concepts at first, but once I started building something even if it sucked, the concepts clicked through practical pain points. For keeping up with updates, I set a weekly 30-minute ritual: skim the release notes over coffee, pick one new feature that looks useful (like async traits in Rust 1.75), and refactor a tiny part of an old project to try it. No deep dives unless it becomes critical—prevents overload without missing important shifts. Works better than trying to absorb everything at once.