Sending patches/PRs to projects creates asymmetric work. The maintainer needs to think about the future work it might create.
Fortunately CI running tests, checking formatting, even enforcing commit message style helps! Reducing the amount of work needed to accept a PR matters.
Related Posts
I've added an eval button to the website of my programming language!
It's a been a lot of work to lock down appropriately. It still needs some UI polish but it's so nice to be able to try snippets immediately.
https://www.garden-lang.org/
I'm having fun writing a simple type checker, but I'm learning firsthand why syntax-directed checking doesn't work. It prevents inference.
My checker catches real bugs, but it can't handle cases like this:
[1, 2].map(fun(x) { x + 1; })
I think I need bidirectional checking.
I'm increasingly doubtful that commit messages should be entirely immutable.
I sometimes find myself editing or commenting on merged pull requests, to help future readers.
Phabricator appended a URL to commit messages, which helped. In principle PR merging could do the same thing.