Comment Iteration and exploration (Score 1) 57
I'd be interested to see stats on refactors and iteration. I no longer writing code for a living, but I do create production and utility scripts, and I find that - while I'm likely not any faster in the end, I am more likely to do the things that I "should" do, like refactor, or explore a tedious, but efficient way of accomplishing something. I wonder if it is the same elsewhere. Thus, while I'm not "faster", I feel like what I do put out is subjectively, and not infrequently objectively "better" than I would have produced without it. Perhaps that my "good enough" is often better than it would have been without the coding assistant?
I also might be a bit of an outlier, though. I usually find myself working in languages I don't know well. It may be just that I'm caught in that low level trap, and that AI is preventing me from investing (allowing me to not invest) the time doing the tedious stuff that creates the skill and insight that would skip most of those iterations, anyway.
The problem is, I have no idea how you would begin to compile stats like that. Much of that work would never be committed, so you would have to try to measure some kind of velocity of change in uncommitted code? That would be incredibly noisy, and so situational, that Im not sure you could learn anything from it. Suggestions?
I also might be a bit of an outlier, though. I usually find myself working in languages I don't know well. It may be just that I'm caught in that low level trap, and that AI is preventing me from investing (allowing me to not invest) the time doing the tedious stuff that creates the skill and insight that would skip most of those iterations, anyway.
The problem is, I have no idea how you would begin to compile stats like that. Much of that work would never be committed, so you would have to try to measure some kind of velocity of change in uncommitted code? That would be incredibly noisy, and so situational, that Im not sure you could learn anything from it. Suggestions?