6 hours a week is low, unless its the average spread across industries. I think I spend more time in Claude Code via the CLI versus any other app I have on my laptop.
Like others said, the frustration is when it gets something so wrong you just think "wow, how'd you mess that up?" but when it gets it right its kind of nice. I also dont like that I basically tell Claude what to do, and then either go to busy work or waste time on the internet.
I kind of enjoy exploring black boxes, trying how different inputs are mapping to differences in outputs. It's kind of like hacking. The problem is, they keep altering the box.
It feels like Greek mythology should have some metaphor for "apparently simple structure that is so complex it leads anybody that studies it into madness". But I can't think of any name to put there.
The third sentence got to what my objection was going to be. It's fun trying to make the thing do what you want it to do! That's why many of us like computers. It's the randomness that sucks and makes the process unsatisfying.
Working with AI is trying to reduce the probability it'll pick undesirable paths. It's an exercise in trying to avoid what you DON'T want.
I suppose it's the same as asking someone else to take care of a feature and hoping they understand what you have in mind. The difference is that there's a lot of context that's shared between you and a human developer that is simply absent with AI.
I wonder how many hours of old stye non-overhead that is. And by overhead I mean mostly meetings. Then again maybe generating paperwork is included so that eats bit into it.
Like others said, the frustration is when it gets something so wrong you just think "wow, how'd you mess that up?" but when it gets it right its kind of nice. I also dont like that I basically tell Claude what to do, and then either go to busy work or waste time on the internet.