Well having done that I get the strong impression that he is in control of his product "all the way down". That is rather significant and marks him out as an unusual case. Most developers have to write code that still works after a third party changes the behaviour of the OS that wasn't documented in the first place. You can't "inspect quality into" that, simply because it isn't your code to inspect, let alone modify, so the financial trade-offs are completely different.
However...
What *I* meant was simply that "inspect X into Y" is a usage that grates horribly to my ear. Inspection is a non-mutating operation in my book, so the statement violates const-correctness. However, that's a minor point and I see this morning that the sub-thread probably doesn't need any more fanning so I will merely agree with...
...and try to run away. :)