3 ms·

This is insane to me. Review your own code. Understand why you made the changes. And then clearly describe why you made them. If you can't do that yourself, I

This is insane to me. Review your own code. Understand why you made the changes. And then clearly describe why you made them. If you can't do that yourself, I think that's a huge gap in your own skills. Making something else do it means you don't internalize the changes that you made.

js2 1y ago
Your comment is not a fair interpretation of what I wrote. For the record, I write better and more detailed commit messages than almost anyone I know across a decades[^0] long career[^1,^2,^3,^4,^5]. But I'm not immune from making mistakes, and everyone can use an editor, or just runs out of mental energy. Unfortunately, I find it hard to get decent PR reviews from my colleagues at work. So yeah, I've started using Claude Code to help review my own commits. That doesn't mean I don't understand my changes or that I don't know why I made them. And CC is good at banging out a first draft of a commit message. It's also good at catching tiny logic errors that slip through tests and human review. Surprisingly good. You should try it. I have plenty of criticisms for CC too. I'm not sure it's actually saving me any time. I've spent the last two weeks working 10 hour days with it. For some things it shines. For other things, I would've been better off writing the code from scratch myself, something I've had to do maybe 40% of the time now. [^0]: https://seclists.org/bugtraq/1998/Jul/172 https://seclists.org/bugtraq/1998/Jul/172 [^1]: https://github.com/git/git/commit/441adf0ccf571a9fe15658fdfcd856d2aabc01cb https://github.com/git/git/commit/441adf0ccf571a9fe15658fdfc... [^2]: https://github.com/git/git/commit/cacfc09ba82bfc6b0e1c047247785d56a6054b2f https://github.com/git/git/commit/cacfc09ba82bfc6b0e1c047247... [^3]: https://github.com/fastlane/fastlane/pull/21644 https://github.com/fastlane/fastlane/pull/21644 [^4]: https://github.com/CocoaPods/Core/pull/741 https://github.com/CocoaPods/Core/pull/741 [^5]: None of the these are my best examples, just the ones I found quickly. Most of my commit messages are obviously locked away by my employer. Somewhere in the git history is a paragraphs long commit message from Jeff King (peff) explaining a one line diff. That's probably my favorite commit message of all time. But I also know that at work I've got a message somewhere explaining a single character diff.

js2 1y ago

Your comment is not a fair interpretation of what I wrote. For the record, I write better and more detailed commit messages than almost anyone I know across a decades[^0] long career[^1,^2,^3,^4,^5]. But I'm not immune from making mistakes, and everyone can use an editor, or just runs out of mental energy. Unfortunately, I find it hard to get decent PR reviews from my colleagues at work. So yeah, I've started using Claude Code to help review my own commits. That doesn't mean I don't understand my changes or that I don't know why I made them. And CC is good at banging out a first draft of a commit message. It's also good at catching tiny logic errors that slip through tests and human review. Surprisingly good. You should try it. I have plenty of criticisms for CC too. I'm not sure it's actually saving me any time. I've spent the last two weeks working 10 hour days with it. For some things it shines. For other things, I would've been better off writing the code from scratch myself, something I've had to do maybe 40% of the time now. [^0]: https://seclists.org/bugtraq/1998/Jul/172 https://seclists.org/bugtraq/1998/Jul/172 [^1]: https://github.com/git/git/commit/441adf0ccf571a9fe15658fdfcd856d2aabc01cb https://github.com/git/git/commit/441adf0ccf571a9fe15658fdfc... [^2]: https://github.com/git/git/commit/cacfc09ba82bfc6b0e1c047247785d56a6054b2f https://github.com/git/git/commit/cacfc09ba82bfc6b0e1c047247... [^3]: https://github.com/fastlane/fastlane/pull/21644 https://github.com/fastlane/fastlane/pull/21644 [^4]: https://github.com/CocoaPods/Core/pull/741 https://github.com/CocoaPods/Core/pull/741 [^5]: None of the these are my best examples, just the ones I found quickly. Most of my commit messages are obviously locked away by my employer. Somewhere in the git history is a paragraphs long commit message from Jeff King (peff) explaining a one line diff. That's probably my favorite commit message of all time. But I also know that at work I've got a message somewhere explaining a single character diff.