The work product is not the work.
Software is made between commits
31–40 of 230 posts
Re: Software is made between commits
#32> Before agents, it was easier to believe that the ceremony of trading comments on snapshots was an effective way to collaborate on software,
I’m highly skeptical of this claim. For any complicated feature, there’s always a design doc (or an RFC, or a wireframe) and that’s what people used for discussion. Discussion in a PR are mostly about whether to accept the code, reject the feature, or provide feedback about alternate implementations. It’s not for pair programming or directing design.
Collaborating together in a research lab (brainstorm session) is not the same as asking feedback for a journal article (PR). What is described in the article is pair programming with extra steps.
Re: Software is made between commits
#33I really don't like this. The code I write between commits is my thinking. I think by writing some code out, deleting it, writing again. The code I write that's shipped in commits is written for others to understand, and is a product of that writing for thinking process. I don't want my thoughts to be serialized, version controlled and publicly accessible. https://www.nature.com/articles/s44222-025-00323-4
Aren't you paid to think?
Re: Software is made between commits
#34I really don't like this. The code I write between commits is my thinking. I think by writing some code out, deleting it, writing again. The code I write that's shipped in commits is written for others to understand, and is a product of that writing for thinking process. I don't want my thoughts to be serialized, version controlled and publicly accessible. https://www.nature.com/articles/s44222-025-00323-4
The collaboration part I’m skeptical of but I get it, as it sounds like a feature made for business consumers
Re: Software is made between commits
#35so i think the thing that everyone building these git alternatives is missing is a multi-repo story - unless the expectation is that everyone is going to start operating out of monorepos i've settled on all of this context attached to issues in a project management system and referenced from commits it works just fine - its not like your agent cannot read your issue tracker
I came across the conclusion here since a change sometimes spans several repos, per-repo history optimizes the wrong target.
Re: Software is made between commits
#36I really don't like this. The code I write between commits is my thinking. I think by writing some code out, deleting it, writing again. The code I write that's shipped in commits is written for others to understand, and is a product of that writing for thinking process. I don't want my thoughts to be serialized, version controlled and publicly accessible. https://www.nature.com/articles/s44222-025-00323-4
Aren't you paid to think?
[deleted]
Re: Software is made between commits
#37I really don't like this. The code I write between commits is my thinking. I think by writing some code out, deleting it, writing again. The code I write that's shipped in commits is written for others to understand, and is a product of that writing for thinking process. I don't want my thoughts to be serialized, version controlled and publicly accessible. https://www.nature.com/articles/s44222-025-00323-4
Aren't you paid to think?
No I'm paid to write code.
Re: Software is made between commits
#38I really don't like this. The code I write between commits is my thinking. I think by writing some code out, deleting it, writing again. The code I write that's shipped in commits is written for others to understand, and is a product of that writing for thinking process. I don't want my thoughts to be serialized, version controlled and publicly accessible. https://www.nature.com/articles/s44222-025-00323-4
Aren't you paid to think?
[dead]
Re: Software is made between commits
#39Just a stream of thoughts: if git commits were a list of sequential primitive changes instead of diff snapshots, conflict resolution would be trivial in most cases.
Not without cons of course: commit byte size, public WIP work and leaked secrets/unwanted edits.
Re: Software is made between commits
#40[dead]