3 ms·
I publish as much as I can, and deliberately so. Not so much for internet points but because: 1. It forces me to write a README. No matter how small the projec
by Hackbraten 5y ago
I publish as much as I can, and deliberately so. Not so much for internet points but because:
1. It forces me to write a README. No matter how small the project, I afford it an introductory paragraph, installation instructions, usage instructions, and a license. Doing that all the time helps build good habits. If it hurts, I’m not doing it often enough. Doing it often enough helps overcome resistance one day when it actually counts.
2. I contribute something back. It’s not exactly curl, but who am I to judge whether my project will be too trivial to be useful for others? I prefer to leave that decision up to the visitor.
3. Future me is going to get a README for free a couple of years down the road, when the details are long forgotten.
Example: this repository [1] is for a 50-line Bash script [2].
[1]: https://github.com/claui/aws-credential-1password https://github.com/claui/aws-credential-1password
[2]: https://github.com/claui/aws-credential-1password/blob/main/aws-credential-1password https://github.com/claui/aws-credential-1password/blob/main/...