The Real Python Community Slack is an English-speaking Python community with members located all over the world. It’s a welcoming group in which you’re free to discuss your coding and career questions, celebrate your progress, vote on upcoming tutorial topics, or just hang out with us at the virtual water cooler.
As a community member, you also get access to our weekly Office Hours, a live online Q&A session with the Real Python team where you’ll meet fellow Pythonistas to chat about your learning progress, ask questions, and discuss Python tips and tricks via screen sharing.
The aim of this guide is to help you:
- Navigate some of Slack’s most useful features
- Get the most out of the Real Python Slack community
- Get your questions answered by other Real Python members
- Learn how to communicate technical problems to your peers
- Get comfortable with the tools you’ll use when you get your first (or next) developer job
We’ll update this guide periodically and welcome any recommendations or questions that you may have. You can share them with me (@Ricky White) in Slack or in the comments below. We’ll make all update announcements in the #hangouts channel of Slack.
Free Bonus: 5 Thoughts On Python Mastery, a free course for Python developers that shows you the roadmap and the mindset you'll need to take your Python skills to the next level.
Successfully Posting to Slack#
Slack lets you post messages and ask questions that everyone within the channel can see. You can also send direct messages to individual users. However, there are a few things to consider before you hit that send button. Let’s discuss those considerations in the context of the three most common ways you’ll post messages in Slack: replying, posting, and cross-posting.
Answering a Member’s Question#
The best way to respond to another member’s post is to use the Reply in thread button. Using threads has the advantage of keeping the entire conversation in one place, which won’t happen if you reply with a new post.
Here’s an example of how to use Reply in thread:
The thread feature is an excellent way to ensure that questions from other members don’t get buried in a flurry of answers to a previous question, which can result in questions being left unanswered.
Another benefit of threads is that they make it very clear to community helpers which questions have already been answered and which remain unanswered. This helps members determine where to focus their time and energy.
Posting Your Question#
When you run into a problem with your code, you may be tempted to jump on Slack, write out your problem, hit Send message, then copy in your code and hit Send again. You may even want to write a more detailed question or explain the solutions you’ve already tried and then—yep, you guessed it—hit Send again.
That’s three posts for the same question.
This approach seems harmless and is technically possible in Slack. But which post are people supposed to respond to? The question, the code, or maybe the initial post where you stated the problem? It’s unclear.
Instead, you should make sure your problem, question, and code are all contained in just one post. This allows people to follow the guidelines for replying in one succinct thread instead of across multiple threads, which can lead to repetition in responses.
You’ll learn more about the best ways to structure your questions and format your code in a bit. For now, all you need to know is that limiting your question to a single post will benefit you and the rest of the Real Python Slack community.
Cross-Posting#
As a general rule, you should try to avoid cross-posting your question to several channels. Cross-posting might seem like an efficient way to get more people to see your question so that you’re more likely to get an answer, but it often has the opposite effect.
Read the full article at https://realpython.com/community-slack-guide/ »
[ Improve Your Python With 🐍 Python Tricks 💌 – Get a short & sweet Python Trick delivered to your inbox every couple of days. >> Click here to learn more and see examples ]
from Real Python
read more
No comments:
Post a Comment