How a one-line fix grows legs
A bug report may point to a single typo, but the typo is not always the first thing that must change. Perhaps the text lives in a software library—a reusable package of code—that only works with a newer operating system. Updating the system, in turn, may require more disk space or a different drive format. Each step is reasonable on its own; together, they can turn a tiny edit into a day of setup.
The dependency chain
Software is built in layers. An application relies on libraries, libraries rely on operating-system features, and the whole stack depends on hardware and storage behaving as expected. When one layer is outdated or incompatible, work at a higher layer can stall. The person making the fix may have to prepare the environment before they can even test it.
That preparation can expose another obstacle: an old project may use tools that no longer install cleanly, or a change may need to be checked across multiple versions. The original task has not become more complicated in principle; the route to completing it has.
Why developers call it yak shaving
“Yak shaving” is informal tech slang for doing a succession of seemingly unrelated chores because each one blocks the next. The name captures how far the work can drift from its starting point. A developer sets out to correct a typo, then updates a library, then the operating system, then reformats a drive—and still has the original correction left to make.
The practical cost is not just the time spent on those chores. Every extra change creates another chance to break something, so developers may need to test carefully and avoid bundling unrelated updates with the small fix. The typo is easy; reaching a safe, working place to change it is the real job.
