181–190 of 290 posts
Earlier quoted context omitted.
Are you sure that's introversion, rather than shyness or insecurity? The answer might help with the solution.
[flagged]
2. It's potentially misleading people on HN (which is full of employers and people's colleagues), about how other people with certain labels work and think.
Earlier quoted context omitted.
1000% agree. I'd rather spin my wheels for an hour on Google than ask a silly question in public
I would like to work with you. Asking searchable things may be considered disrespectful to one's time
We’ve gone backwards in terms of the internet being reliable. Human experience is still useful.
Use Google docs. Ideally, everything or as much as possible should be public and accessible to anyone on the team. Especially planning and scheduling documents. Each meeting should have an agenda attached to the meeting on the Calendar. Each meeting should be transcribed and then summarized using Gemini. Minimize the unsearchable communication tools, like Slack and Discord, though these tools are fantastic for casual…
we also use Google Suite. Google Doc's [] task button is very helpful. We use a single to-do list for the team, which helps keep everyone on the same page
I learned the following: - Everything public in Slack. Create a fun-sounding moto that discourages DMs. Even if a DM happens, and the back and forth resulted in a consensus, share that consensus in a public channel (which makes it searchable). - Record your team meetings, preferably with software that can AI-summarize. Folks on vacation / leave can get the rundown easily. - Encourage the sharing of solutions to vario…
It doesn't actually stop people from DMing me, but it does soften the blow a bit when I immediately move technical/product conversations out of DMs. (Obviously anything personal or sensitive stays private)
Earlier quoted context omitted.
Totally disagree. For introverts, "everything public in slack" means that I would rather not say something than have 50 people see my thoughts/rants/silly questions in public
Are you sure that's introversion, rather than shyness or insecurity? The answer might help with the solution.
Slack / IM often, don't demand a response instantly though, async & remote go hand in hand. Put important stuff in email not slack/IM Have a company wiki Prefer video calls for alignment Write to each other often, spend time crafting written narratives, 1-pagers, amazon 6-pagers etc. to share ideas, make people read them, use google docs or ms word online and get comments inline in the document using those tools, fol…
Make conversations public by default. If you use Slack, make team channels, project channels, announcement channels etc. all public. Discourage 1:1 and private communication unless really necessary, especially for engineering topics. This single change will have an immense impact on overall company culture.
I'm at a company now where we are trying to do this but the CIO/CEO keep weighing in on EVERY conversation where they disagree with the approaach. The whole reason we are having the open conversation is for ideation and good communication but when a high level person comes along and says "well thats not the way I would do it" everyone decides to go back to 1:1s, direct messaging, and calls so as not to document anyth…
I find it very dangerous when you have some technical people who moved upwards into non-technical roles still being involved in technical discussions.
Their words carry a lot of weight, yet they have no idea about the actual context of the work being done.
Sometimes this is useful and a fresh perspective from an experienced colleague can unblock things, but more often it stifles discussion and discourages the juniors from thinking freely.
Make conversations public by default. If you use Slack, make team channels, project channels, announcement channels etc. all public. Discourage 1:1 and private communication unless really necessary, especially for engineering topics. This single change will have an immense impact on overall company culture.
> Discourage 1:1 and private communication unless really necessary, especially for engineering topics. Working at an established org right now, where the team is still remote first. I tried suggesting this, but got pushback and the team actually settled on the opposite. For example, they want any optional changes (e.g. suggestions) in pull requests not to be left as comments but discussed in private which 90% of the…
Slack / IM often, don't demand a response instantly though, async & remote go hand in hand. Put important stuff in email not slack/IM Have a company wiki Prefer video calls for alignment Write to each other often, spend time crafting written narratives, 1-pagers, amazon 6-pagers etc. to share ideas, make people read them, use google docs or ms word online and get comments inline in the document using those tools, fol…