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?

In many respects I feel an LLM benefits from a monorepo. I've vibe coded a bunch of helper CLIs recently and end up repeating the same preferences for all of them.

I want all my CLIs to use clippy, parse arguments with clap, etc. They're distinct tools in distinct repos though.

I think you could build an interesting IDE with a tiny embedded LLM in addition to the usual tooling.

Features like 'extract method' would be much nicer if an LLM could provide a name. Choosing a good name is virtually impossible from just a typed AST.

Delighted to see that TOML has released a new version! TOML is overall a great standard but I understand they had limited people with the power to cut a new release.

https://github.com/toml-lang/toml/releases/tag/1.1.0

You can often estimate the age of a website based on how well it displays on mobile.

All my sites end up with media queries in the CSS for narrow screens. It's so hard to design a single UI that scales from phone to desktop otherwise.

I find it odd that people recommend Docker for sandboxing agentic coding tools. Isn't it easier to just create a separate user account on the machine?

It's an established security boundary, and viewing output is easy (just make the user's home directory world readable).

I'm never sure what to name my remotes in git. I tend to use 'mine' so I can add other forks later, but sometimes I use 'gh' or the traditional 'origin'.

What do others use?

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.

One subtle behaviour of Claude that wasn't obvious to me: whilst each conversation is transient, permissions persist across conversations.

So if you've given permission to run e.g. 'cargo test' or even 'cargo run', you need to be sure that all future invocations are safe too.

You can see the current permissions with /permissions.