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.
Definitely the most important skill to develop. Especially in our profession.
Interesting musing about what it takes for engineers to grow. Clearly there are a few paradoxes in there... that gives ideas to manage your career though.
An excellent essay about generative AI and art. Goes deep in the topic and explains very well how you can hardly make art with those tools. It's just too remote from how they work. I also particularly like the distinction between skill and intelligence. Indeed, we can make highly skilled but not intelligent systems using this technology.
Well, maybe our profession will make a leap forward. If instead of drinking the generative AI cool aid, if we really get a whole cohort of programmers better at critical skills (ethical issues, being skeptical of their tools, testing, software design and debugging) it'll clearly be some progress. Let's hope we don't fall in the obvious pitfalls.
I didn't know this book. It is written in a surprising style, but it's very much down to earth and to the point. For sure a good way to learn calculus.
Definitely this. Listen and write down issues before you start to complain. There might be reasons why things are as they are. Take the time to understand them and refine to have a better feedback.
Funny experiment. This shows what you can achieve in terms of teaching and learning during pair programming setups. Shadowing someone is a powerful approach.