You have conflated the joy of learning with the joy of building. I have been writing code since I was 6 years old and was left to my own devices with the vic-20, the manual, and BASIC instructions.
I have worked as a developer, security engineer, program manager and engineering manager through my career. Writing stuff to understand algorithms or hardware requires engaging with the math, science, and engineering of the software and hardware. Optimizing it or developing a novel algorithm requires deep comprehension.
Writing a service that shuffles a few things around between stuff on my home network so that I can build an automation to turn down the lights when I start playing a movie? Yeah, I could spend a day or two writing and testing it. Having done it a few times, the work of it is a bit of a chore, I'm not learning, just doing something. Using an Claude or some other agent to do that makes it go from 'do I want to spend my time off doing a chore?' to 'I can design this and have it built in an hour'.
Making the jump to using the tools in my day job has been a bitore challenging because as a security engineer I have seen some hairy stuff over the last two years as AI generated stuff wends it's way into production, but the tools and capabilities have expanded massively, and heck, my peers from Mozilla just published some awesome successes working with Anthropic to find new vulns :)
Don't let using tools take away the love of learning, use them to solve a problem and take care of the drudgery of building stuff.
I appreciate your thoughtful response, you might be right, maybe there's an element of getting over myself to stay in the race...
OMG that manual. VIC-20 was my first code experience. I look back and cannot understand how 7 year-old me was patient enough to make a jumping jack guy appear on screen. Joy of Coding? Hell, no. I wanted to see if I could make it work. (I did, and I had no clue how to save to tape)
Sounds like you had one at home? If so, I'm a bit jealous. But also, hello, brother/sister!