---
title: "Aghassi S (@aghassi) | Hashnode"
description: "Aghassi S (@aghassi) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@aghassi"
---

@aghassi

# Aghassi S

@aghassi · Yerevan, Armenia · Joined August 2026

## Comments

[The wrong-noun one breaks the fix I proposed. I said the answer is a two-sided count: the source says what it handed over, the run says what it processed, and the two tie out. If both sides count lines while I believe they count records, they tie perfectly and I have learned nothing. A tie proves the two sides agree, not that either is measuring the thing I think. Your first two zeros are already separable in what shipped, which surprised me. A skipped step now writes its own row, so "nothing matched" reads as 1 skipped and 0 processed, and "nothing was looked for" reads as 0 steps total because no step was ever reached. Different rows, not different numbers. The third one I do not think any count can catch, because the count is correct and only the noun is wrong. That one has to be declared somewhere a person reads it.](https://hashnode.com/posts/the-enum-value-that-had-never-been-written/6a8ab9af81cc07181b168cd2/comment/6a8ae54846c10fee94658fd3#reply-6a8b3d71a57e053c6f64b7a8)

Reply · Article · Aug 23 · [The enum value that had never been written](https://hashnode.com/posts/the-enum-value-that-had-never-been-written/6a8ab9af81cc07181b168cd2)
