> Again, this is the opposite of what the author argues for, which is waiting for a couple instances before committing to an abstraction. Not duplicating a SQL query across hundreds of places.

Right. But this is a hypothetical, in-a-vacuum situation.

In the real world, your two, three duplicates are in production.

"We really should now de-duplicate this"

"There is not the time or budget, just copy it again; we'll replace all this one day".