Show HN: How long do I need to work at my salary before I can coast, or retire?
fire: a day-by-day FIRE simulator How many years at a big salary before you can coast, retire, or retire and never shrink your nest egg. It was built in a conversation with Claude (an AI): someone described what they wanted, and Claude wrote the code, the tests and the design log. Use it to explore ideas, and check anything important with a real human who does this for a living.
- ▪fire: a day-by-day FIRE simulator How many years at a big salary before you can coast, retire, or retire and never shrink your nest egg.
- ▪It was built in a conversation with Claude (an AI): someone described what they wanted, and Claude wrote the code, the tests and the design log.
- ▪Use it to explore ideas, and check anything important with a real human who does this for a living.
Hacker News (Front Page) files mainly under programming. We currently carry 2,077 of its stories. Top-voted stories on Hacker News.
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 | GitHub |
| Canonical URL | https://github.com/karmanyaahm/budget-tools/tree/main/fire |
| Publication time | Thu, 24 Sep 2026 03:53:54 +0000 |
| Retrieval time | 2026-09-24T04:30:12.540Z |
| Last seen | 2026-09-24T04:30:12.540Z |
| 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 | bPGFfq0FkxEK · 1 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
fire: a day-by-day FIRE simulator How many years at a big salary before you can coast, retire, or retire and never shrink your nest egg. Heads up: this is a vibe-coded FIRE tool. It was built in a conversation with Claude (an AI): someone described what they wanted, and Claude wrote the code, the tests and the design log. No financial professional has reviewed it. It is not financial advice. Use it to explore ideas, and check anything important with a real human who does this for a living. What is this? It answers one question: how long do I need to work at a high salary before I can stop, coast, or retire? To find out, it simulates your money day by day to age 112 in real (today's) dollars. Each day, wages arrive net of income tax, the day's expenses go out, and any surplus is invested.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.