If people are going to post questions with code samples in this forum, I think we need to maybe address some basic underlying requirements. Personally, I prefer a loose moderation wherein we try to ensure a few basic quality of life requirements in posts:

  • Try not to provide screenshots of code since that’s harder to review
  • If you need help debugging, please try to only provide the bare minimum portions of your code which are relevant
  • If possible, try to provide a runnable example of your code in question
  • Try to explain: what you’ve tried, what the error is, what you think the problem is

I’m not trying to sound pushy about forum etiquette. But I personally am much more likely to review code that meets the above requirements. I like something I can compile and run quickly. I prefer some context as to where the issue probably is. Everything else is sort of secondary to me, but still matters.

What does the community think? Also, what do we want this community to do? Support specific programming questions or general CS career/education questions? Both?

You are viewing a single thread.
View all comments
1 point

I like those requirements. I’ll stick a post with them in the top of the community, along with some about career/education questions if you don’t mind.

I think that, being still a small community, we can address both topics by now, and if engagement gets too complicated due to community growth, we can split the community. If you all think differently, we can split topics right now, but I think it’s too early for that. Thoughts?

permalink
report
reply

Learn Programming

!learn_programming@programming.dev

Create post

Posting Etiquette

  1. Ask the main part of your question in the title. This should be concise but informative.

  2. Provide everything up front. Don’t make people fish for more details in the comments. Provide background information and examples.

  3. Be present for follow up questions. Don’t ask for help and run away. Stick around to answer questions and provide more details.

  4. Ask about the problem you’re trying to solve. Don’t focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

Community stats

  • 2

    Monthly active users

  • 102

    Posts

  • 481

    Comments