Earlier quoted context omitted.
There's an option now in vscode to autosave every few seconds.
If you can't remember what you wrote a 'few seconds' ago then you have more problems than having to work in vscode!
Who needs Git when you have 1M context windows?
181–190 of 199 posts
Re: Who needs Git when you have 1M context windows?
#182>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-pow…
Re: Who needs Git when you have 1M context windows?
#183Earlier quoted context omitted.
> So maintaining old and new code for X amounts of time? No more than normal? Generally speaking, the author working on the feature is the only one who’s working on the new code, right? The whole team can see it, but generally isn’t using it. > If the code is being changed for another reason, or the new feature needs to update code used in many places, etc. It can be much more practical to just have a long-lived bran…
Medical industry, code that gets shipped has to be documented, even if it's not used. It doesn't mean we can't ship unused code, it just means it's generally a pretty bad idea to do it. Maybe the feature's requirement might change during implementation, or you wanted to do a minor version release but that dead code is for a feature that needs to go into a major version (because of regulations). > I can’t think of any…
Re: Who needs Git when you have 1M context windows?
#184Earlier quoted context omitted.
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!
Honest question - What DO you merge into shared branches? And, when your local needs to "catch up", don't you have to pull in those shared commits which conflict with your magit-wip commits because they touch the same code, but are different commit hashes?
I make "real" commits as I go and use a combination of `git commit --amend` and fixup commits (via git-autofixup) and `rebase --autosquash`. I periodically (daily, at least) fetch upstream and rebase on to my target branch. I find if you keep on top of things you won't end up with some enormous conflict that you can't remember how to resolve.
Re: Who needs Git when you have 1M context windows?
#185Earlier quoted context omitted.
Medical industry, code that gets shipped has to be documented, even if it's not used. It doesn't mean we can't ship unused code, it just means it's generally a pretty bad idea to do it. Maybe the feature's requirement might change during implementation, or you wanted to do a minor version release but that dead code is for a feature that needs to go into a major version (because of regulations). > I can’t think of any…
That document doesn’t say that, as far as I can tell. If you’re using a compiled language, the dead code likely gets removed anyway, it is never shipped.
Re: Who needs Git when you have 1M context windows?
#186Re: Who needs Git when you have 1M context windows?
#187Earlier quoted context omitted.
I like to mess around. Some of my best work comes out of messing around. The trick is making sure you mess around in a way that lets you easily hold onto whatever improvements you make. For me that means committing obsessively.
And branches are free.
Re: Who needs Git when you have 1M context windows?
#188I had a similar anecdotal experience a few weeks ago. I was working on a blog entry in a VS Code window and I hadn't yet saved it to disk. Then I accidentally hit the close-window keyboard shortcut... and it was gone. The "open last closed window" feature didn't recover it. On a hunch, I ran some rg searches in my VS Code Library feature on fragments of text I could remember from what I had written... and it turned o…
Looking back, writing interrupt service routines[1] for DOS as a self-taught teenager has been massively helpful. Primarly because it taught me to save every other word or so, in case my ISR caused the machine to freeze. [1]: https://wiki.osdev.org/Interrupt_Service_Routines
Re: Who needs Git when you have 1M context windows?
#189Earlier quoted context omitted.
Sounds like the Sun Ray thin client, built by Sun Microsystems in 1999. This was similar to the earlier graphical X terminals, which were reminiscent of mainframe terminals in the 1960s. It's the "wheel of reincarnation". https://en.wikipedia.org/wiki/Sun_Ray
Super cool! What I am wondering is if there is any interest in lets say having a smartphone that has this tech(see my other comment wishing for a open source phone somewhere on hackernews or the internet really) So lets say we can just have a really lightweight customizable smartphone which just connects over wifi or wire to something like raspberry pi or any really lightweight/small servers which you can carry aroun…
The bulkiness of having a powerbank + rpi with you could get a little challenging to deal with