¿Menos líneas de código significa más rápido?

Does less lines of code mean faster?

Efficiency Fewer lines of code can achieve the same results (and probably better) than many lines of code. If you reduce the amount of code in a task, you will lower the bug count, especially if the source code is clear, readable, and maintainable.

No. code length does not affect the app performance, but smaller code length helps other to understand your code better. This can be the case when you want someone else to add or modify some functionality to your application. When you can write same logic in less no of lines then it is preferable.

Michael Borgwardt answers (76 votes): 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.

Lines of Code (SLOC or LOC) is one of the most widely used sizing metrics in industry. SLOC is typically used to predict the amount of effort that will be required to develop a program, as well as to estimate programming productivity or complexity once the software is produced.

Java’s checkstyle (checkstyle Size Violations ) puts a default limit of 150 lines before a warning. I think this is a safe upper bound. Even then, I think that most methods should be less than 50 (one screen). You will probably find a way to refactor or encapsulate something if you’re going over 100.

Ideally, one line of code is a unit element that means or performs something specific – a part of a sentence if you will. It is generally agreed that the ideal length for a line of code is from 80 to 100 characters.

Mac OS X is considered to be the largest operating system ever written. It contains over 85 million lines of codes.

So, to count the lines of code in a project on Windows.

1. Open the folder, with the code in, in Windows Explorer.
2. Open WSL there (Shift+Right click and select ‘Open Linux shell here’, or type ‘wsl’ in the address bar.)
3. Type `find . name ‘*.cs’ | xargs wc -l` (assuming you’re using C#)
4. Look at the number.

Review fewer than 400 lines of code at a time A SmartBear study of a Cisco Systems programming team revealed that developers should review no more than 200 to 400 lines of code (LOC) at a time. The brain can only effectively process so much information at a time; beyond 400 LOC, the ability to find defects diminishes.

Is this a lot? By comparison, the Microsoft Windows operating system has roughly 50 million lines of code.

Originally Answered: How many lines of code do professional programmers write per hour? An average programmer writes twenty lines of code in an hour. A good programmer writes one hundred lines of code in an hour.

And all 2 billion lines of code fits into a single code repository….The biggest codebases in history

• approximately 3.5M files that.
• results in a Git repo of about 300 gigabytes in size.
• with 4,000 engineers producing 1,760 daily “lab builds” across 440 branches, plus thousands of pull request validation builds.

I would say that the reason it’s important to reduce the number of lines of code is to be able to view more of a function on a single page. The easier it is to view a method or class without needing to scroll, the easier it is to maintain the context in your head. – CLandry Feb 5 ’13 at 14:14

I am a Software developer who works on J2SE (core java). Often during our code reviews we are asked to reduce the number of lines in our code.

You mention 1,000 lines of code as a “lot.” That really doesn’t mean anything without context. I have worked on several projects that had well over a million lines of code.

Optimize the page load time of your mobile site by deferring the parsing of unnecessary