2 ms·
Exactly. This presentation style made it much easier for me to see what was being added to the code. I don't like having to continually scan different blocks of
by ath92 7y ago
Exactly. This presentation style made it much easier for me to see what was being added to the code. I don't like having to continually scan different blocks of code to see what changed, and try to make sense of how the changes fit in the bigger picture.
- Silhouette 7y agoI don't like having to continually scan different blocks of code to see what changed, and try to make sense of how the changes fit in the bigger picture. Indeed. Visual diff tools were invented for a reason, and using a side-by-side layout with some sort of colour coding and some attempt to align equivalent code is now close to universal. No-one would suggest doing code reviews by printing out the last two versions of a source file and comparing them on paper any more. In presenting tutorial material like this, IME the two most effective formats have been either something like that side-by-side diff, often with some extra annotations like chunky labelled arrows to highlight the specific areas or changes of interest, or something like the style here, with the changes at each step being highlighted and/or animated so it's easy to follow along. Both of these work for code but also other illustrations.