I suppose I see the split a little bit differently. To me it's more that one camp of developers can still get a hit of satisfaction as if they built something themselves even if it was entirely generated by AI.
Would they get the same satisfaction from cloning a public repo? Probably not. It's too clear to their brain that they didn't have anything to do with it. What about building the project with cmake? That requires more effort, yes, but the underlying process is still very obviously something that someone else architected, and so the feeling of satisfaction remains elusive.
AI, however, adds a layer of obfuscation. For some, that's enough to mask the underlying process and make it feel as if they're still wielding a tool. For others, not so much.
I don't follow your analogy at all. Suppose I want to build an application with xyz features. My research yields that there are no such applications that include xyz features. However, there are plenty of applications that might have x feature, y feature or z feature, or a combination of two, but not all three.
If there are no such applications, I don't have a choice but to write it myself. This could take some time, especially if an MVP is all I'm interested in. LLMs are a novel tool in building an MVP. If time is a constraint, I can use an LLM, which should excel since xyz features are in its training set.
I suppose your analogy follows for developers who write applications that support abc features even though there are already applications out there that support abc features. Yes, I don't think that is very interesting. Your umpteenth clone of Snake is not interesting.