DEV Community

Jonathan Berg
Jonathan Berg

Posted on

Saved work is a dependency, treat it like one

Nobody thinks of their own past work as a dependency. Dependencies are other people's code, pinned in a lockfile, watched by bots, cursed at when they break. Your own stuff is just yours. It sits in a repo or a folder or an old agent conversation, and you assume it stays the way you left it.

Then your agent pulls a component you saved months ago into a new project, and the illusion ends. That saved component is a dependency now. It has dependents. It has versions, whether you track them or not. And most of us treat it with none of the discipline we demand from a package registry.

The fix that never travels

I fixed something in one project this week, and then I spent the next hour on a worse problem: how many other projects still carry the old version? With a published package you can answer that. There is a changelog, a version number, a list of what depends on what. With your own saved work the fix usually stays exactly where you made it, while the flawed copy keeps getting reused everywhere else.

This is the uncomfortable math of reuse. The better an asset is, the more places it lives, and the more places its bugs live too. Saving multiplies the good and the bad with the same enthusiasm.

Storage is not maintenance

Saving is the easy half, and I say that as someone who has written a lot here about why saving matters. But a library that only accumulates is a graveyard with good intentions. A saved asset needs to answer a few questions or it slowly becomes useless. What version am I? What changed and why? What work was built on top of me?

Without those answers you drift into the quiet failure mode: you stop trusting your own library. You can no longer tell which copy is current, so you regenerate from scratch, which is exactly what the library was supposed to prevent. Fear of your own saved work is the tell that storage happened but maintenance did not.

The bar I hold my own tools to

This is the standard I am building toward with Sirro. An edit creates a new version instead of silently overwriting the old one. History is kept with the asset, not in your head. And when the source improves, that improvement should be able to reach the work built on it, instead of stranding every past use on the old copy.

We spent years learning to respect dependencies. Pin the version. Read the changelog. Know what depends on what. Your own work deserves the same respect, because your agent is about to reuse more of it than any stranger's package ever will. The component it pulls next month should be the best version you have, not the first one you happened to save.

Top comments (0)