Three Coffees and One Compile Error: A 4 A.M. Coding Diary
새벽 코딩 일지
It started, as these things always do, with a red squiggle that had no business being there. The types were correct. I knew they were correct. I had written them myself, which, in hindsight, should have been the first clue.
By coffee number two I had blamed the compiler, the package manager, a recent minor version bump, and the phase of the moon. I had read the same error message enough times that it stopped looking like words. Somewhere around 2 a.m. I began git-bisecting my own evening.
The culprit, of course, was me: a refactor three commits earlier had quietly changed a generic parameter, and everything downstream had been holding its breath since. One character. Three hours. One-and-a-half of those hours were spent being confidently wrong.
Lessons recorded for posterity: read the error from the top, trust the compiler before you trust yourself, and no code written after the third coffee has ever survived code review.