Live data from Hacker News

Who needs Git when you have 1M context windows?

alexmolas.com

101–110 of 199 posts

Re: Who needs Git when you have 1M context windows?

#101
post #38

Earlier quoted context omitted.

Commit even as a WIP before cleaning up! I don't really like polluting the commit history like that but with some interactive rebase it can be as if the WIP version never existed. (Side ask to people using Jujutsu: isn't it a use case where jujutsu shines?)

Git is a distributed version control system. You can do whatever you like locally and it won't "pollute" anything. Just don't merge that stuff into shared branches. I automatically commit every time my editor (emacs) saves a file and I've been doing this for years (magit-wip). Nobody should be afraid of doing this!

Exactly this. I can make a hundred commits that are one file per commit and I can later go back and

    git reset --soft HEAD~100 
and that will cleanly leave it as the hundred commits never happened.

Re: Who needs Git when you have 1M context windows?

#102

Earlier quoted context omitted.

Indiscriminate squashing sucks. Atomic commits are great if you want the git history to actually represent a logical changelog for a project, as opposed to a pointless literal keylog of what changes each developer made and when. It will help you if you need to bisect a regression later. It sucks if you bisect and find the change happened in some enormous incohesive commit. Squashing should be done carefully to reform…

> It sucks if you bisect and find the change happened in some enormous incohesive commit. But why are any PRs like this? Each PR should represent an atomic action against the codebase - implementing feature 1234, fixing bug 4567. The project's changelog should only be updated at the end of each PR. The fact that I went down the wrong path three times doesn't need to be documented.

yes, that would be ideal. especially in a world with infrastructure tied so closely to the application this standard cannot always be met for many teams.

Re: Who needs Git when you have 1M context windows?

#105

Most IDEs have Local History built-in to retrieve any version of a file, including untracked deleted files: VSCode Timeline, all JetBrains, Eclipse... Are people coding on notepad ?

Jetbrains local history, stacked clipboard, and recent locations (all searchable) are such a massive developer experience boost.

Re: Who needs Git when you have 1M context windows?

#106

"Who needs git when [..]" No matter how that sentence ends, I weep for our industry.

That's nothing. Compare https://xcancel.com/elonmusk/status/1956583412203958733 :

"The phone/computer will just become an edge node for AI, directly rendering pixels with no real operating system or apps in the traditional sense."

Re: Who needs Git when you have 1M context windows?

#107

I use Crystal which archives all my old claude code conversations, I've had to do this a few times when I threw out code that I later realized I needed.

Claude Code archives Claude Code conversations. "claude -r" - or go to equivalent of "~/.claude/sessions" or something like that

Re: Who needs Git when you have 1M context windows?

#108
>give me the exact original file of ml_ltv_training.py i passed you in the first message

I don't get this kind of thinking. Granted I'm not a specialist in ML. Is the temperature always 0 or something for these code-focused LLMs? How are people so sure the AI didn't flip a single 0 to 1 in the diff?

Even more so when applied to other more critical industries, like medicine. I talked to someone who developed an AI-powered patient report summary or something like that. How can the doctor trust that AI didn't alter or make something up? Even a tiny, single digit mistake can be quite literally fatal.

Re: Who needs Git when you have 1M context windows?

#109
Over the years, I've heard so many stories like these without happy ending - developers wasting days and sometimes even a week or two of work, because they do like to commit and use git often - that my long-time upheld practice is to pretty much always create feature/develop branches and commit as often as possible, often multiple times per hour.

Re: Who needs Git when you have 1M context windows?

#110

Earlier quoted context omitted.

> It sucks if you bisect and find the change happened in some enormous incohesive commit. But why are any PRs like this? Each PR should represent an atomic action against the codebase - implementing feature 1234, fixing bug 4567. The project's changelog should only be updated at the end of each PR. The fact that I went down the wrong path three times doesn't need to be documented.

yes, that would be ideal. especially in a world with infrastructure tied so closely to the application this standard cannot always be met for many teams.

Yeah "should" is often not reality, BUT I'm arguing that not squashing doesn't make things better.
Post reply on HN