Hacker Newsnew | past | comments | ask | show | jobs | submit | samuell's commentslogin

Now do the combinations of them.

boom

Yeah, I think as a general direction we need to allow a useful collaboration with the agents on the issue board.

This is btw why Epiq was developed, to keep the board as code, git-backed, distributed (via an event log mechanism), and with the ability to replay the board, to see what agents actually did:

https://ljtn.github.io/epiq


How does this compare to Beads, if you don't mind me asking?

https://github.com/gastownhall/beads


I hope @jolaflow can chime in here eventually, but from a brief look, my impression, besides the fact that Epiq is based on git as opposed to beads where it is optional, is that Epiq seems to be much more optimized for interactive collaboration between the user and the agents.

The graph visualization in beads surely is a neat thing for showing things, but the replay feature in Epiq should provide a similar understanding of what happened.

But again, it seems to me Epiq is the tool that better allow the user to jump right in and collaborate with the agents on the board.

(Again, this is from a brief look, so I could be missing things).


thanks for sharing, going through your blog about cognitive debt.

Sorry, I might not have been clear, but the tool and blog is by @jolaflow (my brother) and I'm so far mostly involved as a reviewer and early adopter, but glad you like it. I might be biased, but I think the tool provides something really useful for agentic coding and hoping it can grow into a thriving open source project.

This looks very cool

Indeed. A google/brave search on that founder generated nada.

Pretty sure that OP ("jakobgreenfeld") is the "founder". That user's last four submissions have all been similar "finding" reports from a Claude-generated mystery research group website.

Yea. A google on that founder generated zero results.

The person you need to google is Jakob Greenfeld - who posted this and other AI spam sites to HN - chasing engagement or proving a point? I'm not sure what his end game is, but it doesn't look great (see his post history for other 'fake' research sites, all just registered, with v limited content.

One founder. Zero results. Honest truth. Verified, not inferred.

Let's not make this a Nordic conflict. We, the Nordic countries need to stay brothers and sisters with each other as we have done for centuries (not without sometimes serious squabbles, but still). Not even a European countries conflict. It is the EU as an institution that has started growing and reaching way beyond the will and welfare of the people.

In jest.

But it seems you didn't even read what I responded to? Not to mention Denmark spraying Skåne with poop for a long time. And Sweden did vote yes to these regulations.


I read it, but OK, I misunderstood.

I also stumbled upon this site, which on a first glance looks really thorough. Interested to hear if folks have comments on it though:

https://walkinglabs.github.io/learn-harness-engineering/en/


I have had a similar experience regarding tiling window managers. Been trying i3, but everything becomes just super complicated, and I learned I somehow actually appreciate having a feel for windows moving around, and having the freedom to open a small mini terminal above all the others for some quick tasks etc.

For me, XFCE (On Linux Mint currently) turned out to be the answer. Has configurable keyboard shortcuts for pretty much anything you need, like tiling to top/right/bottom/left, corners, moving or resizing windows etc.

To me, that is the best of both worlds - a normal window manager with keyboard shortcuts for tiling the windows when you want.


I love XFCE, but I switched to KDE as it supports Wayland (and I want to use WayDroid). KDE has a similar window + shortcut philosophy.


> Why not put issues alongside the codebase?

That's the idea of Epiq: https://ljtn.github.io/epiq/

> In my view, the main obstacle here is that without serious dedication, the user experience for humans would be a major downgrade. This isn’t insurmountable, but it would be a lot of work.

I think Epiq does a decent job of addressing this.

Take a look at the second animation on the page above. It even lets you "scrub" your way through the timeline to very quickly glance at what an agent (or junior developer) did to your code recently.


  "For with much wisdom comes much sorrow;
     the more knowledge, the more grief."
Ecclesiastes 1:18


I found it a bit curious that Mojo seems more readable, while at the same time less compact, than Rust.

At least according to my small experiment:

https://x.com/smllmp/status/2055602226240893043


Interesting, I found the Rust code _far_ more readable.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: