The first time it happened, I was using pbuilder on Debian, a lot. Pbuilder is used to build packages, by first unpacking and installing a apt cache into a chroot, and then unpacking a source tarball, all to the file system, for each and every build, whether the package cache changes or not. And I was building a lot of packages for free software debian would just never package, as well as new releases of my own packages, back then. Hence, why SSD's seemed a miracle to me.J. Q. Public doesn't really care.
As for early adoption of the SSD, I was a pretty early adopter and nothing bricked on me without giving me warning that it was gonna happen.
One day I started a pbuilder, it was in the middle of unpacking, and it died. The SSD was bricked, never to read or write anything again This actually is what led me to create cape devtools, which are now called produceit. My first observation is that redhat mock can work with "dirty" chroots, rather than constantly rebuilding the chroot from scratch with the exact same cache and producing the exact same chroot install result. So I created instead a dirty chroot build manager, and also adapted it to use tooling from inside the chroot itself, and then saved that in an unpackaged directory tree. I also could unpack the deb sources into a ramdisk chroot thru bind mounts to re-animate the chroot for a build session. Almost no disk activity at all for builds... I now mostly use produceit to build AlpineLinux packages here.
When I was done I had a debian build system that did not even have to run on debian, either. And then I adapted it to replace mock and friends on redhat, too. So now I could build redhat packages also without redhat. I thought about what I wanted my main build & dev machine to be, and I chose arch, for the simple reason that they were close to upstream and minimized distro specific patching. This worked great until I was doing an arch upgrade a few months later, with a new and different brand of ssd, and sure enough, in the middle of updates, suddenly a bunch of disk errors popped up, and it failed. But the drive fsck'd good and "seemed" usable. So I tried the update again, and in the middle of that try the newer drive bricked, too...
Is that what you mean by "warning"? . Of curse this was a decade ago...