This community is:

A general purpose programming community for English speakers

Language specific posts like:

and ide specific posts like:

are not general purpose. Posts like that ruined /r/programming for me, and this community seems to be going down the same road. I’m here to read about programming concepts that can be applied to any/most languages, not patch notes for 10 different Js frameworks posted by karma farming bots. If I wanted to read posts like that, I’d have subbed to /c/javascript…

Do you agree with me that they should be removed from /c/programming, and limited only to their respective communities? Or have I missed the point of this community?

  • Dragonseel@lemmy.sdf.orgEnglish
    11·
    1 year ago

    I think both types of community can have a value. Being general as in “all things can fit here” and in “only things that are general to programming”. I have no experience in community management so take my words with a huge grain of salt.

    The communities on Reddit were huge. That lead even in the smaller more specialized communities to have a big volume of posts. I am mainly interested in game-dev and Rust-Lang, and even there were so many posts that do not fit what I am interested in. But would splitting the communities make it better? Maybe I could then chose to ignore some of the posts, but also the hurdle of posting stuff, the and to enter these communities for people might get higher. As a newbie, (either to programming or just to talking on these platforms) you might be intimidated to post to a group of experts. And it is much easier to find. Just a “programming” community where all things have place can be a very good place to “collect” people and filter them into their nieche interests. Link to other communities, crosspost. Hopefully people will then start to post the more specific stuff in the more specific communites on their own.

    I feel like Reddit made it harder over time to form a “meta-community” of multiple subreddits. Though I can’t right now exactly pinpoint why that is.

    So again I see benefits to both approaches. Maybe we just need both. Make a “computer science” community, advertise it on this community, and make it focussed on concepts, papers and the generic programming stuff. Filter the “patch notes” stuff out from there. And this community here could then be the catchall “landing-page” thing. There will be suff for everyone, but not all of it. There will be some general posts and some specifics. And hopefully we can find methods that people find their more specific communities if they have more specific stuff to share or ask.

    Sorry, I got a bit rambly in my stream-of-conciousness post here. Hopefully you can get anything from it. I am not sure :)

    • Shareni@programming.devOPEnglish
      11·
      1 year ago

      I think both types of community can have a value. Being general as in “all things can fit here” and in “only things that are general to programming”.

      I didn’t think of that.

      I have no experience in community management so take my words with a huge grain of salt.

      Same here

      the hurdle of posting stuff, the and to enter these communities for people might get higher. As a newbie, (either to programming or just to talking on these platforms) you might be intimidated to post to a group of experts.

      I think there should be a balance. It might not be ok to lmgtfy people in communities like /c/learn-programming, but it should be fine in others. Just to enforce basic etiquette like googling for a few minutes, or reading the community rules before posting.

      So again I see benefits to both approaches. Maybe we just need both. Make a “computer science” community, advertise it on this community, and make it focussed on concepts, papers and the generic programming stuff. Filter the “patch notes” stuff out from there. And this community here could then be the catchall “landing-page” thing. There will be suff for everyone, but not all of it. There will be some general posts and some specifics. And hopefully we can find methods that people find their more specific communities if they have more specific stuff to share or ask.

      Great points. /c/computer-science does sound really nice.

      What about adding a guideline over here along the lines of:

      if your post is specific to only one programming language or tool,
it should be something that's interesting,
otherwise check out our [community list] or [local community search engine],
and if the community exists, post over there to get better feedback`

(add a list of programming related communities in the sidebar)
(maybe also write it as faux code, and turn it into ascii art, 
it would help catch attention)

      That would limit automated style patch notes to affected communities. So “node version x patch notes” is not fine, but it would be fine to post “node finally supports tail recursion optimization” and just link the patch notes.

      People could redirect posts that should be in specific communities, so for example:

      “How do i x in python?” -> /c/python, “Should i x in Js” -> /c/javascript, “What first language/editor?” -> goto /c/learn-programming, “how do i keep warm in the winter?” -> /c/intellij

      That would help grow those communities, and over here those posts would be filtered out by both active and hot.

      It would be fine to post like: “emacs does something really cool”, “c# binary makes atoms look fat!”, “does rust make lemmy go FASTA?!?!!”

      And it would preserve the general mood with posts like: “fav programming music?”, “programming and humility”, “is chatgpt cheating?” as they’re not specific to any language

      Sorry, I got a bit rambly in my stream-of-conciousness post here. Hopefully you can get anything from it. I am not sure :)

      right back at you, and thanks, this was fun