Good advice on how to learn Rust. I recommend quite some of it.

I wonder how much the focus on Python biased that study... Still, maybe we've been wrong at so much emphasis on math skills for computer science and computer engineering curricula.

The metaphors are... funny. But still I think there's good lesson in there. If you use generative AI tools for development purposes, don't loose sight of the struggle needed to learn and improve. Otherwise you won't be able to properly drive those tools after a while.

Very nice praise to an underrated and underpaid job. Can we have more librarians please?

This is a good list of skills and behaviour to develop if you want to get better at our craft.

There's some truth to this. It's easier to market yourself as a specialist rather than a generalist... This doesn't make it easy.

Even if you use LLMs, make sure you don't depend on them in your workflows. Friction can indeed have value. Also if you're a junior you should probably seldom use them, build your skill and knowledge first... otherwise you'll forever be a beginner and that will bite you hard.

I like this attitude obviously... Go out and teach! Share what you learn!

It's indeed not easy to go from individual contributions, to team level leadership, to organisation level leadership. Many things need to be learned or relearned at each step.

Definitely this. It's important for an organization to create knowledge... and this requires both people willing to learn and to teach.

I'm not sure I would phrase it like this but there's quite some truth to it. It's important to figure out what we take for granted and to open the black boxes. This is where one finds mastery.

This is an interesting way to frame the problem. We can't rely too much on LLMs for computer science problems without loosing important skills and hindering learning. This is to be kept in mind.

Again it's definitely not useful for everyone... it might even be dangerous for learning.

Definitely a good list of lessons to learn when you're a junior developer.

This will definitely push even more conservatism around the existing platforms. More articles mean more training data... The underdogs will then suffer.

OK, this is advertisement to their PSL workshops. That being said the quote from Hoverstadt is important, this and the feedback of one of their attendees: "I can honestly say I learned at least as much from other participants". This is exactly what I'm trying to foster when I design learning experiences.

Not a huge fan of the writing style and the pokemon metaphor. That said, seeing your growth as an engineer based on circles is spot on.

Interesting exploration on the difficulties to switch a team to XP. I'm not fully aligned with some of the fine details pointed there... That said there is a core truth that "XP is about social change" so if you mandate it as a managerial decision it can't be XP anymore.

It tries hard at not being a "get off my lawn" post. It clearly points some kind of disconnects though. They're real. I guess it's to be expected with the breadth of our industry. There are so many abstractions piled onto each other that it's difficult to explore them all.

Good advice, no one should be a "React developer". Make sure you learn more fundamental skills.