What Is Thousands of Lines of Code (KLOC)?

When buying a new car, it's essential to know how many miles per gallon it gets. When purchasing a new house, it's necessary to know how many square feet it has and when you're looking to buy software, it's essential to know how many lines of code it has. The number of lines of code is always measured, which is used to evaluate the software size. KLOCs are always used to estimate the required time for a team to build a project. The lower the KLOC, the less time it takes for your team to make the product—which means you can get your product out there and generate revenue sooner. When you think about it, it's pretty silly to try and measure developer productivity by lines of code. That's not how developers work. For example, if I were a factory worker, I'd be able to tell you exactly how fast I could make widgets. It would be like, "If I work at this pace and produce this many widgets in an hour, then I'm doing great!" but, if I were a software developer and someone asked me how many lines of code I wrote in an hour? Well, that would be silly. Because writing code is only part of what we do as developers, we also have to test our code—sometimes, we need to refactor it and rewrite it entirely! So, if we're being paid based on how many lines of code we write per hour. Wwhat happens when we need to take time away from writing new code to fix bugs or improve our existing codebase? And what happens when we want to write tests first before starting any coding work? If all those things are considered "non-development" work, then we're not being paid for our development time!