I have no idea how Apple prioritise their bug fixing, but it really looks to me like bugs only get fixed when adding new features, if at all.
This is such a trivial big win as well, create a software dev team to focus on the outstanding bugs. Head it with one or two senior developers, make it the first step in onboarding new developers. What a great way to learn, and make a difference.
This is not rocket surgery, and Apple really do have a bad reputation here, even with the muggles.
> This is such a trivial big win as well, create a software dev team to focus on the outstanding bugs. Head it with one or two senior developers, make it the first step in onboarding new developers. What a great way to learn, and make a difference.
Sounds nice on paper. In practice, the seniors assigned to the team will see it as a career dead-end (because fixing bugs doesn't get management attention, but flashy new features do), juniors lack the experience to avoid edge cases or to navigate the project structure, and the seniors/intermediates on the "actual" development team don't have time to waste on reviewing and aiding code of juniors and bugfixes because then they have ownership over that...
This is such a trivial big win as well, create a software dev team to focus on the outstanding bugs. Head it with one or two senior developers, make it the first step in onboarding new developers. What a great way to learn, and make a difference.
This is not rocket surgery, and Apple really do have a bad reputation here, even with the muggles.