Epplus

He opened Task Manager. 1.8 GB of RAM. Garbage collection was running every few seconds, like a frantic housekeeper at a frat party.

EPPlus, like all great libraries, had taught him a deeper lesson: EPPlus abstracts away the horror of Open XML’s SharedStringTable and CellValue types, but it cannot abstract away memory. The “deep story” isn’t about Excel—it’s about the gap between what we ask computers to hold and what they can actually hold. epplus

Arjun needed a different pattern.

// EPPlus is not a database. // It is not a memory palace. // It is a translator between two worlds: // the clean, infinite grid of human thought, // and the cold, finite heap of a machine. // Respect both. Then he pushed, closed his laptop, and watched the sunrise. The spreadsheet ran itself that morning. And for a few hours, Arjun felt something rare: the quiet peace of writing code that finally understood its own limits. If you meant something different—like a dramatic narrative where EPPlus itself is a character or a metaphor—let me know and I'll pivot. He opened Task Manager

Null. He’d written defensive code against nulls. But the null wasn't the problem. It was the memory of the null. EPPlus, like all great libraries, had taught him

He added a comment to the new codebase, right above the using statement:

The ExcelPackage.Load() call hung for twelve seconds—an eternity. Then, a NullReferenceException on a cell that should never be empty. Arjun traced it back to line 847: worksheet.Cells["M" + rowIndex].Value = null;