The importance of Git Commit/Push often

There are many forms of "shipping" your work as we recently discussed

Shipping does not necessarily mean a product release, but rather releasing your work external to you. It can be a Git push, running tests in CI, a prototype, a document that others can read -- basically something of lasting value that others can interact with. (Email does not count).

As a developer, the simplest way to ship your work is a Git push. It does not have to be perfect. In most cases, it does not even have to be done. That is the beauty of software, it is soft -- it can be improved/finished later. A Git commit does not even have to be code -- it can be documentation, specs, etc. A Git commit/push is the simplest and most effective way to demonstrate you are providing value to the project or organization. Yet how many of us are consumed with ephemeral activities that in the end provide no lasting value?