kevinlu1248

Joined 3 years ago

Karma
137
Submissions
103
Member since
Mar 18
building next edit autocomplete for jetbrains
View on Hacker News

Recent submissions

Comment · 9 months ago
Ya definitely, that makes total sense. It feels to me that currently the labs have great researchers, who only care about making models perform better across raw intel and then they have incompetent applied AI engineers / FDE's who can only suggest using better prompting to remove bad habits to make agents more usable.
Comment · 9 months ago
We have an explanation here: https://blog.sweep.dev/posts/next-edit-jetbrains#next-edit-a...

But basically suggesting changes away from your cursor position

Comment · 9 months ago
It's a bit undertrained on C#, we'll continue improving on this!
Comment · 9 months ago
Also wish Fleet took off, not a fan of installing a new IDE for every separate repo that's in a different language
Comment · 9 months ago
I've done some testing before and many of the new Jetbrains internal plugins cause memory leaks which really lags down my IDE...
Comment · 9 months ago
Definitely agree here, have had so many cases where I would like ask Claude for XYZ, then ask for XYZ again but with a small change. Instead of abstracting out the common code it would just duplicate the code with the small change.
Comment · 9 months ago
We currently integrate with Jetbrains' PSI
Comment · 9 months ago
Honestly I think we can improve our training throughput drastically via a few more optimizations but we've been spending most of our time on model quality improvements instead.
Comment · 9 months ago
You can see that Qwen3 does worse than Qwen2.5 on our benchmark. Reason is it's never been pretrained for FIM / autocomplete.
Comment · 9 months ago
Not at the moment but we do host it for our Jetbrains plugin
Comment · 9 months ago
Yes, I've used it to write blog posts / large user-facing copy.
Comment · 9 months ago
Comment · 9 months ago
^ these were pretty much the main reasons.

The other one is that constrained decoding only works on CFGs (simpler grammars like JSON schemas) since only these ones can produce automatas which can be used for constrained decoding. Programming languages like Python and C++ aren't CFGs so it doesn't work.

Also constrained decoding generally worsens model quality since the model would be generating off-policy. So RL helps push corrected syntax back on-policy.

Comment · 9 months ago
Unfortunately, the main optimization (3x speedup) is using n-gram spec dec which doesn't run on CPUs. But I believe it works on Metal at least.
Comment · 9 months ago
Haha, we never trained it for chat but I would bet it works regardless.

Also that's crazy, M4 Mac?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton