No biggie. Unfortunately the way the media reports things a lot of people think Ive is responsible for all of iOS not just interface design.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple iOS 8.0.1 Issues Linked to Maps Debacle, Same Manager Oversaw Both Projects
- Thread starter MacRumors
- Start date
- Sort by reaction score
No biggie. Unfortunately the way the media reports things a lot of people think Ive is responsible for all of iOS not just interface design.
I'm really familiar with this, because I'm a QA Manager at a software company.
This happens at virtually every single software company in the world:
1. Product Managers want to release on the date they promised, and pressure everyone to fix things as fast as possible.
2. Developers fix bugs BUT INTRODUCE NEW ONES IN THE PROCESS. This is called regression.
3. QA has tested nearly everything once, but it is impossible to test everything again for every single change a developer makes.
4. Eventually the release date rolls around, and each release has some level of bug risk due to regression.
There are tons of variables that can account for buggy software being released:
1. Product Managers - This is probably the main reason. They always plan for a ton of features but never plan for the time it takes to test it and retest it. They set a hard release date, then when it comes time to test/retest, they say "RELEASE IT!". They often do this by simply marking P1 bugs as P2/3s.
2. Quality of developers - Good ones write their own tests and test before QA to ensure what they write is high quality. Bad ones don't even think about QA. Developers are the only people that create bugs
3. Management - If this guy was managing 100+ people, there is no way he can be responsible for this specific issue. He's probably got a layer of management below him, and another layer of QA people doing the actual testing. At that point, he's simply trusting that the work they are doing is valid. I guarantee you he isn't personally deep diving in each test case himself to ensure quality. If anything, fault him for his hiring ability.
The simple truth, all software is buggy to varying degrees. You can never know what you don't know, until you know it. Maybe they didnt have a test for this bug. Maybe they did, but it passed earlier, but then got broken again at some point. We don't know the situation.
Excellent post. The one issue that you allude to is trusting the work the group is doing is valid. While this is important, there has to be ways for the manager in question to validate the processes and results their selves. The old "I know because I looked". Trust is important but when that trust turns to abdicating authority to help meet deadlines and get out of the way of creation, standards will start to erode to help facilitate meeting the deadline. I'm sure all of us have said, if my boss would just let me do things how I know how to do them I can get the job done... That manager has to ensure corners aren't cut to ensure deliverable meets the company's standard of excellence.
I just get this feeling with such an amazing staff and company, Mr. Cook simply had to get out of the way to allow this hand picked staff to do their jobs. At first the standards were closer to the previous CEO, but eventually have dropped to where Mr. Cook allows them to be.
If any part of this article is wrong I smell a lawsuit coming macrumors way.
This site has started to become less and less about journalism and more about click baiting. Maybe some common sense is needed before "reports" like this are posted in future.
This site has started to become less and less about journalism and more about click baiting. Maybe some common sense is needed before "reports" like this are posted in future.
I've been on MacRumors a long time - I think the posting of this story was not well thought out. Sure Bloomberg posted it, but that doesn't mean it needs to be perpetuated. Especially given that I'm sure no single detail was verified.
As people have posted before, a lot of people could be to blame for any issue on an engineering project. To just perpetuate this "juicy gossip" is poor taste in my opinion.
I hope this gets deleted from the front page and this thread gets deleted.
As people have posted before, a lot of people could be to blame for any issue on an engineering project. To just perpetuate this "juicy gossip" is poor taste in my opinion.
I hope this gets deleted from the front page and this thread gets deleted.
I'm really disturbed that MR and other outlets posted his name. I'm glad it was quickly removed, but it represents a serious lack of judgement IMO. Witch-hunting like that is not cool. And no, "they did it, too!" or "But they said it first!" is not an acceptable excuse. There are a million and one reasons why the 8.0.1 bungling could have been completely beyond his control, many of which have already been pointed out.
Steve had to go, that's the best thing that happened to him and Apple. But seriouly, two of the biggest mistakes apple has ever made were under Cook's reign.
Why not? People who screw up like this deserve a PSA so that other companies know to beware.
Well, yes, MR has turned into a bunch of second rate click-baiters.
"Your honor, I defamed the plaintiff because Bloomberg did it first."
They reposted news that was already spreading. Plenty of sites do thst automatically just by getting a feed from major news sources like Bloomberg--as in syndication. Good luck enforcing anything there on anyone beyond the original news content creator.
Well, if you're saying that MR has descended to the status of serving as a second-rate syndicator and click-baiting, I can't disagree.
A rumors site actually posting something that is more than even a typical rumor? What are people expecting exactly?
He doesn't deserve to be made a public scapegoat, especially on the word of anonymous sources.