Live data from Hacker News

Viewing profile — jasendo

jasendo

HN member
Joined
Tue, Jan 20, 2026, 8:47 PM UTC
HN karma
2
Public activity
15 items

About jasendo

No profile information was provided.

Recent public activity

  1. comment
    Comment #47810010

    Looks great! Haven't found anything that's abstracted this much of the agent building process out before.

  2. comment
    Comment #46918227

    This looks awesome! Excited to see what happens

  3. comment
    Comment #46904140

    "Each conversation is writing an invisible roadmap you need to materialize". 100%. Most teams treat observability as a checkbox, not a product feedback loop.

  4. comment
    Comment #46890887

    This is actually insane. How do agents secure funding, and do sales, and market, and hear customer feedback and actually accomodate for it?

  5. comment
    Comment #46876086

    Interesting take on building your own orchestration layer. What's the core advantage you're seeing with Adama over existing frameworks? Curious if you've hit any walls with reliabi…

  6. comment
    Comment #46862090

    Really like the framing of "Time to Accountability" as the bottleneck. Curious how you think about this for the orchestration layer specifically. A lot of agent frameworks give you…

  7. comment
    Comment #46829396

    Cost attribution gets even worse when you factor in the bad decisions. Retries, abandoned tool calls, and cascading failures that still hit your bill but never show up in traces.

  8. comment
    Comment #46815919

    The 'you can review code you can no longer write' line is so real. That's the gap that sneaks up on you. Easy to miss until you're three layers deep in something you merged last we…

  9. comment
    Comment #46801850

    Context compression is necessary but it's treating symptoms, not the disease. The core issue is that most agent architectures bolt long-horizon reasoning onto models that weren't d…

  10. comment
    Comment #46784117

    Nice framework. Makes me wonder if the future is better external memory, or models that just handle context natively without the retrieval layer.

  11. comment
    Comment #46770715

    Interesting approach. Curious how you think about the tradeoff between external memory systems vs. models that manage their own context natively. It feels like the industry is spli…

  12. comment
    Comment #46733744

    Solid survey. The breakdown of in-context vs post-training reasoning is a helpful lens. Curious to see how the "long-horizon interaction" challenges they flag get addressed in prac…

  13. comment
    Comment #46719849

    Interesting approach. Progressive disclosure helps with token limits, but I'm curious how you handle state across multi-step tasks where Layer 2/3 context from an earlier step beco…

  14. comment
    Comment #46706171

    The sub-agent context isolation tradeoff is real. We've been experimenting with pushing context management into the runtime itself, with the model deciding what to keep, what to pr…

  15. comment
    Comment #46697657

    We've been working on a similar problem, but went the route of pushing this into the model and runtime layer instead of the orchestration layer. Less scaffolding, more baked into h…