<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reporting on Maarten on IT</title><link>https://maarten.mulders.it/categories/reporting/</link><description>Recent content in Reporting on Maarten on IT</description><generator>Hugo</generator><language>en-us</language><copyright>&amp;copy; 2013 - 2026 Maarten Mulders</copyright><lastBuildDate>Mon, 27 Sep 2021 21:26:41 +0200</lastBuildDate><atom:link href="https://maarten.mulders.it/categories/reporting/index.xml" rel="self" type="application/rss+xml"/><item><title>Quickly count your code base</title><link>https://maarten.mulders.it/2016/02/quickly-count-your-code-base/</link><pubDate>Wed, 03 Feb 2016 08:10:40 +0200</pubDate><guid>https://maarten.mulders.it/2016/02/quickly-count-your-code-base/</guid><description>&lt;p&gt;Often, the size of a code base is measured in terms of &amp;ldquo;source lines of code&amp;rdquo; (SLoC).
If you&amp;rsquo;re interested in the size of your code base - or your client is - this metric provides a way to express that size.
Of course, comments and the like are not considered to be code, so how to determine this metric?
Using &lt;code&gt;grep&lt;/code&gt; is tempting, but it quickly results in a very complex and hard-to-understand approach.&lt;/p&gt;</description></item></channel></rss>