Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on How should we approach a programming site or sites?

Parent

How should we approach a programming site or sites?

+25
−0

We have a suggestion for a site for professional coding, and software engineering and computer science also have some interest, and there are overlapping suggestions for cloud technologies and single-board microcontrollers. It seems likely that participants here have interests in other related areas too. How shall we approach this cluster of topics? Do we want one big tent -- a single programming site? Do we want a big tent and some specialized spin-offs -- what seems to have happened on SE? Do we want to plan for more focused communities from the start -- and, if so, what would they be?

I was an infrequent participant on SO; I have around 1200 rep after many years of passive, occasional posts. I don't have the right experience there to say with any certainty what worked well and what didn't. It appears to me that SO doesn't really have a community; it's too big for that. It might have sub-communities; I don't know how strong they are and how much they interact. And it might have had a community when it started; they're 11 years in now and things have changed. We'll be starting small; we are not operating at SO scale (yet). An advantage of a single site (or small number of clearly-differentiated sites) is that people know where to go; Balkanization where there are two-dozen different sites depending on which libraries or languages or tools you're using probably does not serve the programming community either.

I think a core diffentiator for Codidact is that we're putting community first from the beginning. We want to do what's best for the people participating here, whether that's one site or a handful or many (or one site and later spin-offs). We also have some tools they don't have over on SE, including categories and integrated blogs or wikis. And we're actively working on an open-source platform, so if it turns out there's something we need and don't have, we don't have to wait 6-8 years for somebody to consider the feature request.

It seems clear to me that there is interest in a place for questions about programming -- code, tools, design, and maybe processes. How shall we address that interest? What shall we build?

--

We resolved this by creating Software Development with broad scope. There's even a Code Review category. If the community grows to a size that's hard to manage and subsets want to spin off later, we can do that.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (4 comments)
Post
+0
−0

To answer the original question of how to approach programmer sites, I think a number of important features should be considered.

  • Making relevant versions of OS, programming languages, libraries, software and hardware visible;
  • Having a way to tell whether the question/problem and the answers/solution apply to multiple (a range, multiple ranges or distinct) versions of each relevant OS, language, library. Let's say, in shape of a list of checkboxes of all the versions;
  • Making it easy to add new versions and review older posts, update whether the question and answers are still relevant and work for newer versions.

These are direly needed on StackOverflow due to how old some of the questions and answers are.

Additionally, there needs to be a way to organize/group/link questions about the same, at the base of it, problem, but with slight differences between versions of relevant elements. Something like "Linked questions" widget on StackExchange.

Maybe with even tighter integration/consolidation of data. For example, adding a question variation to an existing question, with a brief description of what makes it different, so users could then browse the same core question, and pick between slight variations on the same page. This could turn the question into more of an all-purpose guide for solving the problem throughout all the versions of the software and OS combinations on one page instead of separate pages. Although it might make the page confusing and harder to navigate.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

General comments (2 comments)
General comments
Monica Cellio‭ wrote over 4 years ago

On your last paragraph, could you give an example? I'm trying to understand the granularity. Do you envision a question about, say, doing or faking multiple inheritance, with variations for C++, Java, Python, etc? Or do you mean something finer-grained, like a question about how to do something in Java that changed from version 7 to 8 to 10?

user1306322‭ wrote over 4 years ago

The only examples of very very similar questions which I think could harmlessly be merged into a single page are questions like "How do I do (something) on Windows (version W) using C# (version C)?" where different versions of Windows had different paths for system files or Registry keys, and also with newer C# versions you could get values easily in new ways. But if you were to change Windows version or C# version, for StackOverflow it becomes technically a distinct question.