I agree with using descriptive identifier names and using function names to express intent of lines of code.
But I don't understand your point in bringing it up here.
> "It is not worth doing," she said, [it=foobar]
baz(it) = "$it is not worth doing"
baz("foobar")
`it` is neither a descriptive identifier, nor did I see a suggestion for what the function `baz` could be called to make it descriptive.
Re:Stop defacing quotes with brackets
by capableweb on Wednesday February 10, 2021 @01:26PM
(#26092924)
It wasn't referring to the specific identifier "it" here, but more in general as I took your point to mainly be about "if there's a benefit to using other values for X in other contexts", meaning that putting things into variables only serves the functionality of reuse in different contexts, not also to name passages of code.
If you never pulled out code into its own separate function just in order to name some lines of code, you should give it a try. You can avoid a lot of comments and/or confusion by just structuring your code in a way that allows you to name lines of code as concepts and abstractions. No need for it to happen more than once for you to do so.