Looks good to me. Improvements from the 1st gen watch, and the FitBit integrations look nice. Having an "official" WearOS watch on offer is always good, my previous and current watches (from Fossil and Skagen) had a lot of issues (battery life, performance, slow updates, etc). Never really was a Samsung guy, but I heard their implementation of WearOS was good.
It's a really useful perspective in real-life scenarios when you're not developping critical software. Of course a baseline of risk-avoidance is always important, but businesses/custommers/users most of the time are ready to handle some risks, like downtime, bugs, delays, etc. SWE and developpers are the more risk-averse of the two parties, which leads to us over-valuing the importance of robustness and stability.
For example, it's way easier/faster to implement observability and some sort of rollback of bad versions than to try and prevent every possible way an app could crash and trigger a bunch of problems. What's going to happen if the app crash is pretty simple : customers will be mad (CS/Marketing/PR can handle them), you'll notice the downtime quickly and rollback (or maybe even rollback automatically!). Then you'll be in a perfect position to handle what went wrong : systems will be back on a known stable position and all the stress of trying to fix something in a live production system will be gone.
Of course, there is no magic bullet. Some problems aren't solved by rolling back services. (e.g. A thundering herd of clients caused by re-deploying an old build overloading your database.)
Yes of course, my fake situation was assuming a pretty boring case of failure with an easy out (rollback). The underlying principle is that most of the time trying to preempt every situation is way more work than being conscious of them and giving yourself and your team(s) reasonable tools to mitigate them :)
I absolutely love Harmonic! Great UI/UX and nice attention to details. Almost prefer browsing HN using it rather than the website :) Thank you for open sourcing!
If you would like an alternative that is still GUI, I personally switched from Postman to Insomnia (https://insomnia.rest/) in the last year and haven't looked back. It has been acquired recently, but it's still open source and very lean. Definitely recommend, you can even directly import your Postman collections if you used them.
I host my own email and most of the time I don't encounter any technical problems: I got rejected once (last week) since I started last year. Most of my problems have been trying to tell/have people read my non "@gmail/outlook/yahoo" domain! Probably depends on how you use your email, but it's been smooth pretty smooth sailing personally.
IIRC, you avoid most of the problems if you set up your DNS accordingly (DMARC, SPF, etc). But for a mailing list AWS SES is probably the way to go to avoid all the trouble.
