Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Seriously. I'm sure Macrumors won't be the only one, but why ruin this guys reputation/career in such a public way? He's human! Humans make mistakes! There's no way to even know if this actually one mans fault. How could he possibly test millions of phones being used in different ways?

People act like the guy is running the country. It's just a damn phone, give the guy a break! (I love my phone too, but come on)

- Agreed. And, "engineers who test the new software often are unable to get the latest iPhones until they are available to customers" ? Good God..
 
Seriously. I'm sure Macrumors won't be the only one, but why ruin this guys reputation/career in such a public way? He's human! Humans make mistakes! There's no way to even know if this actually one mans fault. How could he possibly test millions of phones being used in different ways?

People act like the guy is running the country. It's just a damn phone, give the guy a break! (I love my phone too, but come on)

Wait until he works for a Pharmaceutical company and signs off to release a drug and your family take that drug. His job is QA which should ***** catch any mistake. QA fails, product fails.
 
People are so quick to form some sort of narrative about a single person causing a problem, but that's not how reality works. The problem is probably a structural one, or even more likely, a coincidental one.
 
Wait until he works for a Pharmaceutical company and signs off to release a drug and your family take that drug. His job is QA which should ***** catch any mistake. QA fails, product fails.

Regardless we don't need to know this guys name. It's none of our business. If this guy is responsible it's up to Apple to take whatever action they deem necessary. The general public doesn't get to discipline individual employees at a company.
 
Secrecy has its price!!

Scapegoating is a pointless exercise. The root cause of the QA problems Apple has every fall are the rigid deadline due to the iPhone event combined with the lack of external testing starting in early August onwards necessary to keep new features secret. Until those issues are dealt with there will be bugs no matter who is in charge. Now its quite possible Apple feels that their current way of doing business is worth it from a marketing perspective, black eyes be damned, but that's another issue.

The insane pursuit of secrecy at the cost of keeping employees who really have a need to know in the dark will come back and bite you in the a$$ and cost you $$ in lost value in the marketplace and give you a bad rap with the consumer and eventually alienate enough people that you disappear.
 
This is crazy MacRumors. You'll start a witch hunt. Meanwhile, this guy probably wasn't the actual cause of this issue. Just the one in charge, so it's his head which will now roll. He must be very good at his job in other respects if he's been there since 2000.

Perhaps Apple should post names of their complete quality assurance team so Donald Trump could fire them one by one.
 
According to the Bloomberg report, engineers who test the new software often are unable to get the latest iPhones until they are available to customers, "resulting in updates that may not have gone through tests that are are rigorous as those for the latest handsets," and internal issues can also impact Apple's testing, which may explain how such a significant bug got through the testing process.

Wait... So the manager and his team can't even get a current phone, shoot better yet, a version of each phone that has a different processor and test them to see the effectiveness BEFORE going out the door to the customer? :eek:

So let's just get a bag of parts, turn off all the lights, dump them on the floor, assemble something and hope for the best.
 
I miss you Steve

Steve would have fired this guy right off the bat.

And he would of SERIOUSLY considered getting rid of ANYONE who recommended that they "use something else for their maps app."

Rolling in his grave. Miss you buddy.
 
I thought Maps was Scott Forstall's fault, and his refusal to apologize for that was the reason he's gone.
 
Wait until he works for a Pharmaceutical company and signs off to release a drug and your family take that drug. His job is QA which should ***** catch any mistake. QA fails, product fails.

Nobody has any idea what went on that caused this debacle. Just because some anonymous source goes out of his way to bash this guy doesn't mean it's true. Maybe the anonymous source wants that guy's job. Maybe he just doesn't like him. Or maybe he's right and the guy genuinely isn't very good. We don't know and it's none of our business.

We do know that lots of people were involved in the entire process, so the idea that it is all down to a single guy is utterly ridiculous.
 
I don't think you can blame the Maps fiasco and iOS 8.0.1 on one single person. They'll have had lots of people testing, it wasn't like one single person missed the fact that the update broke two major functions. Poor show on Tim Cook's behalf, he's the man in the charge of it if we're singling out the mid-level guy.

It's concerning the amount of software cockups that are happening at Apple, but perhaps they've pinched a few of the iOS guys to finish off Yosemite.
 
We discussed this in the security lapse thread, the need for increased standards and accountability to those standards to kill the lower level issues that will eventually fix the bigger ticket issues. I'm not saying the dude needs to get fired but he's botched two major releases to the public, his skill set and talents should be evaluated for alignment with the standards of Apple employees and either re-train or find someone that more closely aligns with the Apple standards.

