miniblog.

Test code is total: we require it to always terminate or it's a failure! It also typically has 100% line and branch coverage. I feel way less nervous about refactoring tests, you can always just run them.

I'm writing an experimental PL and I want to exercise it on real programs asap. These need to be useful (so I actually try them), but simple (my PL is unfinished). My current ideas: * A git fuzzy branch switcher (shell commands) * dotfiles sync (filesystem access) Suggestions?

Merge any sequence of patches (e.g. rebasing a branch) feels like it relies on hope. Whether or not you get conflicts, whether or not the output is syntactically valid or does the right thing: sometimes the computer does too little, and other times it does too much.