Scanning code vs. Reading code (and Scanning as the focus of refactoring)
Last January, Uncle Bob wrote a blog post where points out some inconsistencies in a blog post by GeePaw Hill (who, I later learned, is a friend of his and a former employee).
But a few days later, Uncle Bob twitted about another blog post (with video) of GeePaw Hill. In that post, GeePaw Hill differentiates “scanning” code from “reading” code.
And Uncle Bob commended him for it.
Nicely done! Great message. The motivation for refactoring is to optimize scanning. Priceless.— Uncle Bob Martin (@unclebobmartin) February 5, 2018
thanks, bob! that means a lot coming from you.— Michael D. Hill (@GeePawHill) February 5, 2018
The insight that reading and scanning are different; and that scanning is the focus of refactoring, is really valuable. I hadn't thought of that before. So thank YOU.— Uncle Bob Martin (@unclebobmartin) February 5, 2018
A conversation by the greats!… Priceless!!!
And new lessons to remember: “reading and scanning are different” and “scanning is the focus of refactoring”.