Skip To Main Content
Arnav Gupta on Muck Rack

Arnav Gupta

As seen in: Illumination, Medium, Wiley Online Library, arXiv, JAMA Psychiatry, Sportskeeda, Yahoo, HackerNoon, DEV Community, Forrester Research and
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work. Claim your profile

Get in touch with Arnav

Contact Arnav, search articles and posts on X, monitor coverage, and track replies from one place.

Learn more about Muck Rack

Actions

Share this page

Is this you?

As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile

Articles

The future of work is about visibility, not location

|
By Arnav Gupta
| ET Edge Insights Verified
For three years, every leadership conversation about work has started with the same question: where should people work from? Office, hybrid, or fully remote. Boards debate it, HR teams build policy decks around it, and employees quietly vote with their calendars. I think we have been asking the wrong question.
Open in Who Shared Issue with article?

p50, p95, p99: What Latency Percentiles Actually Mean for Your Node.js App

|
By Arnav Gupta
| DEV Community
Your monitoring dashboard shows average response time: 45ms. Looks great. Your users are complaining the app is slow. Both things are true. Here's why. Averages hide the worst experiences Imagine 100 API requests. 99 of them take 10ms. One takes 5000ms. Average: (99 × 10 + 5000) / 100 = 59.9ms Your dashboard shows ~60ms average. Looks fine. But one in every 100 users waited 5 seconds. If you have 10,000 daily active users, that's 100 people per day getting a 5-second response.
Open in Who Shared Issue with article?

Chaos Engineering for Node.js Without the Infrastructure

|
By Arnav Gupta
| DEV Community
Chaos engineering sounds expensive. Netflix built Chaos Monkey to randomly kill production servers. Google runs DiRT (Disaster Recovery Testing) across their entire infrastructure. Amazon does game days where they intentionally take down services. You're building a Node.js API. You don't have a platform team. You don't have a chaos infrastructure. But you still need to know: what happens when your dependencies get slow?
Open in Who Shared Issue with article?
See all 66 licensed articles (68 Total)