I think there are some important things being miss...

# meta

[caelum19]

I think there are some important things being missed here:
• Many people will be learning Kotlin and Android at the same time, and for these people it will be hard to distinguish whether their issue is "related to Kotlin" or not
• Questions are a 2-way opportunity for all but the most well-oiled frameworks and languages. The ability to quickly interact with someone, understand their use case and connect with them on a personal level is something very valuable provided by this slack to the Kotlin community
• Unconstrained linear chat is great for discoverability - someone may come to ask about a vague error message and contribute their insights on another discussion. I agree about questions on the same issue derailing more productive conversation though, and the pros and cons should be weighed out depending on the channel IMO
• Helping people can be a social activity with feelings of social gratification, and I think that is great for engagement of both parties and health of the overall community
• Slack is searchable too and I can often find answers searching here that I can't on google (due to shortcomings of Google Search and SO imo)
•
A reluctance for topics that are less Kotlin related to move elsewhere I believe can be fixed if Slack made it easier to manage multiple servers and invite to other Slack servers like how discord has it, and also Slack being like mentioned above, pretty useless on free tier

I like the idea to have separate "help" equivalents to hotter channels where the questions may be tiresome, repetitive and blocking novel discussion, but if they aren't then I think it's best to keep things as unconstrained as possible for better engagement, community of interest style