fhouser

19 ms·

1.
by fhouser 4mo ago
That's smart. Just the other day, I was thinking about how I would solve images/graphs/rich PDF stuff in a RAG system. Now I know more, thanks!
2.
by fhouser 6mo ago
Not exactly agents ignoring instructions, but I'm wondering if (selective) inclusion of LLM responses in a RAG stack might be suitable as a sort of long-term memory for "accepted" LLM contributions to code for example. This w
3.
Ask HN: Does piping LLM output into a RAG stack sound like a good idea?
2 points by fhouser 6mo ago|2 comments
4.
by fhouser 6mo ago
Yeah, I think that's the most important part in these new types of processes. Although it is tempting to just let an agent run with it for a while.
5.
by fhouser 6mo ago
The Hitchhiker's Guide to issue-tracking.
6.
by fhouser 6mo ago
Hot take: You should want to review your agents' output and progress.
7.
by fhouser 6mo ago
Thanks,that would be great.
8.
by fhouser 6mo ago
Opus 4.6 usually doesn't disappoint .. No double negative auth checks or race conditions to report on, but I can say that introducing new functionality and patterns mostly requires a few cycles before the "repeatable pattern"
9.
by fhouser 6mo ago
I recently shipped a "vibe-coded" project. You raise a good point: I hadn't considered the confidence gap. If it is true that LLM generated code produces more vulnerabilities in addition to there being more code overall, all
10.
by fhouser 6mo ago
Do you have domain knowledge for each category in-house? How did you put together so many specific calculators while maintaining correctness in each calculator's respective domain?
11.
Show HN: I built my first SaaS(lunatic-ai.com)
2 points by fhouser 6mo ago|0 comments
12.
by fhouser 6mo ago
aider.chat was my entry to agentic coding. OpenCode followed. Not looking back.
13.
Open standard for stable machine-readable facts for AI systems(groundingpage.com)
1 points by fhouser 6mo ago|0 comments