Dealing with insurance reimbursements is a huge pain, so threw this together over a few weeks. Not bulletproof, but hoping it can help the thousands of other people in my situation a little bit
hey thanks so much for trying things out! I really, really appreciate it. Totally hear you on the search experience. I currently use Meilisearch (https://www.meilisearch.com/) for the search backend. I love how crazy fast it is and generally have had a nice experience running the system myself. But I totally hear you on the semantic search side of things.
I am definitely hoping / planning to offer that unified "view this product across stores" feature — that would be killer. Just have to work on the ML stuff to get that sufficiently good and get the data in a good spot. The CozoDB thing looks very promising, will check it out! Thanks again
I'm working on Costbot, a price tracking tool designed to help online shoppers save time and money by monitoring price histories and alerting them when their favorite products hit their target prices. The side-project recently become done "enough" to be shared in small fashion, and wanted to ask for feedback/thoughts etc. on here.
I'm a staff software engineer by trade, but love working on side projects in my (relatively rare) spare moments. This has been a fun project, involving some new things I hadn't worked on before (extended parsing / crawling, scraping, headless browsers etc.). Hoping to put together a write-up on the tech soon.
This looks super cool! I have a use case where I store some stateful stuff in Redis that a worker constantly interacts w/ and updates. Redis is great, but the project is a very side thing and would love not to have to pay for bandwidth / just embed it inside of it. Going to take a look at this and see if I can make it work! Didn't see any serialization formats, so might just do that myself. Ty for building this!
Been a fan of fly and have had most, if not all, of my side and semi-side projects on there for some time now. But...the ratio of good/fun/snarky blog posts to reliable service has gotten a bit too large for me, starting to look for other providers at this point just in case they can't turn this trend around. Honestly been a good object lesson for me in the importance of backing up marketing/hype/"mind-share" stuff w/ absolute rock-solid performance/reliability or just forgoing the former for the latter.
As an aside, it's also taking down some decently-load-bearing web infra like unpkg => https://www.unpkg.com/
Yeah, I saw; I've kept up w/ everything pretty closely. Still decently frustrating as a paying customer, but I hope they can figure it out. If they can and can show some real reliability, I'll be an even bigger fan.
Yep! More putting it out there for other folks. I’m also a somewhat frustrated paying customer, but as I’m dealing with my own growing pains, I relate to what they’re going through. I’ve personally migrated my DB to Crunchy to somewhat mitigate the risk.
That's a good point / thing that I've not thought about as much here. I would be much more frustrated if my primary datastores were hosted there. As things stand, their semi-hosted offering never really made sense to me (esp. now lol), but I do think if you get into the game of DB hosting there's almost another level of expectation even beyond basic compute (oddly enough)
Yes web workers are cool. Sadly its only single threaded. If I'm not mistaken the newer version of the engine can run multithreaded but only on super modern browsers. This slightly older version ensures more compatibility
