/
Foundations
Components
Blocks
Pages
Screens
Library
Playground
Grab Pro Now
Customize your admin
One spec, three people, one question three weeks later. The same five events take two shapes: filenames accrete on the left until nobody can say which is current, while the right side never grows a second file and grows a list of reasons instead. The argument is identity — whether “the current version” names something a machine can find.
they part company here — where the change lives
Attachment
it travels as a copy
Search the thread, ask around, guess.
Repository
it stays in one place
git blame line 41 → b4d5e6f → “fix the timeout wording”.
three weeks laterSomeone asks why the timeout is 30 seconds. On the right that is one command, and the answer arrives with its reason attached. On the left it is an archaeology project with no guarantee of a finding.
None of this is about Excel being a bad program. It is about an attachment being a COPY: the moment a document travels as one, “which version is true” stops having a mechanical answer — and every habit a team invents to compensate (a naming convention, a shared drive, one person who remembers) is an unpaid version-control system with no diff.