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).
New Blog: "The Citizenship Argument", in answer to @GeePawHill's brilliant post about TDD. https://t.co/GViS3p5LUx
— Uncle Bob Martin (@unclebobmartin) January 18, 2018
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.
Great new @GeePawHill video. Don’t be fooled by the simple start. Much meat soon follows. https://t.co/iq2CFlCNRT
— Uncle Bob Martin (@unclebobmartin) February 5, 2018
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”.