Why are shorter codes better?

Arguably, using shorter lines of code is more efficient than spreading the code over several lines. If you have more lines of code, there are more places for bugs to hide and finding them might be more of a hassle. Fewer lines of code can achieve the same results (and probably better) than many lines of code.

What makes a code faster?

To code faster, one has to be efficient; that is, no wasted effort or motion. This can mean everything from typing to tools to thinking. But most of our work as programmers isn’t typing, or compiling—it’s thinking. To think faster, you have to learn more patterns and relationships.

Why is long code bad?

Why you should care A piece of source code in your software could be compared to a page of a book. In addition to negatively affecting readability, having very long lines can destroy the positive impact of code indentation, which makes the code even harder to understand and maintain (because of chaotic line returns).

How do I know if my code is efficient?

You know you are writing good code when:

1. Things are clever, but not too clever.
2. Algorithms are optimal, both in speed as well as in readability.
3. Classes, variables and functions are well named and make sense without having to think too much.
4. You come back to it after a weekend off, and you can jump straight in.

Is it better to have more or less lines of code?

It depends, and your example is not useful in making the decision. While fewer lines of code are not always better (at some point it leads to obfuscation), they usually are, simply because there’s fewer things to keep track of when trying to understand the code.

How important is the number of lines of code in reading?

Human eyes tire faster when they have to move a lot, especially when they have to move vertically (lateral movement is less an issue). Using fewer lines of code, all other things being equal, will allow the reader to grasp the code with less vertical eye movement, so that’s somewhat good.

Is it better to use single regex or many lines of code?

With single regex you can achieve as much as with many lines of code – but it sometimes takes hours to understand single regex. However, there are some regex that are widely used and google searchable. Which of these programming styles is better?

What is the best style of programming?

Best style is the one which makes the code most readable (for a human, that is — computers don’t care). But “readable” depends a lot on who does the reading so that’s context dependent. This is enough, though, to answer your exact question: “Is [whatever] always better”?