<p>An interesting exercise is to run a tool like <a href="https://github.com/AlDanial/cloc">cloc</a> to count the number of lines in your application.</p>
<p>It counts the number of files and lines within them, as well as how many lines are blank, comments or code.</p>
<p>It's a metric that I like to check occasionally as I like to keep codebases lean and with the minimum amount of code.</p>
<p>I don't like to have features that aren't used or <a href="/daily/2025/02/16/pre-optimise">pre-optimised code</a> for use cases that may not happen.</p>
<p>The more code there is in your application, the problems you could encounter.</p>
<p>There are more places for bugs and issues to hide.</p>
<p>Keeping the amount of code to a minimum makes it quicker and easier to write, review and release as well as fix any bugs that are found in the future.</p>
format:full_html
processed:|
<p>An interesting exercise is to run a tool like <a href="https://github.com/AlDanial/cloc">cloc</a> to count the number of lines in your application.</p>
<p>It counts the number of files and lines within them, as well as how many lines are blank, comments or code.</p>
<p>It's a metric that I like to check occasionally as I like to keep codebases lean and with the minimum amount of code.</p>
<p>I don't like to have features that aren't used or <a href="/daily/2025/02/16/pre-optimise">pre-optimised code</a> for use cases that may not happen.</p>
<p>The more code there is in your application, the problems you could encounter.</p>
<p>There are more places for bugs and issues to hide.</p>
<p>Keeping the amount of code to a minimum makes it quicker and easier to write, review and release as well as fix any bugs that are found in the future.</p>