> "Somewhere between the janitor and the CEO, reasons stop mattering," says Jobs, adding, that Rubicon is "crossed when you become a VP."
> In other words, you have no excuse for failure. You are now responsible for any mistakes that happen, and it doesn't matter what you say.
http://www.businessinsider.com/steve-jobs-on-the-difference-...
A VP’s job is to find those people and give them the correct incentives. The VP has the rights to hire new people and restructure teams. The VP should use those leverages.
At the VP level, how a particular codebase or team is doing simply doesn’t matter, as the VP has all the leverages for organizational shifts. Blaming a codebase or team only makes sense if the whole company cannot produce quality code, and it’s impossible to hire new employees that can. I am pretty sure that this is not the case for Apple.
1. The system uses a database that is not duplicated.
2. The system has no monitoring.
3. The web frontend is written in PHP.
What do you do?
To fix 1, duplicate the freaking database.
To fix 2, add some freaking monitoring.
3 is presumably the hardest to fix. But remember that you get really high pay and you have a lot of engineers. What did the engineers at Facebook do? They fixed PHP.
Do you blame the previous team that made this horrible system? No. No. No. You own the system now. There are valid engineering approaches to fix. So fix it. It can take a while, but eventually you can fix it. In the worst case, you will have to rewrite. But that's still a feasible thing to do.
Now substitute technical lead with VP.
1. You cannot simply put your standard programmer(or any number of them) with undergrad (even with superb knowledge) of combinatorial algoritms in the former position of someone with a graduate degree that focused on algorithms engineering who didn't give a damn about even the smallest aspects of software engineering like version control or documentation. You have even less ability to do this on an embedded device for numerically sensitive algorithms. I've been in this position (except with a far broader background in mathematics and algorithms engineering) at least a couple times with other engineers with graduate degrees in the requisite areas and (I'm not exaggerating) it is truly a fucking nightmare.
2. Just because you are a VP doesn't mean your managers are willing to approve the amount money that goes into a number of algorithms engineers fixing or rewriting a product that just barely functions well enough. I am incredibly close to a couple people that are VPs at companies with ~10,000 people and you would be surprised with how little power they can have on hiring sometimes. Companies are not bottomless pits of money and the people at the top usually treat it as such.