That depends on how you see it. I started off studying physics, but transitioned to CS. I found I was good at CS and loved tinkering, but the tinkering was always for the exploration of problems. That was always the point, not typing characters on a screen.

I admit, there is/was a certain element of enjoying the zone during development sessions. But mostly, it was the problems, not the tool.

I happened to become good at coding, and good at doing it in a corporate setting, so I adapted my habits, learned to write the best sort of code that keeps a production system solid and fast. But as I say, typing the characters was never really the point. Now a very fast assistant helps me type the characters. I guide it very closely. A lot of the time I have to correct it. Often if I know it is going to probably take a wrong direction I'll write the skeleton of the code I want, write the skeleton of the tests to prove it, and give it this as a "spec". This gets fantastic results.

I haven't lost my trade at all.