---
title: "Ashish Kr Jha (@Ashish14411) | Hashnode"
description: "Ashish Kr Jha (@Ashish14411) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@Ashish14411"
---

@Ashish14411

# Ashish Kr Jha

@Ashish14411 · Joined July 2022

[Website](https://ashishkrjha.dev/)

### [Why describe.concurrent Made My Vitest Suite Slower](https://blog.ashishkrjha.dev/why-describe-concurrent-made-my-vitest-suite-slower?utm_source=hashnode&utm_medium=feed)

The first result was the confusing one.

15 min read · [blog.ashishkrjha.dev](https://blog.ashishkrjha.dev/why-describe-concurrent-made-my-vitest-suite-slower?utm_source=hashnode&utm_medium=feed)

[3](https://hashnode.com/posts/why-describe-concurrent-made-my-vitest-suite-slower/6af753f356fad44e911149a2) [20h ago](https://hashnode.com/posts/why-describe-concurrent-made-my-vitest-suite-slower/6af753f356fad44e911149a2)

### [The CORS Error That Was a Race Condition](https://blog.ashishkrjha.dev/the-cors-error-that-was-a-race-condition?utm_source=hashnode&utm_medium=feed)

The browser blamed CORS. The CORS config was fine. The real fault was two tabs refreshing the same token at the same moment.

16 min read · [blog.ashishkrjha.dev](https://blog.ashishkrjha.dev/the-cors-error-that-was-a-race-condition?utm_source=hashnode&utm_medium=feed)

[Aug 29](https://hashnode.com/posts/the-cors-error-that-was-a-race-condition/6a929d574b9f5949986f9c3c)

### [My Idle Background Worker Was the Most Expensive Thing I Owned](https://blog.ashishkrjha.dev/my-idle-background-worker-was-the-most-expensive-thing-i-owned?utm_source=hashnode&utm_medium=feed)

A queue that was empty almost always, a consumer polling it once a second forever, and a platform that only bills for CPU when requests arrive.

20 min read · [blog.ashishkrjha.dev](https://blog.ashishkrjha.dev/my-idle-background-worker-was-the-most-expensive-thing-i-owned?utm_source=hashnode&utm_medium=feed)

[6](https://hashnode.com/posts/my-idle-background-worker-was-the-most-expensive-thing-i-owned/6a8e33d71011e317aa404c6d) [Aug 26](https://hashnode.com/posts/my-idle-background-worker-was-the-most-expensive-thing-i-owned/6a8e33d71011e317aa404c6d)

### [No fetch, No Storage: Shipping Inside a Sandboxed Host](https://blog.ashishkrjha.dev/no-fetch-no-storage-shipping-inside-a-sandboxed-host?utm_source=hashnode&utm_medium=feed)

Building a React app inside a sandboxed host with no fetch, XHR, or browser storage: SDK network proxies, platform adapters, async polling, idempotency, and local development.

13 min read · [blog.ashishkrjha.dev](https://blog.ashishkrjha.dev/no-fetch-no-storage-shipping-inside-a-sandboxed-host?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/no-fetch-no-storage-shipping-inside-a-sandboxed-host/6a892622668ed11f938ca339) [Aug 22](https://hashnode.com/posts/no-fetch-no-storage-shipping-inside-a-sandboxed-host/6a892622668ed11f938ca339)

### [Instructions Are Hints: Guardrails for an LLM Tool Loop](https://blog.ashishkrjha.dev/instructions-are-hints-guardrails-for-an-llm-tool-loop?utm_source=hashnode&utm_medium=feed)

A model with query access to 530 objects and 13,000 fields needs three of them. Here's the retrieval layer, the guardrails, and why two of the three don't hold.

13 min read · [blog.ashishkrjha.dev](https://blog.ashishkrjha.dev/instructions-are-hints-guardrails-for-an-llm-tool-loop?utm_source=hashnode&utm_medium=feed)

[Aug 21](https://hashnode.com/posts/instructions-are-hints-guardrails-for-an-llm-tool-loop/6a88bc59ebf8ac9e8a7cbdfe)