The person driving is the one that learns the most in pair programming. In the scenario you've described, that would be Claude. LLMs don't learn.
Doesn't CC sometimes take twenty, thirty minutes to return an attempt? I wouldn't know, because I'm not rich and my employer has decided CC is too expensive, but I wonder what you would do with your pair programming partner while you wait.
The bosses would like to think we'd start working on something else, maybe start up a different Claude instance, but can you really change contexts and back before the first one is done? You AND your partner?
Nah, just go play air hockey until your boss realizes Claude is what they need, not you.
> Nah, just go play air hockey until your boss realizes Claude is what they need, not you.
This is a depressing comment.
I am apprehensive about the future of software development in this milieu. I've pumped out a ~15,000 line application heavily utilizing Claude Code over a few days that seems to work, but I don't know how much to trust it.
Certainly part of the fun of building something was missing during that project, but it was still fun to see something new come to life.
Maybe I should say I am cautiously optimistic but also concerned: I don't feel confident in the best ways to use these tools to build good software, and I'm not sure exactly what skills are useful in order to get them there.
and I thought the project was amazing, but I didn't like how the IDs were managed in yml, so I built this to make it more dynamic. I plan to add support for other smart home automations with it as well as more streaming services.
One of the features I really like about it is it makes it easy to print and cut out stickers to slap on the NFC cards for playing media.
My toddler loves it so far and one of his friend's has asked me to make one for him as well
I have criticisms of both tools like Claude Code and how applicable the 'pair programming' metaphor is here, but strong disagree that the person driving during pairing is the one who learns the most (or perhaps the implied "and the non-driver doesn't learn enough"). A good dynamic pairing session is equally valuable for both participants, even if there's a skill gap, and even if you're not alternating drivers as often as you should.
Doesn't CC sometimes take twenty, thirty minutes to return an attempt? I wouldn't know, because I'm not rich and my employer has decided CC is too expensive, but I wonder what you would do with your pair programming partner while you wait.
The bosses would like to think we'd start working on something else, maybe start up a different Claude instance, but can you really change contexts and back before the first one is done? You AND your partner?
Nah, just go play air hockey until your boss realizes Claude is what they need, not you.