What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether the approach also works for fields like hardware design beyond the demonstrated case.From this comment
- How this relates to an existing named auto-research project.From this comment
- Whether anyone has built a verifier for a business or project rather than code.From this comment
- What the actual hardware specifications are so the experiment can be replicated.From this comment
- Which point of a cited book the maker should pay attention to.From this comment
What they doubted or pushed back on our summary
- Argues the verifier idea is old news, citing verification advantage in chip markets decades ago.From this comment
- Notes that gains here mainly work around poor quality of the specific chip family used.From this comment
- Distinguishes optimizing something already working from making anything work at all.From this comment
What the maker answered our summary
13 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Replies that the verifier idea applies to any task with a good verifier, not just this project.From this comment
- Agrees the loop could extend well beyond chips, even to whole companies eventually.From this comment
- Admits being novel is hard and laughs at the tease about the idea being new.From this comment
- Says idea generation needs improvement and welcomes suggestions for adding variability.From this comment
What a builder can take from it: A builder should invest in a strong automatic scoring signal, since the loop only works as well as what measures it. our reading
The title, taken apart our calculation
This post got 241 points; the median for all 1442 posts is 112. In Open source projects (328 posts) the median is 103 points and 38 comments.
When it was posted our calculation
Tuesday at 17:00 UTC. Of 3,019 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 109 (3.6%) reached 50 points; on Tuesdays it was 2.8% of 8,995. The average over all hours is 2.9%. One post's time does not explain its result; the full table of hours is on the Show HN hub.
Check your title our calculation
Type the title you plan to post. It is compared with 1,442 Show HN posts that reached 50 or more points: its length, its shape, and how posts of that length and shape did. Nothing is sent anywhere.
Type a title above to see where it sits.
Draft my Show HN post
Paste your site address and get title options and a first comment for your own Show HN post, written from what your site says and checked against the numbers above. Nothing is posted for you.
Free to try and no account needed. FoxPlug is for people who ship several projects and keep stalling on telling anyone: it turns what you ship into posts you approve before anything goes out. See what each plan includes.
More Open source projects teardowns
Points, comments, titles and times are Hacker News's own numbers, read from the post itself, last updated Nov 2026. Summaries of what people said are ours, written in our own words, and each one links to the comment it came from. Percentages and medians marked "our calculation" are computed from the posts counted on the page: they describe what happened, not what will happen to your post. FoxPlug posts nothing for you. Plans and limits are on the pricing page. Questions: support.
After the launch post: a changelog your users read
A launch brings visitors once. FoxPlug turns what you ship afterwards into a public changelog and ready posts, so the next visitor finds something new.
Start your changelog See a SaaS changelog example
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Visual cards and walkthrough videos made from what you shipped
- Posts for X, LinkedIn and dev.to written from your changes
- Connect GitHub and the tools you build with