Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

ChrisA

macrumors G5
Jan 5, 2006
12,626
1,773
Redondo Beach, California
You’d think they are big enough to have two separate teams, one focused on fixing things and another one developing new things?
That does not work. Software engineers tend to be specialists in a particular piece of software. It takes a long time to understand how, for example, a file system works internally. You have to do that first before you can fix it or extend it.

What you don't want is twice as many people where each has half the experience with the section of the software.
 

antiprotest

macrumors 601
Apr 19, 2010
4,109
14,679
Apple has the resources to push out low bugs software. And Apple has the resources to fix bugs and go full speed on developing new features at the same time.

I consider pushing out high bugs software, and having to slow down new features to fix bugs, FAILURE. It's a problem of leadership and organization, probably.

Of course, many people disagree with this, but I don't care and I refuse to change this opinion and refuse to accept any excuses or reasons.

I would not be satisfied unless we have both speedy bug fixes (or few bugs to begin with) and full speed development on new features.

Not that it makes a difference to Apple what we think, but this is what I think anyway.
 

JustAnExpat

macrumors 65816
Nov 27, 2019
1,009
1,000
Apple has the resources to push out low bugs software. And Apple has the resources to fix bugs and go full speed on developing new features at the same time.

I consider pushing out high bugs software, and having to slow down new features to fix bugs, FAILURE. It's a problem of leadership and organization, probably.

Of course, many people disagree with this, but I don't care and I refuse to change this opinion and refuse to accept any excuses or reasons.

I would not be satisfied unless we have both speedy bug fixes (or few bugs to begin with) and full speed development on new features.

Not that it makes a difference to Apple what we think, but this is what I think anyway.
How would Apple be able to do both at the same time, assuming they are using some type of Scrum methodology?
 
  • Like
Reactions: Jumpthesnark

JustAnExpat

macrumors 65816
Nov 27, 2019
1,009
1,000
My thought exactly. Their “brief” bug bonanza was WAY too brief.
Doesn't make sense to me for a week long sprint to take place.

Day 1: Identify and sort the bugs using some agreed to criteria
Day 2 - 4: Fix the bugs. Hope new bugs won't get introduced
Day 5: Debriefing day on what went right and wrong

So three days to fix all the bugs in iOS 18?
 

Mr. Dee

macrumors 603
Dec 4, 2003
5,990
12,833
Jamaica
We need another Snow Leopard and iOS 12 like release where the focus was just optimization and bug fixes. These operating systems are super feature rich at this point where one year where there is little to no user facing features would not be a crime. Just make stability be the feature. Then follow up release, you can go at it.
 

tweaknmod

macrumors 6502
Feb 13, 2012
491
1,643
Ottawa, Ontario
I made a thread related to this a while ago:

Unrealistic — but fun — idea...​

There're many comments, in various threads, wishing Apple would slow down, or even stop, adding software features, and focus on tightening-up their software.

Many often cite Snow Leopard as being the heyday for Apple's "it just works" age, and I'm sure there's a similar reference for iOS. As Apple continues to strive to add more and more bells and whistles to their software, more and more bugs and inconsistencies are bound to come up.

As far as I know, this is somewhat inevitable with such a fast development cycle. I've heard people blame Apple's focus on pleasing shareholders first, and consumers second — drive more sales of the newest hardware models through software updates that require new purchases. I'm sure it's more complicated than that, but you're here for a crazy and fun idea, not my ignorant speculation...

The idea...


Apple announces, in typical cryptic fashion, that the Apple polishing cloths will no longer be available until further notice.

Later, when it comes time for WWCD of that year, the theme is some clever variation on 'the year of polish' or 'our lineup has never been shinier' or something actually good.

The point:

Apple announces that the polishing cloths were no longer available to the public, as they were needed internally. They needed them so they could spend a full year focused on 'polishing' their existing offerings (not literally, of course - I'm talking software).

They announce the name of the new update to macOS as [clever name], and a video plays with a reel like: (with accompanying iOS and iPadOS versions)

New features: none!
Added functionality: none!
Pretty novelties: none!
...
Bugs fixed: 23,434,543
Consistency improved: 3,567,343 instances
Energy efficiency: up 363%
Crash decrease: 476%
User satisfaction: +254%
etc... (any metrics which can actually measure these improvements)
  • They talk about taking everything they already have, but has objectively needed more time to polish and refine, and then re-offering it in an update which re-commits to the principles of quality over quantity, reliability, and "it just works".
  • They talk about longer lasting hardware (due to more efficient and optimized software), in order to help with e-waste.
  • They talk about staying true to the principles which made them the most valuable company in the world.
  • They talk about defining their software in the same way they have done with their hardware: polished and refined to a level unmatched in the industry.
Then, at the end, they show a room full of Apple employees polishing MacBooks, iPhones, watches, and iPads. All getting shinier and shinier...

"The polishing cloths will be available again on [DATE]." <– the release date for the 'new' OS.

Shareholder relations...


There would need to be a separate, specific, presentation directed at shareholders, so they don't think Apple has gotten lazy and will lose sales.

This would be a long-term gain to offset the downturn in hardware sales, and to get fans to fall in love with their products again. If they pulled this off, then it would, hopefully, pull more and more people into the Apple ecosystem due to it's ease of use, consistency, and reliability — all things which used to be associated with Apple far more frequently.

Not gonna happen!


I know. I just thought it would be fun to write out and discuss.
 

ss2cire

macrumors 6502
Jun 18, 2008
338
462
Earth?
Doesn't make sense to me for a week long sprint to take place.

Day 1: Identify and sort the bugs using some agreed to criteria
Day 2 - 4: Fix the bugs. Hope new bugs won't get introduced
Day 5: Debriefing day on what went right and wrong

So three days to fix all the bugs in iOS 18?
Fair points, but who's to say it was literally only a week? what if they did prep the week before and a debrief the following week?
 

JustAnExpat

macrumors 65816
Nov 27, 2019
1,009
1,000
Fair points, but who's to say it was literally only a week? what if they did prep the week before and a debrief the following week?
Even if it's two weeks that still wouldn't be enough time to squish the bugs, especially in software as complex as an operating system.

But are they allowing bugs to pile up and having a special "cleaning sprint" to remove the bugs :O
 
  • Like
Reactions: ignatius345
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.