Wait, nobody has gone &quot;Chuck Norris&#x27;s Norris Number is 2.2 million!&quot;? (I clicked on the title just because of Norris, I was thinking it was another Chuck reference.)<p>I can see the steps.  I have and can crank out 2,000 lines of code.  We see this all the time in hack-a-thons.<p>20K lines means a team and tools and some level of software control. Maybe a nod to architecture.<p>200K lines is a good sized project with a starting level of architecture first (maybe proceeded by throwaway prototypes) and then some serious software development methodology.<p>While the author writing 200K lines of code is cool, in today&#x27;s business environment, that&#x27;s not really going to happen.  The cycle of prototype, code, build, test, (x2) then pivot and then repeat everything isn&#x27;t a single programmer.<p>I&#x27;ve done 3GL &#x2F; 4GL for a long time (Burroughs LINC!!) that promised that.  And while it did turn 50 lines of LINC into 1000 lines of COBOL, there was a lot of though in those 50 lines.  So I look at the current &quot;10 lines of code in XYZ&quot; I think &quot;and I need 100,000 lines of libraries too&quot;.<p>Large code bases are not for the faint of heart of for cowperson coders.  You may be able to write 200K of code, but it it can&#x27;t be checked in and not break my build I can&#x27;t use you.