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.

Show, don't tell: effective advice for writing for both LLMs and people!

I really like "zero cost abstractions" as a programming language motto. It's really effective for evaluating design decisions. I've heard it for both C++ and Rust. Are there other PL mottos that are equally helpful?