3 ms·
I think it’s a mistake to assume that developers can, or should, only talk to each other in one specific way. Every project I’m involved in has some mix of eph
by PragmaticPulp 5y ago
I think it’s a mistake to assume that developers can, or should, only talk to each other in one specific way.
Every project I’m involved in has some mix of ephemeral chat and more permanent, long-lived communication. It could be as simple as a Discord and GitHub issues. Everyone understands that the chat is for quick conversations and GitHub issues is where things are documented for collaboration.
In my experience, trying to force everyone into a single mode of communication becomes more of a problem. GitHub issues are impossible to follow when they have hundreds of side debates that should have been chats. IRC logs are impossible to consume when you have to search for vague keywords through endless months of backlogs to try to parse out specific topics.
Let people discuss things where it fits best.
- williamstein 5y agoThe Zig programming language approach to communications is a great example of what you advocate: https://github.com/ziglang/zig/wiki/Community https://github.com/ziglang/zig/wiki/Community