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?

  • Shareni@programming.devOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    Wouldn’t !programming_languages@programming.dev already be a more appropriate community for content about programming concepts applied to languages?

    Thanks, didn’t know about that one

    I don’t think your clickbait here is fair, as the original post you linked to doesn’t really have a similarly sensationalized title, nor anything about neckbeards.

    It looked cool, so i made a joke and maybe more people clicked it. Also, when the author says you prolly shouldn’t do this, it makes sense that the experts don’t want you to know about it.

    You may be envisioning the term programming a bit narrower than most, as programmers often deal with dependency management, documentation lifecycles, passing down tribal knowledge, juggling infrastructures, things that go way beyond just language concepts.

    I’m here to read about programming concepts that can be applied to any/most languages

    None of those concepts are language specific.

    That is a fair criticism, as generic or low quality questions should be discouraged from being blasted across the (main) !programming community. I don’t mind when someone puts forth a well researched issue with an extensive write up and is merely probing or polling the community at large for insight or opinions, but if it’s just a “How do I do X?” questions prompting “You should do Y!” answers, then those posts should be relegated to dedicated Q&A communities or appropriate stack exchange sites.

    I agree completely.

    What do you think 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
    

    been

    reasoning