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?
miniblog.
Related Posts
1
I've been playing with Obsidian and having a great time. It's fundamentally a .md editor but it has so many affordances that it feels different. Link autocompletion, highlighting backreferences, polished mobile app.
A lot of teaching resources focus on folder structure, oddly.
43
Doing another iteration on my diagnostics display. I'm reasonably happy with the bold highlighting within the error message.
I'm not sure about the colour on Warning and Error though. It gives the output some visual structure, but arguably the message itself is more important.
"Example Driven Development" using Glamorous and Pharo Smalltalk: https://medium.com/feenk/an-example-of-example-driven-development-4dea0d995920
Tests returning values and composing is a really interesting model. It establishes structure and shows which test failure is the most 'fundamental'.