my strategy for getting rid of these (earworms? had never heard that term until now) is to just play the song in full, _let it finish_ and go to another song (any song). congrats it's now out of your head. you're welcome!

yeah and:

> By contrast, core features in Dia, like chatting with tabs and personalization features, are used by 40% and 37% of DAUs respectively

well of course. these are likely some of the few major features of Dia which is still in private beta.

this is awesome news. I loved the original pebble but moved to the apple watch after pebble's demise.

I am curious what people here use their smart watches for on a daily basis and couldn't live without, other than to check the day/time. for me it's just message alerts, timer, and media controls. just those 3 features on a e-ink screen would make me super happy.

I moved from Apple Watch to Garmin, so I’m not in the market for something like a Pebble, I value the fitness features too much.

But putting that aside, I’d say the essential features for me are notifications, timer, calendar, media controls.

agreed. at my company we ended up rolling our own system. but this area is absolutely ripe for some configurable saas or OS tool with advanced reporting and alerting mechanisms. Datadog has a decent offering, but it's pretty $$$$.

Gonna throw in my hat and say that if you’re working on industrial applications (like energy or manufacturing) give us a holler at www.sentineldevices.com! Plug-and-play time series monitoring for industrial applications is exactly what we do.

love this.

thank you so much!

I love this. but, why?

ha. this just reminded me that some old touchtone phones had a pulse button in case you needed it.

Every POTS phone I've ever seen, touchtone included, has a pulse button. It's the hook switch!

wow - this was a great walk down memory lane. I remember using all of them, particularly tables for creating complicated layouts. it worked beautifully but was an unbelievable pain to maintain when making layout changes. what's wild though is that this technique eventually went way beyond the category of "hack". slicing tables into layout became officially supported by major software such as dreamweaver (big at the time) and photoshop! yes, you could open a static design in photoshop and use the "slice tool" to cut it up into an HTML table. good times...

I agree with this approach. the other added benefit is that when they decided to optimize the app by eliminating or tuning queries and utilizing replicas for reads, they ultimately made the app much more performant while possibly reducing complexity. the "squeeze" mindset pays off in the long-run here. the continued optimization over time is infinitely better than adding the complexity of microservices or expanded infrastructure because the latter will simply bury and compound the potential optimizations which could AND SHOULD have been made. squeeze squeeze squeeze until you just can't squeeze any more!