Sure security is important but integrity is too.
Tangential story - 12-13 years ago I was a burgeoning and super eager software dev that moved to Seattle to be closer to "the scene." tenderlove's content was a major reason for me going there and I poured through his posts learning way too much about Nokogiri, Active Record, and much much more.
I went to every Ruby meetup I could get to out there and I remember one in particular, a Seattle RB meetup, in the Substantial office. It was a pretty small group, at most 15-20 people.
I was with a coder buddy but knew nobody else. We were all just drinking pints of Manny's beer and eating pizza from Big Mario's or something. Ryan Davis (the creator of minitest among other things) was doing a presentation on Unicode.
Aaron Patterson (tenderlove) was cracking jokes at every opportunity. At one point I asked a relatively naive question and Aaron _tenderly_ answered in joke-form response. I felt such a _part_ of the scene then. Aja Hammerly was super engaged in the presentation, I think even Ryan Bates and/or Geoffrey Grosenbach were there.
It was quite surreal to be in this dream-like state around giants and heroes just doing what they were doing and being so inclusive. It seemed so normal but became a core memory.
Thanks for everything Aaron, you've truly been an inspiration!
For the longest time my process while traveling was importing onto my iPad or occasionally my iPhone since I didn't have a personal laptop, just a Mac Mini at home.
For the 99.999% of us who just use our phone, nothing to worry about.
Scared me for no reason! =P
So much wasted time, now I just use image capture to import and organize directly.
Still get errors from time to time.
Apple needs to hire more quality control, their software integration is going from a positive to a negative.
Seamless integration was a large part of Apple's initial hook, and continues to be a part of their drive to push services, it should be a priority.
(sorry not sorry)
I got similar symptoms as mentioned, I suspected AFS+, but what do I know. It has happened on at least 3 iphones (pros), now when I think about it, I don’t remember any iphone I haven’t have troubles with. Having 5000+ images (non-raw) where 5-10% are corrupt is infuriating, but I just stupidly buy another iphone every year (the most expensive one).
Re-importing images 10-100 times could sometimes extract a few additional images, but the phone just disconnects after a while when running such scripts.
Photos does a lot of extra work on import (merging RAW+JPEG pairs, generating previews, database indexing, optional deletion), so my guess is a concurrency bug where a buffer gets reused or a file handle is closed before the copy finishes.
Rare, nondeterministic corruption fits the profile.
A better way to have further narrowed down the problem down to Actually iPhoto would've been to do the same tests with a USB-C card reader plugged directly into the Mac, which would've eliminated cables, hubs, and camera hardware/software/firmware as possibilities.
It's worth noting that searches show that OM-1 USB support is imperfect, the camera manual addresses that "USB transfers aren’t guaranteed in some setups", and user consensus seems to be to use a card reader for reliable file transfers.
But good gravy that troubleshooting path got expensive real fast. Replacing the laptop and the camera? Why not start by trying something other than Photos? It doesn’t even need to be a paid product; the Olympus software is free not to mention a good baseline since it - of all the applications - should be able to import photos without corrupting them.
Edit to add: delete on import seems pretty risky. My workflow is to import and only delete from the camera after 1) the imported photos are backed up 2) I’ve done a first pass culling.
I’ve used Olympus cameras for over a decade. Well, the same camera to be honest, a PEN E-PM2. This has only appeared in the past couple of years.
I haven’t seen it on photos from my Canon EOS 80D yet, but I guess it’s time to change my workflow. And maybe OS.
* iTunes/Music app randomly reassign my Album artwork, with different (incorrect) art showing up on different devices!
* Reminders app: shared reminder lists can end up with the name of a different list
* Ghost photos that are deleted from my phone, and come back later.
* Maps, when I say "navigate to $friend" set a route that ended in my own driveway.
To me, these bugs suggest a fundamental design flaw, perhaps they are using a simple Integer as an index rather than a UUID?
Or maybe the database schema are solid, but there's some sort of race condition in their synchronization frameworks and the data is getting scrambled in RAM?
Whatever it is, it's absolutely insane that in 2025 these kinds of bugs are happening.
That's because my worry is corruption of the entire Library, which Photos stores as one gigantic opaque file/directory abomination. My .photoslibrary file is currently 70gb in size, and I'm terrified of what would happen if it becomes corrupted. The Photos app crashes not infrequently.
I've been importing raws for years from Sony and earlier from Pentax and didn't experience it.
In fact searching for "OM image corruption" shows bunch of results not related to Apple Photo.
My guess is that OM has buggy SD driver which starts deletion before actual read finished.
All my photos are managed using Digikam and developed using Darktable. They are also visualized via immich, but immich only has access via a read-only mountpoint.
Everything is hosted locally of course.
I learned the hard way to never delete photos from the SD. Just buy a new one it's so cheap anyway.
Great article by the way, sounds like my kind of rabbit hole :)
Last time I looked (pre-COVID) there wasn't a lot of promising options, and some didn't support HEIF images
On day 7 or so the import failed and all files on the pad got corrupted. But also the SD card got corrupted.
I stopped using the device and the card because I knew not all is lost. I had to buy a new card in SF as replacement. Back home I used a recovery software to check if data is still on the card (I used the same software before on a card that got deleted by another person and I was able to get all images back). I was able to get most of the images recovered and also recovered a few from the iPad. All in all I lost maybe 10 out of a few 100. Now I travel with multiple cards and backup already each night while in the hotel. And I don’t delete the images on the SD Card. I format only when I’m sure I have everything copied and secured.
https://cdfinder.de/blog/files/image_capture_bug.html
(I'm not sure whether this bug has been fixed or not yet, though I think it has been fixed.)
I may be paranoid because I used to handle footage for VFX pipelines and you just do not mess around with those kinds of files. If you lose footage, you are in big trouble.
How do you know? Why do you believe that they're competent on writing security code but not competent enough to write a general purpose app? Is there a different company culture applied to the latter?
Is that a necessary qualifier? I used to get that impression, but on the outside it's gradually become a rarely believable pitch. Without having an iPhone and without having an Apple Watch, and without having already had them years ago, it just seems like I've sort of made the right choice with just mac over the years, and with the latest OS that's becoming just a tiny bit more questionable; their decision making with software seems sus.
Like I've never had to qualify my setup of using a mac for work, Android phone for phone, and I guess Audio Technica for headphones. It's not super nerdy, it's not super integrated, but if I wanted it to be super integrated, "what value would I get out of steeping myself into the Apple ecosystem further" is the question that comes to mind. I also have an old iPad that I tried to make useful, and the iPod nano 3rd gen which was actually amazing, but ultimately was hampered by software limitations that they don't seem to have advanced on much in 10 years. I've always found their discrete hardware products to be amazing in terms of industrial design, but they've never really been compelling in terms of their utility.
That describes 2025 too
Something related: exporting originals from Photos used to give the current timestamp back in Ventura, which annoyed me to no end.
They fixed that bug in either Sonoma or Sequoia (I jumped straight from Ventura to Sequoia).
Anything important should be kept inside the file. Filesystem metadata gets lost all the time, isn't consistent between operating systems, zipping up a folder and extracting it will probably mess up timestampts too.
It's a folder that acts like a file.
Right click > Show Package Contents works, and there's an "originals" folder that should have all your photos in normal everyday files.
There's also the excellent osxphotos utility which can export / backup / migrate photos in and out of apple photos:
No longer have to bring laptop or external drive along for backups
Not a good idea, you are going to have piles and piles of SD cards that will be hard to manage, and you will burn through $$$.
It's strictly for looking and exploring old photos. It doesn't do photo editing (except metadata editing), nor do I expect it to.
I wouldn't say that out loud. Apple's motto with software is move slow, break backwards compat anyway.
Random is random, and random is clumpy, so maybe swapping parts is irrelevant, but... I wanted more detail how often the corruption happened throughout his replacement journey.
edit: also wth i just realized I went to "tenderlovemaking.com" at work. gross. lol.
Edit: Nevermind, the contents are vastly changed. This is like a different stream of input got used, or a buffer was written over with contents from another image.
The software engineering standard at Apple has clearly tanked in the last decade, which is sad because the exact opposite appears to have happened to their hardware.
I would think the diffs would be telling to the right people.
It's on the front page of HN, so that's a good start!
> I stopped checking the “delete after import” button
”Glad” to see it was an actual bug.
Never use the camera over USB, the experience is terrible on everything from Canon to Sony to Panasonic to Fuji.
Don't fight it, just buy that $30 USB hub and get on with your day.
It’s understandable why they changed their name.
I have since turned off iCloud Photo Library, downgraded iCloud (no longer needed so much storage), and started using fully open source photo management with flat files on disk.
Though, considering the macOS 26, it’s likely the Photos app.
* prompts in settings for adding an account recovery contact that never go away, even after months and months of successfully setting it up multiple times.
* OS account profile picture can barely stay associated with the most recently picked option. Happens for non-iCloud local accounts on Mac, happens when I change profile pictures on iOS for iCloud… weird.
* OS account update screens on iPad, iOS, and watchOS will forget that they are in the middle of updating if you navigate away from the settings screen. Thankfully, today they at least recover from it (it’s probably still happening in the background), but it takes several long seconds of spinning for the settings page to remember that it was doing an update two seconds ago before I navigated away from it.
* similar to your ghost pictures bug, deleting a large media file from a media player app moves it to recently deleted, but you can sometimes end up in situations where you can’t permanently delete the file, or it doesn’t show up anywhere but still takes up space. (Talking about 20GB-80GB file sizes where it makes a big difference on OS storage space)
Some of these bugs have been around for a VERY long time.
But the weird thing is I don’t see them in 3rd party apps.
I then subscribed to Apple Music and relied on its matching function. After switching from an Intel Mac to an M2 and redownloading my library from remote, it now believes that each and every song in my library are rented Apple Music copies. Even those it shows as having been added in 2003.
Some songs are missing; some go missing, then inexplicably come back months later. Worse: so far I have found around a dozen which have been replaced by different versions.
It's a real mess.
The Safari reading list can't even sync properly between devices for me. Image Capture ("Keep Originals"??) or AirDrop is a little minimal for such a keystone part of the phone -> computer if you don't want to use Apple ecosystem after.. Let alone the other more complicated issues.
Dropbox doesn't seem to keep timestamps properly either.
I like using filesystem timestamps to sort through things in Finder, and thankfully I like A Better Finder Attributes for being able to batch copy EXIF data into timestamps.
[1] https://www.publicspace.net/ABetterFinderAttributes/index.ht...
Ensuring ZFS has at least 2 copies on physically separate disks and using scrub frequently is the way, right?
Please correct me if I am wrong HN!
Every professional/paid client I shoot for, I do on new SD cards. I have dual slot cameras, so one card just permanently lives in my camera and gets formatted between shoots, the other I treat as a one-time use card.
Doesn't eat into my margin too much, and I appreciate the extra redundancy when dealing with someone else's wedding photos, so that if somehow something went catastrophically wrong with the rest of my back up process and off sites, at the very least I still have the SD card with the RAWs on it.
Also a good idea to copy to multiple locations when importing. When I do professional work and import into Lightroom from SD card I have it set to create two copies - import to my external SSD (the "working" copy) and also copies the files to my NAS (which is then backed up to the cloud).
Nowhere in that process do I ever delete anything.
They constantly ask for an example project, even if it's something that is easily demonstrated, simply by running existing Apple software, and creating a project, would be a huge pain.
They also ignore reports. Very rarely, I may get a ping on one of my reports, asking me to verify that it was fixed in some release. Otherwise, there's no sign that they ever even read it.
I usually end up closing my bug reports and feature requests, after a few months, because I'm tired of looking at them.
It's clear that they consider every bug report to be a burden. That's a very strange stance, but then, they are not a typical company.
I guess you can't argue with the results, as they have a market value North of 3 trillion dollars, but that does not make it any less annoying.
Which means that if that bug has been present since the (now unsupported) Mavericks, tough luck!
What's the point of it? It is well known in the industry they ignore bugreports.
Also, this bug doesn't affect the majority of users, so it won't ever be fixed.
It’s more likely that things will be reversed: the old, battle-tested framework may have bugs, but it’s is less likely to have serious ones.
They should try to hunt down bugs in the existing code. A partial rewrite of parts that historically have many bugs may be in order, but a complete replacement? Unlikely to be an improvement.
I had one case where I screwed up a shoot and thought file corruption might have been involved (it wasn't) Even though I had formatted the card with the camera and shot maybe 5 test shots I was able to recover most of the images with Disk Drill
https://www.cleverfiles.com/data-recovery-software.html
which has both Windows and Mac versions and looking at a sample of them confirmed it wasn't corruption, it was user error.
https://www.reddit.com/r/audioengineering/comments/mftc0g/ge...
I still use Macs because data on a physical disk seems perfectly reliable, but I've been bitten by so many of these bugs in their apps. iCloud files completely disappear, then reappear a day later. Highlight a couple chapters of a PDF in Preview, then reopen the file and they're gone because iCloud thinks the older unhighlighted version is newer or something. Madness. I don't touch any of these Apple services/apps anymore.
There's very clearly a fundamental bug in whatever sync framework they seem to share across everything. It's bad enough to have data disappear entirely or deleted data reappear, but then when data shows up in the completely wrong place, and this has been happening for years and years and still isn't fixed... I don't know what to think.
You're right. There's no other word for it but "insane". They can engineer their A-series and M-series microchips, but it's been over a decade now and their sync is still fundamentally broken.
Not sure when exactly that changed, but it was probably a few OS releases ago?
There are certainly other words for it. Lazy, anticompetitive, disinterested, any of those are more plausible than all of Apple being insane. They sold you a microchip that you knew you wanted, now they are beholden to little else. For over a decade, Apple didn't even offer the iOS APIs for third-parties to implement cloud storage. They know you need their software services, regardless of how shit they are.
Insanity would be a pretty satisfying explanation. Fickleness fits a lot better with Apple's track record though.
Btw, it was fine from withing iTunes, just never stop using iTunes I guess...
The Apple Photos app sometimes corrupts images when importing from my camera. I just wanted to make a blog post about it in case anyone else runs into the problem. I’ve seen other references to this online, but most of the people gave up trying to fix it, and none of them went as far as I did to debug the issue.
I’ll try to describe the problem, and the things I’ve tried to do to fix it. But also note that I’ve (sort of) given up on the Photos app too. Since I can’t trust it to import photos from my camera, I switched to a different workflow.
Here is a screenshot of a corrupted image in the Photos app:
I’ve got an OM System OM-1 camera. I used to shoot in RAW + jpg, then when I would import to Photos app, I would check the “delete photos after import” checkbox in order to empty the SD card. Turns out “delete after import” was a huge mistake.
I’m pretty sure I’d been getting corrupted images for a while, but it would only be 1 or 2 images out of thousands, so I thought nothing of it (it was probably my fault anyway, right?)
But the problem really got me upset when last year I went to a family member’s wedding and took tons of photos. Apple Photos combines RAW + jpg photos so you don’t have a bunch of duplicates, and when you view the images in the photos app, it just shows you the jpg version by default. After I imported all of the wedding photos I noticed some of them were corrupted. Upon closer inspection, I found that it sometimes had corrupted the jpg, sometimes corrupted the RAW file, and sometimes both. Since I had been checking the “delete after import” box, I didn’t know if the images on the SD card were corrupted before importing or not. After all, the files had been deleted so there was no way to check.
I estimate I completely lost about 30% of the images I took that day.
Losing so many photos really rattled me, but I wanted to figure out the problem so I didn’t lose images in the future.
I was worried this was somehow a hardware problem. Copying files seems so basic, I didn’t think there was any way a massively deployed app like Photos could fuck it up (especially since its main job is managing photo files). So, to narrow down the issue I changed out all of the hardware. Here are all the things I did:
I did each of these steps over time, as to only change one variable at a time, and still the image corruption persisted. I didn’t really want to buy a new camera, the MKii is not really a big improvement over the OM-1, but we had a family trip coming up and the idea that pressing the shutter button on the camera might not actually record the image didn’t sit well with me.
Since I had replaced literally all of the hardware involved, I knew it must be a software problem. I stopped checking the “delete after import” button, and started reviewing all of the photos after import. After verifying none of them were corrupt, then I would format the SD card. I did this for months without finding any corrupt files. At this point I figured it was somehow a race condition or something when copying the photo files and deleting them at the same time.
However, after I got home from RailsConf and imported my photos, I found one corrupt image (the one above). I was able to verify that the image was not corrupt on the SD card, so the camera was working fine (meaning I probably didn’t need to buy a new camera body at all).
I tried deleting the corrupt file and re-importing the original to see if it was something about that particular image, but it re-imported just fine. In other words, it seems like the Photos app will corrupt files randomly.
I don’t know if this is a problem that is specific to OM System cameras, and I’m not particularly interested in investing in a new camera system just to find out.
If I compare the corrupted image with the non-corrupted image, the file sizes are exactly the same, but the bytes are different:
Checksums:
aaron@tc ~/Downloads> md5sum P7110136-from-camera.ORF Exports/P7110136.ORF
17ce895fd809a43bad1fe8832c811848 P7110136-from-camera.ORF
828a33005f6b71aea16d9c2f2991a997 Exports/P7110136.ORF
File sizes:
aaron@tc ~/Downloads> ls -al P7110136-from-camera.ORF Exports/P7110136.ORF
-rw-------@ 1 aaron staff 18673943 Jul 12 04:38 Exports/P7110136.ORF
-rwx------ 1 aaron staff 18673943 Jul 17 09:29 P7110136-from-camera.ORF*
The P7110136-from-camera.ORF
is the non-corrupted file, and Exports/P7110136.ORF
is the corrupted file from Photos app. Here’s a screenshot of the preview of the non-corrupted photo:
Here is the binary diff between the files. I ran both files through xxd
then diffed them. Also if anyone cares to look, I’ve posted the RAW files here on GitHub.
I’m not going to put any more effort into debugging this problem, but I wanted to blog about it in case anyone else is seeing the issue. I take a lot of photos, and to be frank, most of them are not very good. I don’t want to look through a bunch of bad photos every time I look at my library, so culling photos is important. Culling photos in the Photos app is way too cumbersome, so I’ve switched to using Darktable.
My current process is:
I’ve not seen any file corruption when importing to Darktable, so I am convinced this is a problem with the Photos app. But now, since all of my images land in Darktable before making their way to the Photos app, I don’t really care anymore. The bad news is that I’ve spent a lot of time and money trying to debug this. I guess the good news is that now I have redundant hardware!
It doesn't strike me as different from "porn" i.e. "unix porn" "food porn" etc, which are at least somewhat widely accepted. I assumed it was self-aware/deprecating humor, as in the people there recognized they were frequently replacing which gear they used beyond what might be strictly necessary.
It was colorful, in the way a lot of music and art is colorful. It's not like it's a sysadmin forum...
It's like, we collectively prioritize efficiency over fun and then we wonder why life is not fun even though it is efficient.
Then apple fucked everyones libraries up completely in an auto update, destroying the metadata and making them unusable, except for songs bought via apple music that is...
https://lapcatsoftware.com/articles/2025/8/7.html
Edit: accidentally called sysdiagnose a spindump.
Hm. That is more than I ever got, but I also never bothered to report anything to any company after being ignored the first tries.
If nothing else, it lets you get your card back much more quickly, as a file-system copy runs at ~1500MBps, which makes a difference when importing 50-100GB of photos.
I also don't delete the images off the memory card until they've been backed up from the disk to some additional medium.
maybe the randomness is based on the other apps he's using at the same time.
I just use KDE's default one, Klipper, and I raise the max entry number.
If something bad replaces your copy, you can get the good one back from the history.
There are nice features like QR code generation for your copied text if you want to quickly share something with someone else's phone as well.
My $dayjob is IT/infrastructure ops, so backup hygiene is engraved in me as a core value. A shocking amount of people outside of tech have no concept of backups or redundancy.
I've had pretty good luck reporting bugs to Google (notoriously bad!):
1. provide simple, crystal clear examples that cannot be due to third parties, misconfiguration or user error.
2. show that it's happening to a large number of mainstream users (not niche)
3. show that it breaks critical workflows and has no easy workaround (incl partial workarounds).
4. if you meet #1-3, then wait 6-9 months minimum (more if hard to fix). If not, wait 3-5+ years.
---
Favorite example: in the mid-2000s, I caught google maps confusing suite/apt numbers for street numbers. It got flagged as low priority. So, to get the team's attention, I reproduced the bug on a large Google offices. Six month later, bug fixed.
After that experience, I report everything to Google that breaks my workflow. Like clockwork, the biggies get fixed a couple of quarters later.
---
Want long? Try improving/fixing core issues with the API design of Linux or PostgreSQL: fix times can be measured in decades. Backward compatibility is insufficient - they rightfully worry about libraries and tools adopting the new APIs and then breaking legacy systems that cannot be upgraded even for mission-critical security issues.
---
NOTE: OP bug feels P0 and the better strategy is either mass media (incl HN) or networking to someone inside the company. I've hit those too over the years and can usually find someone at the company to send directly.
They could really benefit from how Google does it on Android and decouple it. Push updates to their first party apps via the app store like everyone else, and let the OS update on its own separate schedule.
I also want to point out that I've seen similar corruption in the past, only in Lightroom. The culprit ended up being hardware, not software. Specifically, the card reader's USB cable. I've actually had two of these cables fail on different readers. On the most recent one, I replaced it with a nicer Micro B to USB C cable, and haven't had an issue.
I'll tell you a secret though that kind of pisses me off. If you have shipped with a bug, that automatically lowers the perceived priority as well. You know, as opposed to introducing a new bug in a new release. "We've already lived with that old bug…" seems to be the mind set. Oh well.
To be sure though, if you saw the number of bugs that queue up for a popular app like Photos, you'd know that fixing all of them is not going to be possible — some kind of system of prioritization is required.
Let's just leave aside the fact that the name genuinely made many people uncomfortable and unwelcome there (it did), it was also just teenage and immature. There's ways to inject personality and fun into a social experience without giggling about sex. Talk about lowest common denominator...
Why? If your app is used by billions of people, surely you can afford a few additional testers and engineers? Your app doesn't have an unlimited number of bugs: if you are solving them faster than you are introducing them, the number of bugs will eventually approach zero.
Sure, you'll always have newly-introduced bugs which are still waiting to get fixed, but if you've got an ever-increasing pile of bugs which have been around for years - even when they have been reported with easy-to-reproduce steps - then something has gone horribly wrong with your development process. At a certain point you have to stop shoveling new crap, rethink the workflow which is introducing so many new bugs, and slowly start fixing old bugs. The alternative is that your code will inevitably degrade into 100% bugs and become completely unusable and unmaintainable.
Generally I'm frustrated with the state of USB. Bad cables are all over the place and I'm inclined to throw cables out if I have the slightest problem with them. My take is that the import process with Lightroom is fast and reliable if I am using good readers and good cables; it is fine importing photos from my Sony a7iv off a CFExpress card but my Sony a7ii has always been problematic and benefits greatly from taking the memory card out and putting it in a dedicated reader, sometimes I use the second slot in the a7iv.
There is one more thing that gets factored into the bug triage. If the bug affects professional users (as in, data corruption from external media) - fuck them. Apple couldn't care less about professional users. The priority is to fix Photos.app for utility gauge pics and preferably in HEIC and other default settings.
(Yes, this came close to killing someone close to me. Fortunately someone else happened to come along to help.)
Even if it's standard among tech giants, you could be the one that makes a new standard! Good luck in your new role, btw.
Wasn't there an xkcd about that scenario...
That’s what technical debt is. It’s the cost for moving forward quickly. I’m not sure I understand what you’re trying to state.
This mentality is all over BigTech: This bug didn't block release X-1, why should it block release X? So, it inevitably just sits in the backlog forever. If your releases are 90 days apart, any bug found has an average of 45 days to be fixed, or it ends up on the "we lived with it last time" list.
There are many personalities. Not everything has to be mature
I don't recall there ever being any official language about "squeezing both sides of the phone" to make emergency calls. Doesn't the feature description in Settings explicitly reference which buttons to press?
“This bug didn't block release X-1, why should it block release X?” Is actually a pretty strong argument and tough, but not impossible, to counter.
And the bug backlog only gets longer with time. It’s the price of greatly increased software complexity.
In Sonoma or Sequoia they started bundling all Safari updates with macOS, but right now Safari 26 appeared as a separate update in Sonoma/Sequoia—-and it will likely stay that way.
Each thing separately can be explained, but when put together it’s somewhat messy..
The problem is that societal consesus is often wrong, and that image of a perfectly mature person actually does have a lot of problems with it. Every generation discovers this, and redefines that ideal.
40 years ago in my country a "mature man" was expected to take part in alcohol drinking contests until blackout. Nowadays a "mature man" is expected to drink as little alcohol as possible.
Neither attitude is actually about learning and forming a personal, informed opinion, both of them are about following whatever is currently in fashion.
You seem to be assuming that the company will eventually pay off the technical debt rather than just continue accumulating it and lowering production quality.
Once you have market power (which means different things for different companies) you can safely feed the tech debt monster just as little as you feel like.
Btw I wonder if Apple sends some spoken message to the emergency services or some metadata or just connects the phones and that's it.
Edit: oh and I forgot: my wife got a loud message (that bypassed DND) telling her that her father maybe felt, because she is one of his emergency contacts.
Hold on to your optimism, but try not to let that turn into scorn for folks who've seen the other side.
Frequently they were excited to start work at a place where they could "make a difference" and within a year they came to the conclusion that there's wasn't any possibility they could make a difference.
Organizations of that sort have no interest at all in hiring people who aren't going to cooperate on their process.
Also, you may not be aware of Car Crash Detection https://support.apple.com/en-us/104959
Your outlook on career growth is nihilistic, not realistic.
The Insurance Institute for Highway Safety has done a lot as a private organization to raise standards for automotive safety but the statistics they publish that show that larger vehicles are safer than larger vehicles are frequently wrongly interpreted -- in many of the cases where the large vehicle does better it's not that you die in the smaller vehicle but instead get a broken bone. Once something is seen as "life or death" some people will think they have no choice but to spend another $50,000, spew another 20 tons of carbon pollution, etc.