miniblog.

I've had good results by prompting an LLM "review your changes" in the same session when I don't like the initial output. I'm surprised this is effective: I would think it's redundant when you're running with a high effort setting.

I made some changes to a node express project that I haven't touched in almost five years. I was pleasantly surprised that I only needed to update one dependency to get it working again! (It was sqlite3, which is a native dependency using node-gyp.)

I really like the MELPA model of packaging directly from git. It solves the problem of forgetting to release something -- just merge a PR and you're done. It also makes version number bumps much less important. You could go even further in a statically typed language and also figure out when breaking changes occur.