miniblog.

I'm still not sure whether a language should include a "kitchen sink linter" like Rust's clippy or have a package oriented "thousand flowers bloom" linter like eslint for JS and TS. Clippy is delightful out of the box but eslint makes it so easy to have project specific lints.

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.

Today I learnt that `cargo fix` won't fix code with compiler errors by default, but you can override this! $ cargo fix --broken-code --allow-dirty && cargo clippy --fix --allow-dirty This incantation does exactly what I wanted :)