Skip to main content
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
Source Link

This subject itself is difficult to google, so I apologize beforehand for the hundreds of links I'm sure are hidden somewhere. This question was moved from the philosophy site as they told me that it fits better here.

So, it came with this question: Is fewer lines of code always better?Is fewer lines of code always better?, a somewhat subjective question about code (about best practices). Then I thought about it and now I'm really curious about it. I have some questions around this subject itself:

  1. Are there other words that show signs of a sentence that, while syntactically correct and apparently right, can be used to clearly see that a sentence might be logically wrong? Always/never in something that makes me read it slowly and double check about the validity of that sentence.

  2. Where/how can these words be used? If it's a definition, for example, always can be used (as long as it doesn't class with other definitions). But people don't normally talk with pure definitions, and there're many cases (in programming at least) that people overuse the words 'always/never', maybe for laziness or shortness sake. Another example (for programming), 'Global state is evil', which could be reworded as 'Never use global state'.

This subject itself is difficult to google, so I apologize beforehand for the hundreds of links I'm sure are hidden somewhere. This question was moved from the philosophy site as they told me that it fits better here.

So, it came with this question: Is fewer lines of code always better?, a somewhat subjective question about code (about best practices). Then I thought about it and now I'm really curious about it. I have some questions around this subject itself:

  1. Are there other words that show signs of a sentence that, while syntactically correct and apparently right, can be used to clearly see that a sentence might be logically wrong? Always/never in something that makes me read it slowly and double check about the validity of that sentence.

  2. Where/how can these words be used? If it's a definition, for example, always can be used (as long as it doesn't class with other definitions). But people don't normally talk with pure definitions, and there're many cases (in programming at least) that people overuse the words 'always/never', maybe for laziness or shortness sake. Another example (for programming), 'Global state is evil', which could be reworded as 'Never use global state'.

This subject itself is difficult to google, so I apologize beforehand for the hundreds of links I'm sure are hidden somewhere. This question was moved from the philosophy site as they told me that it fits better here.

So, it came with this question: Is fewer lines of code always better?, a somewhat subjective question about code (about best practices). Then I thought about it and now I'm really curious about it. I have some questions around this subject itself:

  1. Are there other words that show signs of a sentence that, while syntactically correct and apparently right, can be used to clearly see that a sentence might be logically wrong? Always/never in something that makes me read it slowly and double check about the validity of that sentence.

  2. Where/how can these words be used? If it's a definition, for example, always can be used (as long as it doesn't class with other definitions). But people don't normally talk with pure definitions, and there're many cases (in programming at least) that people overuse the words 'always/never', maybe for laziness or shortness sake. Another example (for programming), 'Global state is evil', which could be reworded as 'Never use global state'.

Tweeted twitter.com/#!/StackLinguist/status/354058640191262720
Source Link

Can words like 'always' and 'never' be used to determine sentences inherently wrong?

This subject itself is difficult to google, so I apologize beforehand for the hundreds of links I'm sure are hidden somewhere. This question was moved from the philosophy site as they told me that it fits better here.

So, it came with this question: Is fewer lines of code always better?, a somewhat subjective question about code (about best practices). Then I thought about it and now I'm really curious about it. I have some questions around this subject itself:

  1. Are there other words that show signs of a sentence that, while syntactically correct and apparently right, can be used to clearly see that a sentence might be logically wrong? Always/never in something that makes me read it slowly and double check about the validity of that sentence.

  2. Where/how can these words be used? If it's a definition, for example, always can be used (as long as it doesn't class with other definitions). But people don't normally talk with pure definitions, and there're many cases (in programming at least) that people overuse the words 'always/never', maybe for laziness or shortness sake. Another example (for programming), 'Global state is evil', which could be reworded as 'Never use global state'.