1 brick is fungible with another brick. Lines of code are not. A project could be roughly sized by "bricks required"(if the project is a wall), but very few tas

1 brick is fungible with another brick. Lines of code are not. A project could be roughly sized by "bricks required"(if the project is a wall), but very few tasks in programming are like that. I'll be asked how long something will take to produce, not how many lines of code it will have in the end. Line count is certainly a horrible measure generally, but it may not be a horrible measure for a given (programmer, language) pair, because most programmers have a certain style and may have a fairly standard rate of useful expression per line (or something like that, I just made it up). However, without knowing either the programmer or the language, just raw line of code count is meaningless. People spend money on software because of what it usefully does for them, not because of the LoC. And yes, I did read that far.