miniblog.

Over a sufficiently long time horizon, all code you write is legacy code.

When a tool supports both regular expressions and literal strings, which should be the default? If you default to regex, users can match more strings than they realise (e.g. `foo.txt`) or less (e.g. `foo(bar)`). I typically see regex as the default, but I prefer the opposite.

I've been writing docs for different programming language operators (+, *, == and so on). Each one gets a separate web page. I've suddenly realised that / is much harder! docs/+ and docs/== is fine, but docs// just doesn't work as a URL in a static site. Any ideas?