Joseph T. Lyons

@JosephTLyons

I'm an Indiana University South Bend CSCI graduate. Fields of interest include GUI apps, multi-threaded apps, and contributing to open-source software.

Commit activity

16 commits in the last year

longest streak 3 days

446 / 1,000 XP554 XP to wheel

Fri, Nov 6

Thu, Oct 22

Tue, Oct 20

replying to @RaphaelFakhri
Well let the agent decide. When it comes along to edit some past code, it can literally look at any line, or character, and query the conversation that produced it. From there, it can make better decisions about how it edits your code because it’ll see all the past decisions and…
so every line keeps a pointer back to the conversation that wrote it. that's basically git blame for intent, which is the part that always goes missing. really like that

Mon, Oct 19

replying to @RaphaelFakhri
delta.dev rest upon a database we built called DeltaDB, that tracks and stores all conversation alongside the edits produced by either humans or agents. We’re trying to solve this context problem by making the capture part automatic.
automatic capture is the right call, nobody keeps notes up by hand for long. curious how you decide what's worth surfacing back later vs just stored? that's where mine gets noisy

That's @JosephTLyons's first reply.