Viewing profile — bisonbear
bisonbear
HN member- Joined
- Wed, Sep 17, 2025, 2:36 PM UTC
- HN karma
- 53
- Public activity
- 79 items
- HN profile
- View on Hacker News ↗
About bisonbear
Recent public activity
-
comment
Comment #49223058
Experimentation makes a lot of sense as agents need to be pleasant to work with, and power users are a willing and able cohort to do that differentiation. Agent capability is only …
-
comment
Comment #49215350
This approach seems fundamentally predicated on being able to evaluate coding agents on your own code by having domain specific evals. With that knowledge, you can trust the routin…
-
comment
Comment #49172400
This is the right direction (Anthropic removing 80% of the system prompt https://claude.com/blog/the-new-rules-of-context-engineering... ) However what I wonder how we make these d…
-
comment
Comment #49171367
Thanks for the comment - I’ve actually been working on something to generate evals from private repos, as I 100% agree that public benchmarks are either contaminated (as OpenAI fou…
-
comment
Comment #49170298
I’ve been thinking about how we practically implement this at an organizational layer for large codebases. There’s clearly alpha to be had in optimizing AGENTS.md / skills / tools …
- story
-
comment
Comment #49043549
Also working on a product to build tasks from your own work for testing coding agents. Main thing I would offer is to look carefully at the agent trajectories - they love to figure…
-
comment
Comment #49030780
To me, this comes down to verifiability. How do we measure the quality of what an agent is doing on our codebase rather than simply measuring task accomplishment? > Verifying quali…
- story
-
comment
Comment #48827502
It depends on what you're measuring. I agree that model resourcefulness is useful, but if you're trying to simulate real user sessions, then Claude looking at upstream Git and fetc…
-
comment
Comment #48822868
as a tip - models will always find a way to cheat, you will probably need to impose some restrictions on what they do / are able to access in the sandbox environment see https://cu…
-
comment
Comment #48811785
I've actually been working on a solution for this problem! https://www.stet.sh/ At a high level, it - Mines tasks from your merged PRs/commits - Replays them in Docker containers w…
- story
-
comment
Comment #48455594
[flagged]
-
comment
Comment #48440352
beat saber is the only game I play on it and it's incredible
-
comment
Comment #48439707
The most salient point here is the societal acceptance of consuming slop - somehow we've gotten to a point where the majority of people are ok with mediocre art. I feel that this i…
-
comment
Comment #48419390
Agree - all of this is based on vibes (I also use TDD based on vibes FWIW). The only way to settle "does TDD / caveman / [insert random skill here] help" is to replay real PRs from…
- story
-
comment
Comment #48304354
> Seems like the progressive disclosure approach is the best for context efficiency; I wound up with a somewhat tight generic AGENTS.md, and the .cursor/rules individual files with…
-
comment
Comment #48304338
> we lack common tools to assess and compare This has been bothering me for a while - the entire dev community is running on vibes when talking about AI. We're operating in an old …
-
comment
Comment #48304320
Yes, agree that low n makes overclaiming a real risk with this sort of optimization loop. Low n results can be useful directionally but can't claim superiority without expanding th…
- story
- story
-
comment
Comment #48162108
Yeah, I've found that to be more effective. Going with the example "Always clarify intent before acting" > "Never act without getting intent first", seemingly because telling the a…
-
comment
Comment #48161536
My advice, from doing this myself and reading best practices, would be: - Keep it concise, use progressive disclosure / nested AGENTS.md for information expansion - Give agent the …