<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: adrianvi</title><link>https://news.ycombinator.com/user?id=adrianvi</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 18 Sep 2026 15:52:18 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=adrianvi" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by adrianvi in "This PCB is brought to you by Fable 5"]]></title><description><![CDATA[
<p>There's eebench, but maybe it's not exactly what you were thinking</p>
]]></description><pubDate>Thu, 17 Sep 2026 08:34:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=49737967</link><dc:creator>adrianvi</dc:creator><comments>https://news.ycombinator.com/item?id=49737967</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49737967</guid></item><item><title><![CDATA[New comment by adrianvi in "Show HN: Copperhead – Cursor for circuit boards"]]></title><description><![CDATA[
<p>> That is a leap in logic<p>It is not, it doesn't matter if a brain's neurons or a prediction algorithm managed to get the solution if it has done so in a (sort of) reliable way.<p><a href="https://en.wikipedia.org/wiki/Duck_test" rel="nofollow">https://en.wikipedia.org/wiki/Duck_test</a><p>Errors are made by both machines and humans, so that's not a differenting factor.<p>What is clear is that the human element will be more valued on art as time goes on.</p>
]]></description><pubDate>Wed, 09 Sep 2026 19:30:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=49632783</link><dc:creator>adrianvi</dc:creator><comments>https://news.ycombinator.com/item?id=49632783</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49632783</guid></item><item><title><![CDATA[New comment by adrianvi in "Show HN: Copperhead – Cursor for circuit boards"]]></title><description><![CDATA[
<p>Yes, the optimal solution won't be achievable, it will burn lots of compute and we need better simulations so that less errors are made (and will be made).<p>Still, if LLMs are capable of writing working code, art and solving math problems, they qre definitely capable of doing suboptimal routing (with some algorithmic aid)</p>
]]></description><pubDate>Wed, 09 Sep 2026 14:06:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=49626848</link><dc:creator>adrianvi</dc:creator><comments>https://news.ycombinator.com/item?id=49626848</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49626848</guid></item><item><title><![CDATA[New comment by adrianvi in "Show HN: Copperhead – Cursor for circuit boards"]]></title><description><![CDATA[
<p>I do think that slightly smarter LLMs and a good (although not perfect) autorouting algorithm could solve 99% of hobbyist's projects and simple industry boards, due to the repetition of those patterns in real life.<p>The LLM would learn the heiristics (example: data lines first, power lines later, etc.) and would request the autorouter to do that routing, then take the image output and request a different part (depth-first). If later no routing is posible with that configuration, after some retries it could try another way.<p>It wouldn't solve complex boards, and engineers are always needed for short comings (and even if not, for research), but I wouldn't say this is something different than poetry, music or pixel art, LLMs can imitate although most of the times in a uncanny way.</p>
]]></description><pubDate>Tue, 08 Sep 2026 21:08:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=49617076</link><dc:creator>adrianvi</dc:creator><comments>https://news.ycombinator.com/item?id=49617076</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49617076</guid></item><item><title><![CDATA[New comment by adrianvi in "Advancing the price-performance frontier with GPT‑5.6"]]></title><description><![CDATA[
<p>I can't speak for all cases, but the AI space is seeing improvements month by month, so it is beneficial to wait until it settles (a model becomes the standard in intelligence/price) before designing and mass producing an "LLM ASIC" of said model.<p>The big AI labs won't do that unless they are forced to, as they want you to spend more money on the big, expensive, frontier models (so they can live up to their valuation), so it's more likely that you will see this on smaller open weights models.</p>
]]></description><pubDate>Fri, 31 Jul 2026 08:38:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=49120535</link><dc:creator>adrianvi</dc:creator><comments>https://news.ycombinator.com/item?id=49120535</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49120535</guid></item><item><title><![CDATA[GitHub Copilot App]]></title><description><![CDATA[
<p>Article URL: <a href="https://github.com/features/ai/github-app">https://github.com/features/ai/github-app</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48596902">https://news.ycombinator.com/item?id=48596902</a></p>
<p>Points: 3</p>
<p># Comments: 0</p>
]]></description><pubDate>Fri, 19 Jun 2026 10:14:47 +0000</pubDate><link>https://github.com/features/ai/github-app</link><dc:creator>adrianvi</dc:creator><comments>https://news.ycombinator.com/item?id=48596902</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48596902</guid></item><item><title><![CDATA[New comment by adrianvi in "Claude Fable 5"]]></title><description><![CDATA[
<p>Important to note that both OpenAI and Anthropic do not allow the subsidized monthly subscriptions for enterprises.<p>Companies have to pay monthly for the harness app (codex, claude code) and the tokens are priced separately based on standard API pricing.</p>
]]></description><pubDate>Wed, 10 Jun 2026 10:02:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=48473981</link><dc:creator>adrianvi</dc:creator><comments>https://news.ycombinator.com/item?id=48473981</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48473981</guid></item><item><title><![CDATA[New comment by adrianvi in "GitHub removed the old copilot multipliers on a pricing page"]]></title><description><![CDATA[
<p>I'm not sure if your estimate is right. These summer months you will get 7000 AI credits (4000 from september, iirc). Each AI credit is 1 cent. Meaning, 100 AI credits = 1 $.<p>Then they have a price table that is the official public API prices for the models, but converted to their AI credits.<p>Currently, I'm averaging 15 credits (0.15 $) per request for some QnA questions with claude sonnet 4.6. It should be similar with gpt 5.4 (same output token price, similar input token price).<p>I think with the current pricing you can do light work with normal models (10-20 code completions/day), but vibe coding, heavy usage or using bigger models is not viable anymore.<p>It's hard to measure since I did not average my token expenditure per day.</p>
]]></description><pubDate>Mon, 01 Jun 2026 13:34:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=48356687</link><dc:creator>adrianvi</dc:creator><comments>https://news.ycombinator.com/item?id=48356687</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48356687</guid></item><item><title><![CDATA[New comment by adrianvi in "GitHub removed the old copilot multipliers on a pricing page"]]></title><description><![CDATA[
<p>So, the day arrived when some users (annual billing Pro and Pro+) would see their usage bar fill faster. I checked today and they modified it so you can't see the original page.<p>Unfortunately, nobody saved it on the wayback machine (I just did with today's page), but you can search "github copilot pricing multiplier" and still see on google images the cost increase x6 or x9 on some models.<p>I am on an Enterprise plan so it's different for me: I pay the subscription and I get credits, but the token pricing is essentially the same as the public API pricing.<p>I understand they needed to change it, but I don't like how they try to erase the old prices from the record.</p>
]]></description><pubDate>Mon, 01 Jun 2026 11:53:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=48355641</link><dc:creator>adrianvi</dc:creator><comments>https://news.ycombinator.com/item?id=48355641</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48355641</guid></item><item><title><![CDATA[GitHub removed the old copilot multipliers on a pricing page]]></title><description><![CDATA[
<p>Article URL: <a href="https://docs.github.com/en/copilot/reference/copilot-billing/request-based-billing-legacy/model-multipliers-for-annual-plans">https://docs.github.com/en/copilot/reference/copilot-billing/request-based-billing-legacy/model-multipliers-for-annual-plans</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48355640">https://news.ycombinator.com/item?id=48355640</a></p>
<p>Points: 4</p>
<p># Comments: 3</p>
]]></description><pubDate>Mon, 01 Jun 2026 11:53:32 +0000</pubDate><link>https://docs.github.com/en/copilot/reference/copilot-billing/request-based-billing-legacy/model-multipliers-for-annual-plans</link><dc:creator>adrianvi</dc:creator><comments>https://news.ycombinator.com/item?id=48355640</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48355640</guid></item><item><title><![CDATA[New comment by adrianvi in "Amazonbot is finally respecting robots.txt"]]></title><description><![CDATA[
<p>step 1: create the problem, step 2: sell the solution, step 3: profit</p>
]]></description><pubDate>Thu, 14 May 2026 23:22:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=48142539</link><dc:creator>adrianvi</dc:creator><comments>https://news.ycombinator.com/item?id=48142539</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48142539</guid></item><item><title><![CDATA[Show HN: Xecai, a minimal Python interface for LLM providers for RAG systems]]></title><description><![CDATA[
<p>A small python library to simplify LLM calls, database retrieval, reranking, conversation storage & embeddings when building RAG systems.<p>The library intentionally exposes only the functionality common across providers to avoid provider-specific parameters.<p>Libraries like LangChain provide many integrations but often rely on many abstractions, heavy use of kwargs, and complex code that can be difficult to customize.<p>Features:
- Sync and async APIs
- LLM calls: invoke and stream (temperature, reasoning level)
- Response metadata: answer, token usage, stop reason
- RAG documents: retrieval, reranking, embeddings
- Chat history: conversation store
- Common error handling across providers
- Providers: OpenAI, Anthropic, Google, AWS<p>Retry logic is left to the user (see README). Agent functionality is not supported yet.</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47419930">https://news.ycombinator.com/item?id=47419930</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Tue, 17 Mar 2026 23:48:43 +0000</pubDate><link>https://github.com/AdrianVispalia/xecai</link><dc:creator>adrianvi</dc:creator><comments>https://news.ycombinator.com/item?id=47419930</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47419930</guid></item></channel></rss>