Never believe stories like this, measuring productivity is an impossible problem. Microsoft spend something in excess of 3 billion dollars trying to quantify productivity in the 90s and they couldn't do it. One of my college professors worked on this exact problem for the Army in the 80s, they created a formal domain specific language for quantifying employee productivity it took them 20 years and several hundred mil…
This is what makes me so uncomfortable with hiring software developers. I don’t know how good of a job they’re doing, or what’s taking them so long, or whether another group of developers would do a better job faster. If I hire painters, I can tell if they’re doing a good job by looking at it. I know what’s taking them so long. They’re using slower drying drywall compound, or they’re having to mask off because they’r…
It's easy to make a job look good for a day, but on some jobs if you skip the prep work, lining, filling, priming, undercoat, additional coats, clearcoat, and finishing the paint job is going to look pretty bad after a year. You can't tell how good a painter is unless you know a bit about painting things.
The same is true of software. In order to know if a developer is productive you really need to know quite a lot about the domain they're writing software for.