3 ms·

> I have never had a discussion with coworkers that hinged upon whether or not a particular function is, was, or ought to be a method Because _you_ haven’t mea

> I have never had a discussion with coworkers that hinged upon whether or not a particular function is, was, or ought to be a method Because _you_ haven’t means the entire industry is wrong?

stouset 2y ago
I’m not saying the industry is wrong. The two words have clear and distinct meaning. My point is only that fretting over the distinction between the words serves nearly zero utility in day to day software engineering. It’s like “less than” vs. “fewer”. Each has a correct use, but nobody is confused when you use the wrong one. Many confuse the two, to the point that it’s becoming less and less wrong to use one when the other should be used. “Method” and “function” are similar. In twenty years, nobody is going to care that they once had a distinctive purpose because that distinction serves little utility.
- alex_lav 2y ago
  “People will know what I mean, so why bother being correct or specific” is a flimsy argument, to me, as to why a person shouldn’t care about using correct and precise language. Nor does it really challenge the need for correct and precise language in the first place. Small children say things incorrectly and we still understand them. Should we all talk like that?
  - stouset 2y ago
    Language is fluid and changes over time. Pedantically clinging to distinctions that no longer serve useful purposes doesn’t stop this from happening. If a clear separation in meaning between the two words was useful, their distinct use would become more closely adhered to over time. If not, people will start to blend and confuse the two. Of those options, the latter has happened and will likely continue happening with or without your objections. That this has happened is pretty clear evidence that the distinction hasn’t been worth maintaining. > Small children say things incorrectly and we still understand them. Should we all talk like that? Fully grown, articulate adults say things “incorrectly” all the time and nobody bats an eye. The sentence “Hey, where you going?” is missing an entire verb and every one of us has said and heard that sentence (or one like it) hundreds of times without anyone noticing or caring.
    - alex_lav 2y ago
      Yes, exactly. Language is fluid and the value of preciseness depends entirely on context. As in, when discussing language design (like we’re doing in this blog post and these comments), method vs function is important. Because of the context. So, when you’re talking to your coworkers about…whatever… the context probably makes method vs function insignificant. Unless you work in language design, in which case your take is just pretty blatantly awful.

> I have never had a discussion with coworkers that hinged upon whether or not a particular function is, was, or ought to be a method Because _you_ haven’t means the entire industry is wrong?

stouset 2y ago

I’m not saying the industry is wrong. The two words have clear and distinct meaning. My point is only that fretting over the distinction between the words serves nearly zero utility in day to day software engineering. It’s like “less than” vs. “fewer”. Each has a correct use, but nobody is confused when you use the wrong one. Many confuse the two, to the point that it’s becoming less and less wrong to use one when the other should be used. “Method” and “function” are similar. In twenty years, nobody is going to care that they once had a distinctive purpose because that distinction serves little utility.

alex_lav 2y ago
“People will know what I mean, so why bother being correct or specific” is a flimsy argument, to me, as to why a person shouldn’t care about using correct and precise language. Nor does it really challenge the need for correct and precise language in the first place. Small children say things incorrectly and we still understand them. Should we all talk like that?
- stouset 2y ago
  Language is fluid and changes over time. Pedantically clinging to distinctions that no longer serve useful purposes doesn’t stop this from happening. If a clear separation in meaning between the two words was useful, their distinct use would become more closely adhered to over time. If not, people will start to blend and confuse the two. Of those options, the latter has happened and will likely continue happening with or without your objections. That this has happened is pretty clear evidence that the distinction hasn’t been worth maintaining. > Small children say things incorrectly and we still understand them. Should we all talk like that? Fully grown, articulate adults say things “incorrectly” all the time and nobody bats an eye. The sentence “Hey, where you going?” is missing an entire verb and every one of us has said and heard that sentence (or one like it) hundreds of times without anyone noticing or caring.
  - alex_lav 2y ago
    Yes, exactly. Language is fluid and the value of preciseness depends entirely on context. As in, when discussing language design (like we’re doing in this blog post and these comments), method vs function is important. Because of the context. So, when you’re talking to your coworkers about…whatever… the context probably makes method vs function insignificant. Unless you work in language design, in which case your take is just pretty blatantly awful.