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've been experimenting with different pagination UIs. It's so common to have arrows, but I've realised they're redundant here. When you have the adjacent values as well as the final value, you don't need > and >> arrows too. Thoughts?

I find myself using a "splatter then clean up" technique when working with code. I add a ton of prints/logs/asserts/type annotations until I've found the issue. I then throw them all away! It feels like redundant work, but I don't have a nicer solution.