Talking with a lot of developers, I've noticed that everyone falls somewhere on a spectrum. On one end, you have developers who enjoy building a product. On the other end, you have developers who enjoy writing code.
Some people take a lot of pride in every single line they write. For them, writing code is like solving a puzzle. And for others, the code is just the medium. They care about expressing a product concept in the best way possible to a user. The code itself is incidental.
I fall very far towards the product end of the spectrum. Others I talk to fall very far on the craftsmanship end.
As the tools available to us get better and better, I think the people who take enjoyment primarily in the craftsmanship will have a harder and harder time finding satisfaction in this field. Not because they won't be needed, at least not yet, but because the thing they love doing is rapidly becoming something you supervise rather than perform. And I think that's going to be a rough adjustment for a lot of people.
The developer role is quickly becoming a technical PM role. Maybe it already has. You spend less time in an editor writing code and more time deciding what should be built and reviewing whether it was built correctly.
From the other direction, product managers are slowly approaching developers. They're picking up tools like Lovable for prototyping, building things that until recently would have required a developer or a UX designer. It's still early, but you can see where it's going. The next step is integration with design tools, and eventually with the autonomous coding tools themselves.
Both sides are moving towards each other. I'm not sure which is moving faster. But the gap is closing.
I don't think most people in either have internalized what that means yet.