---
title: "Comment by Sanoary Istiaque on \"My Idle Background Worker Was the Most Expensive Thing I Owned\" | Hashnode"
description: "This was such a relatable engineering story. It’s easy to overlook the cost of something that’s “just sitting there” until the numbers make you pay attention. I"
url: "https://hashnode.com/posts/my-idle-background-worker-was-the-most-expensive-thing-i-owned/6a8e33d71011e317aa404c6d/comment/6a8ec051b25232b1a0daab87"
---

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

Comment [My Idle Background Worker Was the Most Expensive Thing I Owned](https://hashnode.com/posts/my-idle-background-worker-was-the-most-expensive-thing-i-owned/6a8e33d71011e317aa404c6d)

[Sanoary Istiaque](https://hashnode.com/@istyy)

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

This was such a relatable engineering story. It’s easy to overlook the cost of something that’s “just sitting there” until the numbers make you pay attention. I really liked the practical lesson here: infrastructure decisions should be revisited as usage and scale change. A great reminder that optimization isn’t always about making things faster it can also be about questioning what actually needs to be running in the first place.

[Ashish Kr Jha](https://hashnode.com/@Ashish14411)

[Aug 29](https://hashnode.com/posts/my-idle-background-worker-was-the-most-expensive-thing-i-owned/6a8e33d71011e317aa404c6d/comment/6a8ec051b25232b1a0daab87#reply-6a929e6406cfedaf8b76039e)

Exactly. The useful question turned out to be less “what can I optimize?” and more “what actually needs to exist all the time?”