Here is an easy workaround to the "programmer = resource" question. If I make 50/hr as a programmer than the cost per day of me as a programming resource is 508

Here is an easy workaround to the "programmer = resource" question. If I make 50/hr as a programmer than the cost per day of me as a programming resource is 508 = 400. Now we can add an "Efficiency coefficient" to account for how skilled I am. So, the default cost for our programming "resource" per day is: ResourceCostPerDay = HourlyRate8EfficiencyCoefficient If this coeff. defaults to 1 then in my example: ResourceCostPerDay = 5081 = 400 If I am really super good we can change this to have a coeff. of 1.5 so ResourceCostPerDay = 5081.5 = 600 If I totally suck we can change the coeff. to 0.5 so ResourceCostPerDay = 508*0.5 = 200 So by having a simple "efficiency coefficient" the resource cost for a programmer can indeed be modeled fine, so with due respect to the person who posted this article, he is mistaken: a programmer or engineer (speaking as a test automation engineer myself) can indeed by quantified quite well as a "resource" like any other "resource" such as the number of application servers a company has. Reductionist? Yes. But this is a reductionist universe. Deal with it. :-)