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.

Post History

50%
+0 −0
Q&A How should we approach a programming site or sites?

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, ...

posted 4y ago by user1306322‭  ·  edited 4y ago by user1306322‭

Answer
#2: Post edited by user avatar user1306322‭ · 2020-06-21T20:19:25Z (almost 4 years ago)
  • 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;
  • - 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.
  • 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.
#1: Initial revision by user avatar user1306322‭ · 2020-06-21T20:18:23Z (almost 4 years ago)
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;
- 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.