Where I work we have high standards and very little margin with the public or oversight agencies. We manage low level trends with higher levels of management to ensure the proper processes and standards are used and adhered to. I think the leadership change at the top has revealed how a nicer more people friendly CEO has allowed standards to drop through all layers of the company. Being an outsider, its difficult to observe how the accountability model is enforced and maintained, but there are gaps and a need for those gaps to be identified and managed better. Apple seems very collaborative and perhaps needs a more directive approach in the short term.

Actually, as an outsider, I would say Apple isn't collaborative enough. Hence the inability of the testers to have the capability of testing on latest hardware. And the reported issues of one group testing specific things, issuing an ok and another group noticing breaks, yet it seems theses groups do not talk to each other.

I worked in software dev for 25+ years. It's essential that all groups actually TALK TO EACH OTHER. I think Apple's penchant for secrecy is reaching up to bite them in the a$$. Secrecy if great for generating marketing hype. But not for developing, testing, and actually rolling out quality software. As Apple grows this 'secrecy' environment is beginning to show its flaws. Frankly I'm surprised it has taken so long for this to happen.

That being said, I don't know if this guy's head should roll. Depends on whether he tried to change the culture, whether he was too complacent, on whether, his team is actually functional... Lots of 'what if's'. But he may well be incompent too. hopedully Apple will make the right decision. Fire him if he is incopentant, listen to him if he tried to change things.
 
Bad form, Juli Clover. It seems that the Macrumors staff needs to come up with some editorial guidelines.
 
Looks like they found Oliver North at Apple.
Poor guy. He'll probably get his golden parachute and be on his way.

*Apple is praying this puts their consumers as ease...
 
"He has to be fired." Multi-million peoples were stranded without cell reception for hours.

A maximum of 40,000 people were affected, a tiny fraction of the people who own an iPhone.

Remember....update 8.0.1 didn't break every phone it went on.

This guy made 2 mistakes in 2 years, that's not a bad record, give him a break.
 
Remember....update 8.0.1 didn't break every phone it went on.

It broke every new phone (6/6+) it went on which is even worse in terms of PR. Either way, no one even knows if this guy was responsible. People calling for his firing might want to actually know the facts first.
 
#TimMustGo

If you're a chef baking a cake & the boss comes in the kitchen and asks how it's going,
and you tell him it isn't ready yet but he serves it anyway, how is that the chef's fault?!?
 
Even if there is 100% cast iron evidence that this person was responsible for the problem then it still isn't polite to name and shame. If anyone has to do that it should come from Apple, ideally Tim Cook himself, but I doubt he / they would single out an individual person.

Sometimes QA does miss things, throw in greater pressure and there is the greater risk for things being missed. We're only human after all and we all make mistakes.

Their internal teams not having access to new devices to test on is very dangerous indeed. I understand the desire for secrecy, but when you encounter a problem as serious as this, I think you need to re-evaluate things. If you do not trust your QA team to keep quiet about devices then you need a set of people who will respect the secrecy.
 
Macrumors needs to name the person responsible for naming the Apple guy.....then HE could name other names....
I want my iphone plus.....i won't bend it and it will be loved
 
Steve would have fired this guy right off the bat.

And he would of SERIOUSLY considered getting rid of ANYONE who recommended that they "use something else for their maps app."

Rolling in his grave. Miss you buddy.

And Steve would have been wrong. It takes a real man to admit when a mistake has been made and apologize for it. Tim Cook is a man in ways Steve Jobs never was.
 
A maximum of 40,000 people were affected, a tiny fraction of the people who own an iPhone.

Remember....update 8.0.1 didn't break every phone it went on.

This guy made 2 mistakes in 2 years, that's not a bad record, give him a break.
At the same time just because 40,000 is a small percentage doesn't make it a small number, nor does it have anything to do with te level of how problematic an issue is for those people.
 
#TimMustGo

AGAIN, if a chef is told by his boss to bake a cake, but the oven he's given doesn't work,
HOW IS THAT THE CHEF'S FAULT?!?

The problem is whenever Tim's interviewed, he always goes to the outlets
that will slather his ass & wont ask the tough questions
so they can continue to be on the VIP seating list at Apple events and get pre-release hardware to "review".
Instead, they pitch him softball questions whose only answers
let him spout his PR BS as if he were onstage at the Yerba Buena Center.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.