I had the same experience. For years, like clockwork I had monthly episodes of debilitating back/neck pain that only my chiropractor could "fix".
After reading Healing Back Pain: The Mind-Body Connection by John E. Sarno ( https://www.goodreads.com/book/show/144873.Healing_Back_Pain ), I recognized that my body was trying distract me from my troubled relationship at that time. On my next painful episode, I mentally said "F*ck it, there is nothing wrong with me physically" and the next day the pain was gone, never to resurface again. The whole thing coincided with my relationship finally ending, so that might have had a positive impact as well.
It still blows my mind though, how much grief my brain gave me over the years.
Happy Kagi user here. I'm gladly paying $25 per month because of all their AI features, which work well for me overall. Yes, I could set up API keys on OpenAI, Anthropic, Google and Mistral and get a similar experience for less, but I prefer the convenience of their interface and have clean search results bundled into the experience. I will continue to recommend them and hope that T-Shirt becomes available soon.
With over 100 sensors and 14 nano cameras, the e1 precisely analyses your teeth, gums and automatically removes over 95% of the detected biofilm, in less than a minute.
Real-world "things we ran into" stories like this are super helpful when choosing a service or technology.
Unfortunately, I have a similar experience with Firebase, where I wish I would have known that:
* Don't like the text of your Firebase Auth SMS verification message that we send on your behalf -> tough luck
* Your app name is longer than 15 characters? We are not going to include that hash in your Firebase Auth SMS message that is required by Android to perform an automatic login.
* Global Firebase Auth SMS pricing does not work you economically? Welcome to implement the whole thing yourself anyways.
* Dealing with development environments is flakey, as Firebase's emulators work 98% similar to production, but you will regularly hit things that are different.
* You can't completely automate environment creation/tear down, as not everything is covered by Terraform or Google's own APIs, so you will end up doing manual things in their admin interface.
* Real-time subscriptions in Firestore end up not being worth the tight schema coupling between client and server, as you can't control when the updates fire and you end up with a lot more unintended side effects than what this technology benefits you.
So after a year of workarounds you finally end up deeply understanding the trade-offs involved in Firebase and make the decision that its downsides exceed its out of the box benefits. :(