Ask HN: What are you doing during inference?
The article discusses the challenges of using AI agents for programming tasks. It emphasizes the importance of closely monitoring the work of these agents to avoid mistakes and hallucinations. The author suggests implementing proper development practices and testing to improve the reliability of agent outputs.
- ▪Using multiple agents simultaneously can lead to confusion and inefficiency.
- ▪Relying solely on AI agents is risky due to their potential for errors.
- ▪Implementing development practices like Test-Driven Development (TDD) can enhance the reliability of agent outputs.
2 outlets in our directory ran this story, first to last over 18 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ What are you doing with your old cases? — Reddit
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=47944917 |
| Publication time | Wed, 29 Apr 2026 06:45:56 +0000 |
| Retrieval time | 2026-04-29T07:10:31.876Z |
| Last seen | 2026-04-29T07:10:31.876Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | cuebYraHrkj1 · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
> If you’re using agents to program, what are you doing while they work?If I am using agents I try to do something that is closely related to the task they are on. Otherwise I am just context switching once they are done and I want to review the work, which makes it difficult to focus on that task.I also don't try to run too many agents at the same time as that is just madness. That's just herding cats at that point.> As a side note, having Codex review Claude’s work (or vice-versa) throws up so many show-stopper issues (even with plan, revise, implement, review loops), I feel like you’d have to be nuts to just have a bunch of agents YOLOing itSolely relying on agents is bad regardless. It certainly is the easy route and our brains are wired to take the easy/lazy approach.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.