> I reject the idea that programming is „just typing“, so we are very unlikely to understand each others.

I'm sorry if I gave the impression I think programming is just typing. For me "programming" is the whole activity of creating software with code, you can do programming without the literal action of typing.

> Writing the code and thinking about the exact logic you want to apply and all its implications are part of the same problem solving process in my mind.

That's really interesting perspective to me, as these two activities for me are two completely things, and "thinking about the exact logic" happens way before I actually write any code at all, sometimes weeks/months even.

> putting things together in code is a very satisfying and IMHO is the actual building part of the job.

I agree that it's satisfying, but I guess "putting things together in code" still for me is more about being able to mash two concepts together in an elegant way, and none of that actually requires actual typing still.

> LLMs move me away from the implementation, which is more a managerial role, something I personally have zero interest in.

This is also interesting, because it feels like LLMs give me the opportunity to do more implementation, and not get stuck in the minutia so much, but rather focus on how the design and architecture actually fits together. Refactoring no longer is "I want to but also I don't want to spend the time nor get stuck in more rabbit-holes", so being able to focus on architecture/design more feels like it lets me care more about the implementation than before.