Completely disagree. Can't put it more plainly than as satire: "Dear Programmers: Stop Giving Me a Ballpark Lines of Code Estimate Once a programmer and I ar

Completely disagree. Can't put it more plainly than as satire: "Dear Programmers: Stop Giving Me a Ballpark Lines of Code Estimate Once a programmer and I are past finalizing requirements and have selected a stack (or they are contributing to an existing project) I need to know exactly how many lines of code they will be writing for the functionality. I need this for my accounting requirements. Stop giving me ballpark estimates like "a few hundred" or "thousands" or "well, it depends on whether I can use an external module, can I get back to you?" That is unacceptable. Once we have agreed on requirements, I will be paying for your "discovery session" where you must sit down and discover exactly how many lines of code you will be writing. At the end of the day, you're the one writing it. Only you know what that number will be. I require an exact number of lines of code that I will be paying for. 7,428 lines of code is not the same as 9,416 lines of code. The difference between 7,428 and 9,416 is the same as the difference 3 and 1988. Likewise, the difference between 76 and 7,428 or between 7,428 and 14780, or between 458,583 and 465,935 LOC are exactly the same. (in each case it's a difference of 7352.) If you expect me to pay you to discover my requirements, do you expect me to be able to pay you to discover your requirements? Or is there some sense of scale that you can have some kind of understanding of?" According to the author, there is not.