▲ | cloverich 5 hours ago | |
Its puzzling to me that people are still debating productivity after its been good enough to quantify for a while now. My (merged) PR rate is up about 3x since i started using claude code over the course of a few months. I correspondingly feel more productive and that i have a good grasp of what it can and cannot do. I definitely see some people use it wrong. I also see it fail on some tasks id expect it to succeed at, such as abstracting a singleton in an ios app i am tinkering with, that suggests its not merely operator error but also that its skill is uneven dep on task, ecosystem, and language. I am curious for those that use it regularly, have you measured your actual commit rates? Thats ofc still not the same as measuring long term valuable output, but were still a ways off from being able to determime that imho. | ||
▲ | surgical_fire 3 hours ago | parent [-] | |
Measuring commit rates is a bad metric. It varies depending on the scope and complexity of what I am doing, and the size of individual commits. I can increase dramatically my number of commits by breaking up my commits in very small chunks. Typically when I am using AI I tend to reduce a lot the scope of a commit to make it more focused and easier to handle. |