Hey CitrusFruits, thanks for the plug!
(Haha I agree with the dead comment that this reads like a paid ad. I'm grateful you took the time to post this... before I even realized we were on HN!)
We're building so that you're (hopefully) both right:
- The focus is on code, especially macOS/iOS devs in Xcode.
- We want working together to feel as intuitive as Figma/Miro.
Multi is typically used for long-term teammates. That's when, the extra features we get from being native, as well as the command palette to reach someone, are more useful.
Not sure about this for larger teams, but for very early stage teams I agree.
Seeing people using a hard-to-build feature a couple times a day, then more, until eventually you have to mute notifications to focus on work is a great way A/ to feel the progress, and B/ notice trends you can't pick out in averages.
Example for A:
Just yesterday our CTO wrote in a feature-specific channel:
> This page is now unreadable due to volume of usage pings! Go team!!
Example for B:
Intuitively noticing whether your tool, that has say 6 DAUs on a team, is being used once by all 6 people, or in 3 pairing sessions, or something in between.
Yes could run an analysis for this, but at an early stage co it's easier to just notice.
We became June users at our pre-launch co a few months ago, and the feature 0xferruccio mentioned is part of what sold me initially.
Not sure how long it'll remain useful but loving it for now.
John the author doesn't have a HN account so standing in for him here.
We as a team were initially divided on whether to push NSSttatusItem limits in this way. Fighting the OS is always extra work and risk. But at the end of the day Apple's own FaceTime pulls similar shenanigans and ultimately it feels like a successful design.
I live in NYC and was recently surprised to learn that despite the population, we don't rely at all on desalination. Pure water catchment. Good YT doc on this: https://www.youtube.com/watch?v=IDLkOWW0_xg
Most of the points here are about separating your self-worth from your work, and that's certainly good general advice, but it's not the only way to go.
I'll be honest and admit that I connect self-worth with my work, or the sport I'm playing... part of my identity is the desire to do things well.
So yeah criticism hits personally for me. But actually: In a good way. I view every piece of feedback as an opportunity to advance that personal identity.
Usually at work that's desired: The people giving feedback are trying to help. But even that criticism from that stranger on the internet trying to get you down is an opportunity.
It took me a while to get here. I still have half a second of defensive feelings when I receive unexpected feedback. But I've trained myself to quickly let curiosity overpower the defensiveness.
As others have said, your awareness is half the battle. You're on a good path. I hope this alt POV helps!
Cofounder of Remotion here. Thanks for the mention!
We actually still have the drop-in rooms.
The pivot if you're curious is because very few teams adopted the rooms just for hanging out. Instead people ended up doing work in them, like pair coding. So we decided to keep the rooms, but focus all our feature development and marketing on the collaborative features.