Capturing Code Conversations
Concurrence between two blog posts.
I saw an interesting concurrence between a couple blog posts that came across my feed:
In both there's a desire to capture the conversations that produced code, alongside the code. For the Tigerbeetle dev, the desire is to reuse git and your usual text editor when doing code reviews, so that the code review comments, answers, and adjustments live in git as part of the history. For the Zed team, they think git is insufficient for capturing the conversations they're having, which I presume would include code review, such that they're going to build a new version control system. I wonder if the Zed team and the Tigerbeetle dev are feeling the same pain around trying to orchestrate communication within git's commit system.