Yep productivity is a complicated tricky subject. And yes if your work generates zero $ then your productivity is zero by my definition. Or actually negative if

Yep productivity is a complicated tricky subject. And yes if your work generates zero $ then your productivity is zero by my definition. Or actually negative if you spent money doing it. This is because I am thinking like a business person. However you can use other definitions of productivity of course. You could define it to be issues fixed per month for example. However that is even more tricky. Because different issues require different skills and effort. And to make it even more complicated, an issue that is easy for Ada to fix might be hard for Bob. Simply because Ada have fixed similar issues before. So Ada using C++ might be way more productive than Bob using Python. But that doesn’t prove that C++ is more productive than Python of course. Which is why studies using the same people to solve the same problem twice using 2 different languages to “prove” that language A is more productive than language B is non-scientific BS. Obviously solving the same problem the second time gives you a huge advantage. No matter the language you use. And obviously the people involved will know one of the languages better than the other. Which again makes the whole experiment non-scientific BS. So yes productivity is a complicated slippery tricky thing to nail down. We all think we know what it means but the more objective/precise we try to be the more slippery and complicated it gets :)