Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.


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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: