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

Apple Briefly Paused Work on New Features for iOS 18 and macOS 15 to Clean Up Bugs

Bubble99 said:
You mean Apple has a shortage of software engineers not a money problem.
Click to expand...

I would clarify that to “Apple has a shortage of engineers who understand the code”. My guess is that with industry turnover, people tasked to fix the bugs probably have no idea how the code they are looking at even works let alone what’s wrong with it.

I’m speaking as a software engineer with close to 25 years of experience.
 
  • Sad
Reactions: maxoakland
Bubble99 said:
You mean Apple has a shortage of software engineers not a money problem.
Click to expand...
They apparently don't have people to coordinate the projects, or they don't do a good job of it.

They also don't have a person in charge of products who can look at something and tell them, "this is a piece of crap! look at this! do it right!".
 
  • Like
Reactions: maxoakland
I think you are right, someone needs to tell them when something is a piece of **** or why did you do it this way.

For example something that doesn’t directly affect me was the watch face swipe change. Why didn’t they put a toggle to allow swipe to change so people could revert the old way if that’s what they wanted?

Why change a whole feature and say “this is the way it is now”

Doesn’t make sense. The brightness levels are **** to. 15% 20% 25% are your options. If you don’t like it and can’t see ****, **** you.
 
  • Disagree
Reactions: ProfessionalFan
Morac said:
I would clarify that to “Apple has a shortage of engineers who understand the code”. My guess is that with industry turnover, people tasked to fix the bugs probably have no idea how the code they are looking at even works let alone what’s wrong with it.

I’m speaking as a software engineer with close to 25 years of experience.
Click to expand...
The pay to software engineers is not high enough at Apple and that why so many of them are leaving and such turnover?
 
  • Sad
Reactions: maxoakland
redheeler said:
Yes please...I don't even update every year anymore, and yet have to face stupid Appleisms like Xcode being incompatible with my less than one year out of date OS.
Click to expand...

Well compared to say Windows it still way less buggy. I would take iOS or MacOS any day over say windows of how buggy windows is And bigger bugs in windows.
 
There is bug where Hot Corners stop working intermittently - you move the mouse to a screen corner and nothing happens. The workaround is to close the laptop lid and open it again.

This bug has been present in all versions of macOS since I switched to it 11 years ago. Every release I hope it will go away and it never does... so I just keep closing and opening the lid few times a week.
 
  • Wow
Reactions: maxoakland
dzankizakon said:
There is bug where Hot Corners stop working intermittently - you move the mouse to a screen corner and nothing happens. The workaround is to close the laptop lid and open it again.

This bug has been present in all versions of macOS since I switched to it 11 years ago. Every release I hope it will go away and it never does... so I just keep closing and opening the lid few times a week.
Click to expand...
I thought this was only me?

I got my first Mac after switch from windows last year and saw this.

I thought this was only me………..

I don’t have to close the lid but open another app and start toggling between the 2 then it starts to work……………..
 
  • Like
Reactions: maxoakland
Haiku_Oezu said:
Didn’t we hear this before?
I would fully welcome a iOS and macOS release with zero new features, not “none to little”, literally zero
Click to expand...
Wouldn't "no bugs" be a really new, innovative feature? :cool:

I guess software development and software users have moved into the realm of sports fans. The games don't matter so much, except to the gamblers, because everything is about some fantasy league and some nebulous future.
 
  • Like
Reactions: Haiku_Oezu
wankey said:
This article is mostly ********. 1 sprint is 2 weeks minimum. If they're running agile sprints, it's at least 4 weeks (2 sprints) to get stuff done.

Article is obviously written by non techie.

What really happened was probably this, upper management had a meeting with QA and top level software execs, started identifying a huge surplus of bugs (I'm sure Apple employees themselves have noticed)

They then spend several weeks to months prioritizing these bugs, making sure they are carefully identified and easily produced. Then have an action plan to fix these in the next quarter.

Some bugs take minutes, some bugs take weeks, some need some major rewrite.

I'm guessing the week downtime is basically to do the first part, stop production of new bugs, have the teams sit down and carefully analyze areas of improvement, parts that need to be fixed, rewritten, refactored, then start up the development again.
Click to expand...

There's no golden rule that says sprints need to be a fortnight's duration (or longer) to qualify as "agile". The essential point the duration of sprints is that (a) incorporates feedback loops with turnover/feedback as quickly as practicable (b) it fits with organisational practice – no point in working to 1 week sprints if reality means teams can't get feedback that quickly.

See below:

scagile.io

Being more successful with 1 week sprints • scagile Blog

What is the perfect scrum sprint length and why a 1 week sprint is much more effective and increases the team velocity enormously!
scagile.io scagile.io
 
  • Love
  • Like
Reactions: drumcat and JustAnExpat
T0mmyR0t said:
There's no golden rule that says sprints need to be a fortnight's duration (or longer) to qualify as "agile". The essential point the duration of sprints is that (a) incorporates feedback loops with turnover/feedback as quickly as practicable (b) it fits with organisational practice – no point in working to 1 week sprints if reality means teams can't get feedback that quickly.

See below:

scagile.io

Being more successful with 1 week sprints • scagile Blog

What is the perfect scrum sprint length and why a 1 week sprint is much more effective and increases the team velocity enormously!
scagile.io scagile.io
Click to expand...
No kidding… how do they know they're not running Kanban?

Sprints are inefficient because you're sizing by guessing. If you're still running sprints, it's habit, because it's not ideal.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back