I think the best way to do this would be to keep /v/programming as a catch all, but keep the recurring content segretated. What I've seen some subreddits do is to have automated threads for recurring themes. For example, you could have a weekly "Programming Help" thread where users submit what they need help with in the comments, and other users can help them out.
This way the content is segreated, but still part of the main sub, as /v/programming is expected to have the largest userbase of programmers, so it makes sense to keep the help where all the people good at programming are.
Another thing is, consider who is going to subscribe to /v/programminghelp. The majority of it is going to be people who need help. Sure there will be people who can help, but they will be fewer as /v/programminghelp is a sub with limited content, and that content is not interesting to normal good programmers, which once again falls back to the idea of /v/programming having a much larger programmer userbase.
I think the best way to do this would be to keep /v/programming as a catch all, but keep the recurring content segretated. What I've seen some subreddits do is to have automated threads for recurring themes. For example, you could have a weekly "Programming Help" thread where users submit what they need help with in the comments, and other users can help them out.
This way the content is segreated, but still part of the main sub, as /v/programming is expected to have the largest userbase of programmers, so it makes sense to keep the help where all the people good at programming are.
Another thing is, consider who is going to subscribe to /v/programminghelp. The majority of it is going to be people who need help. Sure there will be people who can help, but they will be fewer as /v/programminghelp is a sub with limited content, and that content is not interesting to normal good programmers, which once again falls back to the idea of /v/programming having a much larger programmer userbase.