It's a very good idea to help C++ developers pickup Rust.

For studying it makes sense. But don't shun other's work away only because of trust or ego issues.

This is a good rant, I liked it. Lots of very good points in there of course. Again: the area where it's useful is very narrow. I also nails down the consequences of a profession going full in with those tools.

Somehow not surprising... There's an area where it works OK. That said, I think we don't have the right UX to exploit it safely and productively. The right practices still need to be found. This isn't helped by all the hype and crazy announcements.

This is I think the most worrying consequences of this current hype. What happens when you get a whole generation which didn't learn anything related to their culture? Is Idiocracy the next step? How close are we?
At least, it will have made very obvious the problems with how our education system evolved the past twenty years (if not more).

Quite some good advice in here. I like being around people who proactively communicate, mind the quality of the communication and look for new things to work on. Who wouldn't?

Or why it's important to deeply understand what you do and what you use. Cranking features and throwing code to the wall until it sticks will never lead to good engineering. Even if it's abstractions all the way, it's for convenience but don't treat them as black boxes.
Interestingly this article draws a parallel with organizations too. Isn't having very siloed teams the same as treating abstractions as black boxes?
Quite some food for thought here.

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.