> I don’t get it - asking ‘can you reduce line item n by x’ is exactly the same thing as ‘can you reduce the bottom line by x’
"Can you reduce bottom line by x" is like saying, "the documentation is a bit vague, can you improve it please?"
"Can you reduce line item n by x" is like saying, "there's no way the user could possibly intuit that the sampling period may be truncated to precisely hit the target value after the specified duration. Given that the programming language itself has no specification, this longstanding behavior must be explained clearly in the user docs."
Which response do you suppose will be more likely to lead to an improvement in the docs? It's probably the one that shows evidence you know your domain and how to assess quality there.
Of course, that analogy is the dream. In reality the car salesperson will come back with the reduced line item but with adjustments somewhere else. And it's hard to keep track of because, for example, how would an increase in the down payment affect your idea of the "total bottom line?"
This would be like a developer countering by saying, "Ok, but to clarify that section of the docs I added threading to the event loop." And then every single developer suddenly becomes some kind of darkworld saboteur, and you finally give in by saying, "I guess this is just how software gets made..."