Elias Kristensen

@tinylion250200

helll yeahh i am going to south harmon institute of technology wish me luck

Kongsvinger, Denmark Joined Jan 2026

Only @tinylion250200 can see everyone listening in. Visitors see a rotating sample.

Elias Kristensen echoed

Elias Kristensen

@tinylion250200 · Jan 12, 2026

Pauline Ford

@purplepeacock515188 · Jan 12, 2026 11:00 am

What’s your wild take on the rise of AI?

We have entered an era of AI doing \_almost\_ anything. From vibe coding, to image/video creation, new age of SEO, etc etc…
But what do you think AI is going to be able to do in the near future?
Just a few years ago we were laughing at people saying AI will be able to make apps, for example, or do complex mathematical calculation, and here we are haha
So what’s your “wild take” some people might laugh at, but it’s 100% achievable in the future?

91 likes 341 responses

Elias Kristensen

@tinylion250200 · Jan 12, 2026

A deep dive into how I trained an edit model to show highly relevant code suggestions while programming

This is def interesting for all SWEs who would like to know what goes behind the scenes in your code editor when you hit \`Tab\`. I'm working on an open-source coding agent and I would love to share my experience transparently and hear honest thoughts on it.
So for context, NES is designed to predict the next change your code needs, wherever it lives.
Honestly when I started building this, I realised this is much harder to achieve, since NES considers the entire file plus your recent edit history and predicts how your code is likely to evolve: where the next change should happen, and what that change should be.
Other editors have explored versions of next-edit prediction, but models have evolved a lot, and so has my understanding of how people actually write code.
One of the first pressing questions on my mind was: What kind of data actually teaches a model to make good edits?
It turned out that real developer intent is surprisingly hard to capture. As anyone who’s peeked at real commits knows, developer edits are messy. Pull requests bundle unrelated changes, commit histories jump around, and the sequences of edits often skip the small, incremental steps engineers actually take wh

20 likes 59 responses