miniblog.

What software designs require clean slate 'revolution' implementations, rather than evolution? I can think of: borrow checking in a PL (existing code is unsafe), microkernels (architecture is too different from monokernels), and full REPLs (can't add type redefinition later).

I've heard the term 'mechanical sympathy' for the ability to write efficient code due to understanding how a CPU works. Is there a legacy software equivalent? 'Architecture sympathy', where you've worked out the structure that the author intended and things begin to make sense?

I'm writing ASCII diagrams for docs. It's not terribly pretty, but it's so easy to contribute to. I've seen so many beautiful architecture diagrams go stale because no-one wants to find the file and the GUI tool to keep it updated.