If Claude writes the code, what makes me still a developer?

Architecting, specifying, verifying and validating are still important disciplines - those /can/ be in scope for a traditional ’developer’. You’re not irrelevant, but your role may be shifting a bit. Embrace the learning opportunities if they suit you, and if they don’t - well there’s likely something else you love to do that you could monetise…

This bit made me laugh:

> What I actually do all day

> (…)

> Research. I ask Claude to research the feature I need to build.

I’m not convinced “asking someone else to do the thing” is the same as “doing the thing”.