That's a valid take. I think there's substance to that claim. Maybe what I've been struggling with lately is how blurry the lines seem to be. When am I building on top of something, and when am I claiming credit I don't deserve?
Along these lines, an interesting category of work is when I have an LLM do something I could do myself. I totally understand the code, I instruct it all the way, I have it redo things, revise, rejig, etc... But I don't actually write any code. How responsible am I for any of that?
At work there are a ton of small scripts I use for piping data around ad-hoc, and this is often how I do it. Claude can make dumb pipes really well and remarkably quickly with reasonably clear specs given to it. I compose all kinds of specs, reports, plans, etc. using this workflow. And I find myself wondering... How much of this is me? How much credit do I deserve? The code is gone, the outputs remain, and I can't quite tell how responsible I am for the end product. It's a strange experience.
To me it's about effort more than anything. If you're sharing your work with others, people want to see things in which the author put effort into. Likewise, if I put effort into an endeavour I can feel good about the result.
Along these lines, an interesting category of work is when I have an LLM do something I could do myself. I totally understand the code, I instruct it all the way, I have it redo things, revise, rejig, etc... But I don't actually write any code. How responsible am I for any of that?
At work there are a ton of small scripts I use for piping data around ad-hoc, and this is often how I do it. Claude can make dumb pipes really well and remarkably quickly with reasonably clear specs given to it. I compose all kinds of specs, reports, plans, etc. using this workflow. And I find myself wondering... How much of this is me? How much credit do I deserve? The code is gone, the outputs remain, and I can't quite tell how responsible I am for the end product. It's a strange experience.