Live data from Hacker News

Viewing profile — afshinmeh

afshinmeh

HN member
Joined
Thu, Jan 31, 2013, 12:02 PM UTC
HN karma
4,379
Public activity
807 items

About afshinmeh

afshin.io

Recent public activity

  1. story
  2. comment
    Comment #48344275

    Genuinely wondering though: is the problem that the patch was vibe coded, or is that no one reviewed the changes?

  3. comment
    Comment #48332690

    what does "LLM-native code understanding" mean in this context?

  4. story
  5. story
  6. comment
    Comment #48045867

    I love SQLite and thanks for sharing it but there should be a "(2018)" at the end in the title: > As of this writing (2018-05-29) the only other recommended storage formats for dat…

  7. comment
    Comment #48038449

    That's exactly how I tried to address that problem with https://github.com/afshinm/zerobox -- you control what network access (e.g. `--deny-net *.amazonaws.com`) your agent has and…

  8. comment
    Comment #48013559

    I'm mainly looking at Rust based projects and haven't been able to find something to use out of the box, without hacky RPC/Shell execs. Curious if you have any suggestions?

  9. comment
    Comment #48011066

    Sort of. My thinking is that the input to define the workflow should be anything you prefer to use (TS, Go, YAML, etc.) and the orchestrator's job is to model that and execute the …

  10. comment
    Comment #48010592

    Yeah, that makes sense. I looked at a few workflow orchestrators and I'm building something that I will release soon, but my thinking is that the "workflow engine" should be an abs…

  11. comment
    Comment #48010186

    Curious, what format would you prefer to use to represent a workflow instead of YAML?

  12. comment
    Comment #48010108

    https://github.com/vivekg13186/Daisy-DAG/blob/main/backend/s...

  13. comment
    Comment #47993733

    I wonder though, what about cases where you have multiple agents or LLM backends and the credentials is shared between all of them?

  14. comment
    Comment #47993677

    Agreed and it's a pattern that OpenAI suggested a few days ago, too [1]. I also built a cross platform process level sandboxing that uses parts of OpenAI Codex for the same purpose…

  15. comment
    Comment #47989763

    Vibe coding aside [1], it's very interesting software projects these days don't really care about adding a single test [2]. [1]: https://github.com/withastro/flue/blob/8fdf8e0e9df5…

  16. story
  17. comment
    Comment #47923203

    > It solves the problem the originating user asked it to Interesting. And is there a mechanism to go back and "fix" the tools after they are published? What happens if the tool dec…

  18. comment
    Comment #47922888

    > how do we avoid burning tokens solving the same problems over again Letting the LLM write half baked tools is the recipe for burning more tokens. > There's a wiki the LLM searche…

  19. comment
    Comment #47917891

    https://github.com/mozilla/standards-positions/issues/1067

  20. comment
    Comment #47911934

    It's actually interesting to me that the author is surprised the agent could make an API call and one of those API calls could be deleting the production database. It's a sad story…

  21. comment
    Comment #47771518

    I have been struggling with the same issue but help me understand this: > The lack of predictable output/outcomes How does that actually show up in practice for you? Asking because…

  22. story
  23. story
  24. comment
    Comment #47624122

    I'm adding snapshotting as well https://github.com/afshinm/zerobox/pull/21 Then you can run: ``` zerobox --snapshot -- sh -c 'echo "abc" > a' ``` and also `zerobox snapshot list/di…

  25. story