Nijat Ahmadzada

disclaimer: I m guilty of this.

The more agentic capability i seem to have at my disposal, the deeper i go. But is that where I should be?

I spent a week fixing three separate monitoring bugs and they turned out to be the same bug wearing different clothes. In all three the instrument could only ever return good news, and none of them looked broken.

One. A refresh job reported one item refreshed successfully. I checked the field that records when the price was last written and it had not moved. The function underneath returns an ok status for a product that does not exist, and my counter incremented on ok rather than on a value having been written. So the counter measured whether the call returned, not whether anything happened. It had been reporting success for as long as it had existed.

Two. A scraper node was supposed to rotate its address after being blocked too often. It had rotated zero times in twelve hours. The block counter was fed in the general error path, but a captcha was caught by an earlier branch that returned before reaching it. So the one failure the entire mechanism existed for was the one failure it could not see. The node called itself healthy the whole time it was being turned away.

Three. My public status page showed a degraded service for weeks. The service was fine. Worker identity was keyed on hostname, and inside a container the hostname is the container id, so every restart registered a new machine while the old rows stayed forever, ageing and unhealthy. The status page was correctly reporting on machines that had not existed for weeks.

Writing this down before tomorrow so I can be held to it.

The last three weeks were almost entirely the boring half. Making the same prompt land in the same place twice. Making the model picker say why it swapped instead of swapping silently. Making a Look load the whole recipe in one click rather than most of it. None of that demos well and all of it is the difference between a tool and a toy.