I guess I was trying to claim that in a lot of places there isn't such a person. yeah - if an application company runs up against a poorly designed OS interfac

I guess I was trying to claim that in a lot of places there isn't such a person. yeah - if an application company runs up against a poorly designed OS interface - they usually aren't aware, or just back away slowly. they don't have the scope or mandate to pursue it. that kind of behavior often extends to library dependencies, and even internal interfaces that the company should ostensibly own. its not so much an administrative problem as a desire to limit spending and time on software and do a kind of agile mvp glue job over an unbounded number of external dependencies. that often leads to an unmaintainable hairball. but if the alternative is to hire a bunch of really experienced developers and let them 'do the right thing' for 5 years... even if you do, there is a still a good chance that the output isn't gonna be that great. software people lost a lot of credibility with that model. we've probably swung too far in the other direction