SCMandLLM.md · GitHub Skip to content Search Gists Search Gists Sign in Sign up You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert Instantly share code, notes, and snippets. gritzko / SCMandLLM.md Last active February 15, 2026 09:10 Show Gist options Download ZIP Star 0 ( 0 ) You must be signed in to star a gist Fork 0 ( 0 ) You must be signed in to fork a gist Embed Select an option Embed Embed this gist in your website. Share Copy sharable link for this gist. Clone via HTTPS Clone using the web URL. No results found Learn more about clone URLs Clone this repository at <script src="https://gist.github.com/gritzko/6e81b5391eacb585ae207f5e634db07e.js"></script> Save gritzko/6e81b5391eacb585ae207f5e634db07e to your computer and use it in GitHub Desktop. Embed Select an option Embed Embed this gist in your website. Share Copy sharable link for this gist. Clone via HTTPS Clone using the web URL. No results found Learn more about clone URLs Clone this repository at <script src="https://gist.github.com/gritzko/6e81b5391eacb585ae207f5e634db07e.js"></script> Save gritzko/6e81b5391eacb585ae207f5e634db07e to your computer and use it in GitHub Desktop. Download ZIP Raw SCMandLLM.md I. Challenges of revision control in the LLM era Software development is changing rapidly and the tool stack has yet to catch up. As we see, the value of IDEs diminishes as developers are less inclined to edit the code now. More and more of the work is browsing and talking to LLMs, less and less is coding and debugging. About 8 years ago I gave a talk at the internal JetBrains conference “Code is hypertext, IDE is a browser”. My points look even more relevant now: effective browsing of code and history is a prerequisite to effective understanding. Understanding underlies everything now. No understanding = no control, then a developer is like a rider who fell off a horse with his foot caught in the stirrup (you may search YouTube to understand what I mean). git is increasingly becoming a point of friction. LLMs have high throughput in regard to code edits. Sorting out the changes then takes disproportionate time and often repeats your previous work, if you actually read the diffs during the session, which I highly recommend. Even single-person development now becomes collaborative: at the very least, your collaborator is an LLM. In calm waters, running several agents is nothing special. Then I have an entire team, with all the merges and rebases (which we like to do beyond any measure). That is why I think it is the right time to look for git replacements, and that is why I am working on one. I definitely reject the “git compatible” approach despite the immense gravitation of the existing mass of git repos. jj to git is what subversion was to cvs . Wh
Source: Hacker News | Original Link