<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: 0xfurai</title><link>https://news.ycombinator.com/user?id=0xfurai</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 25 May 2026 18:36:02 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=0xfurai" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by 0xfurai in "Migrating from Go to Rust"]]></title><description><![CDATA[
<p>The "when to enforce it" framing is what sticks with me. Go and Rust agree on safety, concurrency, simple deployment, but Go says "catch it in review" and Rust says "catch it before it compiles." The right answer depends entirely on how expensive a production incident is for you vs. how expensive slower iteration is.</p>
]]></description><pubDate>Sun, 24 May 2026 21:32:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=48261202</link><dc:creator>0xfurai</dc:creator><comments>https://news.ycombinator.com/item?id=48261202</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48261202</guid></item><item><title><![CDATA[Show HN: Telegram bot that notifies you when your GitHub repo gets a new star]]></title><description><![CDATA[
<p>I built a small side project: Telegram GitHub Stars Bot. @gh_stars_bot
It’s a Telegram bot that pings you in real time when someone stars your repo on GitHub.<p>Why?<p>GitHub stars are one of the simplest signals of interest/traction, but unless you’re constantly refreshing your repo page, you miss the dopamine hit . This bot solves that by dropping the notification straight into Telegram.<p>What it does
- Tracks new stars on any public repo
- Sends real-time Telegram notifications
- Lets you subscribe to multiple repos per chat
- Shows bot/repo stats
- Respects GitHub API rate limits and supports access control<p>Repo<p><a href="https://github.com/0xfurai/gh-telegram-stars-bot" rel="nofollow">https://github.com/0xfurai/gh-telegram-stars-bot</a></p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=45414378">https://news.ycombinator.com/item?id=45414378</a></p>
<p>Points: 2</p>
<p># Comments: 1</p>
]]></description><pubDate>Mon, 29 Sep 2025 14:36:46 +0000</pubDate><link>https://github.com/0xfurai/gh-telegram-stars-bot</link><dc:creator>0xfurai</dc:creator><comments>https://news.ycombinator.com/item?id=45414378</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45414378</guid></item><item><title><![CDATA[Show HN: Claude Code Subagents – 100 domain-expert helpers for dev workflows]]></title><description><![CDATA[
<p>I built a collection of 100+ specialized subagents for Claude Code that act like on-call experts (Python, React, Postgres, Docker, Stripe, Kafka, Prometheus, etc.). They can be auto-invoked by context or explicitly called (“use the postgres-expert to design indexes”), and each carries a focused system prompt + quality checklist. The runner picks a Claude model per task to balance speed/cost.<p>- Covers languages, frameworks, DBs/ORMs, DevOps, testing, ML, observability, auth, payments, messaging, and more.
- Zero server: they’re just files in ~/.claude/agents/.
- MIT-licensed and contributions welcome.<p>I’d love feedback on missing domains, rough edges in prompts, and real-world cases where this helped (or failed). Thanks!</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=45066110">https://news.ycombinator.com/item?id=45066110</a></p>
<p>Points: 2</p>
<p># Comments: 1</p>
]]></description><pubDate>Fri, 29 Aug 2025 16:23:57 +0000</pubDate><link>https://github.com/0xfurai/claude-code-subagents</link><dc:creator>0xfurai</dc:creator><comments>https://news.ycombinator.com/item?id=45066110</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45066110</guid></item></channel></rss>