zlacker

[return to "Measuring the impact of AI on experienced open-source developer productivity"]
1. noisy_+g5[view] [source] 2025-07-10 17:04:56
>>dheera+(OP)
It is 80/20 again - it gets you 80% of the way in 20% of the time and then you spend 80% of the time to get the rest of the 20% done. And since it always feels like it is almost there, sunk-cost fallacy comes into play as well and you just don't want to give up.

I think an approach that I tried recently is to use it as a friction remover instead of a solution provider. I do the programming but use it to remove pebbles such as that small bit of syntax I forgot, basically to keep up the velocity. However, I don't look at the wholesale code it offers. I think keeping the active thinking cap on results in code I actually understand while avoiding skill atrophy.

◧◩
2. RainyD+hp6[view] [source] 2025-07-13 04:05:45
>>noisy_+g5
More sinister is it then takes 80% of the credit.
[go to top]