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.

This can change from organization to organization. This post proposes a career ladder which will work in some contexts. What's clear is that it's all about scope and impact.

If you're just doing the minimum to deal with a task to "mark it done" you're probably not doing enough and missing out on learning opportunities.

Interesting tips to keep learning on the technical side of the job as you get more managerial responsibilities.

Another excellent piece from Kent Beck, he's right that the real differentiator in our profession is about digging deep on topics, seeing them through even if that's on the side. Curiosity is a key trait.

Indeed, those are fundamental traits to make sure you learn and make progress on your journey.

I very much agree with this. The relationship between developers and their frameworks is rarely healthy. I think the author misses an important advice though: read the code of your frameworks. When stuck invest sometime stepping into the frameworks with the debugger. Developers too often treat those as a black box.