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.
miniblog.
Related Posts
LLMs have been really helpful for me porting some JS projects to TS.
Since the types are erased and annotations are optional, I can go gradually and safely with more minimal human oversight.
(I'm not sure if it'll significantly help robustness, but it's lovely for navigation.)
Reviewing some of my earliest web projects: they have a mix of Postgres, MySQL and Mongo.
These days I just use sqlite for all my personal projects. It's really good at my scale and makes deploying very easier.
Caddy is really growing on me. It's nice having a web proxy that includes letsencrypt functionality without any additional configuration.
I've tended to use nginx with a separate letsencrypt setup for projects before, and it's much more awkward.