this post was submitted on 06 Jan 2025
24 points (92.9% liked)
Apple
17650 readers
141 users here now
Welcome
to the largest Apple community on Lemmy. This is the place where we talk about everything Apple, from iOS to the exciting upcoming Apple Vision Pro. Feel free to join the discussion!
Rules:
- No NSFW Content
- No Hate Speech or Personal Attacks
- No Ads / Spamming
Self promotion is only allowed in the pinned monthly thread
Communities of Interest:
Apple Hardware
Apple TV
Apple Watch
iPad
iPhone
Mac
Vintage Apple
Apple Software
iOS
iPadOS
macOS
tvOS
watchOS
Shortcuts
Xcode
Community banner courtesy of u/Antsomnia.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don’t think that’s necessarily a bad thing. The unfortunate reality is that any sufficiently large software project with a lot of engineers touching the code is going to have bugs. At least someone at Apple is trying to fix these as opposed to ignoring/pretending they don’t exist
Except that these bugs are being found after release, which means that alpha and beta testing is not finding these bugs and the internal testing process isn't finding them before release either.
I can’t speak specifically to apple’s testing process, but as someone who has worked in software QA, it’s simply not possible to catch all the bugs. Obviously no one wants bugs, so I’ve witnessed past employers try everything from adding more manpower to attempting engineering culture changes to adding public beta programs. None of these meaningfully reduced production bugs. If you or anyone else knows a better way, I’m listening :)
@cantankerous_cashew @apple_enthusiast Especially when it’s being delivered to the masses. We’re not talking about a couple 100,000, we’re talking millions.