akarshc

5 ms·

1.
by akarshc 5mo ago
I wrote this after building an AI gateway layer for ModelRiver to handle streaming responses, retries, and provider failover across LLM APIs. Phoenix supervision trees ended up being especially useful for isolating failures between model ca
2.
Ask HN: How are you testing LLM integrations in CI?
1 points by akarshc 7mo ago|0 comments
3.
by akarshc 8mo ago
I’ve worked on and shipped a few AI systems that reached real users. This post isn’t about models or prompts. It’s about the things that kept breaking once AI moved off the happy path: async jobs, retries, silent failures, provider outages,
4.
What breaks when you ship AI in production(akarshc.com)
2 points by akarshc 8mo ago|1 comments
5.
by akarshc 8mo ago
This is one of the harder problems, and there isn’t a perfect answer. The main thing we try to avoid is pretending mid-stream retries are the same as pre-request retries. Once a stream has started, we treat it as a sequence of events with c
6.
by akarshc 8mo ago
This was something we were careful about. The request and event models are intentionally close to what most providers already expose, rather than introducing a completely new abstraction. Teams usually integrate it incrementally in front of
7.
by akarshc 8mo ago
I’m one of the builders. Once AI requests moved beyond simple sync calls, we kept running into the same problems in production: retries hiding failures, async flows that were hard to reason about, frontend state drifting, and providers timi
8.
Sync vs. async vs. event-driven AI requests: what works in production(modelriver.com)
4 points by akarshc 8mo ago|10 comments
9.
by akarshc 8mo ago
Totally agree, that “what actually hit the wire?” view is critical once things go async. ModelRiver already has this covered via request logs. Every request captures the full lifecycle, the exact payload sent to the provider, streaming chun
10.
by akarshc 8mo ago
If streaming behavior is still product-specific and changing fast, this adds friction. It only pays off once failure handling stabilizes and starts repeating across the system.
11.
by akarshc 8mo ago
Queues work well before or after a request, but they’re awkward once a response is already streaming. This layer exists mainly to handle failures during a stream without spreading that logic across handlers, workers, and client code.
12.
by akarshc 8mo ago
While building AI features that rely on real-time streaming responses, I kept running into failures that were hard to reason about once things went async. Requests would partially stream, providers would throttle or fail mid-stream, and ret
13.
Show HN: a small API layer for real-time AI streaming, retries, and debugging(modelriver.com)
4 points by akarshc 8mo ago|7 comments
14.
Relearning Programming: My Process in the Modern Tech World(akarshc.com)
2 points by akarshc 11mo ago|1 comments
15.
by akarshc 11mo ago
In the age of AI, how I rewire my mind to pick up new programming languages.
16.
After Trying Everything, I Built My Own Focused Productivity Tool(hyperzoned.com)
3 points by akarshc 11mo ago|1 comments
17.
by akarshc 11mo ago
In 2025, productivity isn’t about doing more, it’s about doing what matters most. With too many tools claiming to make life easier, project management often becomes a task by itself.
18.
by akarshc 11mo ago
That’s true. As the app grows, having many pages can become difficult to manage, especially with JS backends.
19.
by akarshc 11mo ago
That’s fair, Rails + Hotwire is excellent for building fast MVPs. What really set Phoenix apart for me was the built-in real-time layer (via channels), the BEAM’s fault tolerance and concurrency, and how effortlessly it scales with backgrou
20.
by akarshc 11mo ago
Absolutely, any frontend, LiveView or React, can get messy if not carefully maintained. As the app grows and more developers contribute, regular code reviews and removing unused logic are essential, otherwise DX suffers just like in any oth
21.
by akarshc 11mo ago
True, I just liked the gradient for branding, and I love how it looks. From your perspective, you’re right though. At least I can assure you there’s no AI-generated code on the landing page. I’ll keep working to improve it as much as possib
22.
by akarshc 11mo ago
Yeah, like all other sites or just mine? Everything you are seeing is an AI? (from your perspective). What makes you less of an AI then?
23.
by akarshc 11mo ago
Author here: Not sure why everyone’s taking this as anti-rails or anti-laravel. It’s not. I just shared what worked best for my use case. Real-time updates are built into phoenix through channels and liveview, while in rails it’s handled th
24.
by akarshc 11mo ago
true, there’s always more to learn. i just shared what worked best for my use case with liveview. rails is also a great framework and i enjoy using it, but liveview’s built-in real-time updates and state management fit my project needs bett
25.
by akarshc 11mo ago
At the end of the article, I’ve highlighted the app I built with Phoenix, which is what he is referring to.
26.
by akarshc 11mo ago
Thanks for your feedback! Yes, Oban is a third-party package, but it’s built for Phoenix, which is what I meant in the article. Also, the article is not AI-generated. I’ve mentioned the app I built with Phoenix at the bottom to give context
27.
by akarshc 11mo ago
It’s not just a simple todo list. The product includes advanced features like goal tracking, minimal project management, a streak system, daily task resets with a 3-task limit, and AI-powered task creation that can break tasks into subtasks
28.
by akarshc 11mo ago
I completely agree. Requiring credit card info for a free trial often feels like a dark pattern designed to trap users into paying. I’m taking a different approach with my product by offering a 3-day free trial that doesn’t require a card,
29.
by akarshc 11mo ago
I don’t hire developers who are tied to just one framework. I prefer someone who has a solid understanding of a platform but also a mindset to learn new technologies. You don’t need a large team, just one or two talented developers on a goo
30.
by akarshc 11mo ago
I didn’t say that rails doesn’t use websockets. What i meant is that liveview comes with websockets fully integrated into the framework. This doesn’t mean rails can’t use websockets, but liveview has implemented it more seamlessly at the co

More ›