miniblog.

I've never seen a good design philosophy on how to sort compiler errors for the best UX. Do you order by line, or by severity? Do you put the most actionable at the end (because that's most visible when the terminal scrolls) or at the beginning?

If you have a value that can be any type (the 'top type'), what operations should your language support on that value? Equality is very common, but it's debatable. I increasingly feel that every value in a language should have some sort of debug print available.

Suppose you set up a repository that accepts any PR that passes CI. You forbid CI changes, but the rest of the codebase is fair game. What sort of testing, linting etc would you configure for CI?