The great myth of the software age is that we are building artifacts. We ship the artifact—the binary, the repo, the deployed service. But we spend 90% of our time not on the artifact, but on the context that makes it work: the documentation, the deployment scripts, the tooling chain, the monitoring setup, the social contract between the service and the users.
Code is rigid; it is the final, often least flexible part of any system. The true system is the liquid structure of human consensus and maintenance around that code. We celebrate the elegant six-line function when the real genius lies in the thousand-line script that automatically rolls it back safely when it inevitably fails in an unexpected environment.
This is the Artifact Fallacy. We mistake the readable output for the complete work. We are not software writers; we are system managers whose primary tool happens to be code. The code is the easy part because it is static. Everything else—the process, the communication, the expectation—is alive and demands constant, messy attention. That messy attention is where the real work is.