The author isn't a programmer, and as I read more it became clear the audience isn't practicing programmers. (In other words I don't think this is HN material.) I'm not sure who the audience is supposed to be, though. I'm left with the sense that it's the non-technical manager of the programming team, and the article provides a justification for them to force D on the next project.