pauldjohns
The most compelling use case has been surfacing in a collaborative review env. We've had installs using it to consolidate the fix-it feedback rather than decipher screenshots from Slack or tickets from Linear. They're using our product as an instant DevOps stand-in, hosting branch-based review environments and allowing in stakeholders to comment directly or even propose a simple fix (copy, color, etc. - things that shouldn't need a ticket).
I'm wondering if this is just a use case for smaller teams w/o dedicated DevOps or more valuable for review in general. Anyhow, try it if you have time or interest: review.somethingelse.ai - it's been fun to build and we're thinking this may be the right area to spend more of our development time.
From my several visits to the audiologist, it still seems noise therapy is the most highly regarded therapy.
Get a white noise machine for sleeping. Hands down the best thing for me until I just got used to it always being there.
Personally, I'm working on a river TierBlend seasonal forecast (currently 6–15 weeks per gauge) — in-house ML model trained on 35+ years of weekly discharge plus NRCS SNOTEL snowpack features (https://pauldjohns.github.io/usgs-discharge-poc/)
If you want to try to build more of a personal connection, it's more about introducing small talk and banter into whatever frequency you guys meet (stand-ups, etc.). Learn a little bit about each other and what the other person's interested in. You may find common ground that you didn't know existed. For example, my co-founder and I both learned that we both really enjoy cooking.
At the end of the day, as long as it's strictly professional and focused on work, there's no harm in it. As long as you guys enjoy working together, are driven toward a common goal, and get joy out of the time that you do spend together, even if you're not going out and doing things together when you're not working.