miniblog.

Learning software development through playing and contributing to a MUD: https://tashian.com/articles/how-i-learned-to-program/

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've been using "Expected Int, but got String" for my type error messages, but I've been wondering if I could do better. "Expected Int here, but this value has type String" or "This expression requires Int, but the value is String". Do you have a favourite?