Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

For a long time, the aboutabout page described Stack Exchange as drawing from wikis, share-and-vote sites, blogs and forums. “How do I fix this program?” is best suited for forums. Wikis need a structure, so that you can find the right page. A debugging service works differently: there's no good indexing schemes for buggy programs. Share-and-vote is secondary: a debugging service requires content to be provided in the form of solutions to make the program work. Blogs are inadapted because they're completely focused on the initial content, whereas the most important part of a debugging service is the solutions.

Now this kind of modeling is common enough in the daily life of a programmer that I think it can fit under “software algorithms”“software algorithms”. But I admit that it is marginal. For this reason, I have so far refrained from voting to reopen the question.

For a long time, the about page described Stack Exchange as drawing from wikis, share-and-vote sites, blogs and forums. “How do I fix this program?” is best suited for forums. Wikis need a structure, so that you can find the right page. A debugging service works differently: there's no good indexing schemes for buggy programs. Share-and-vote is secondary: a debugging service requires content to be provided in the form of solutions to make the program work. Blogs are inadapted because they're completely focused on the initial content, whereas the most important part of a debugging service is the solutions.

Now this kind of modeling is common enough in the daily life of a programmer that I think it can fit under “software algorithms”. But I admit that it is marginal. For this reason, I have so far refrained from voting to reopen the question.

For a long time, the about page described Stack Exchange as drawing from wikis, share-and-vote sites, blogs and forums. “How do I fix this program?” is best suited for forums. Wikis need a structure, so that you can find the right page. A debugging service works differently: there's no good indexing schemes for buggy programs. Share-and-vote is secondary: a debugging service requires content to be provided in the form of solutions to make the program work. Blogs are inadapted because they're completely focused on the initial content, whereas the most important part of a debugging service is the solutions.

Now this kind of modeling is common enough in the daily life of a programmer that I think it can fit under “software algorithms”. But I admit that it is marginal. For this reason, I have so far refrained from voting to reopen the question.

replaced http://cs.stackexchange.com/ with https://cs.stackexchange.com/
Source Link

Questions about designing or analyzing algorithms (as opposed to questions about implementing them) may find a better home on Computer ScienceComputer Science. I've reposted the question therereposted the question there) (formulated in my own words).

Questions about designing or analyzing algorithms (as opposed to questions about implementing them) may find a better home on Computer Science. I've reposted the question there) (formulated in my own words).

Questions about designing or analyzing algorithms (as opposed to questions about implementing them) may find a better home on Computer Science. I've reposted the question there) (formulated in my own words).

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

For a long time, the about page described Stack Exchange as drawing from wikis, share-and-vote sites, blogs and forumswikis, share-and-vote sites, blogs and forums. “How do I fix this program?” is best suited for forums. Wikis need a structure, so that you can find the right page. A debugging service works differently: there's no good indexing schemes for buggy programs. Share-and-vote is secondary: a debugging service requires content to be provided in the form of solutions to make the program work. Blogs are inadapted because they're completely focused on the initial content, whereas the most important part of a debugging service is the solutions.

For a long time, the about page described Stack Exchange as drawing from wikis, share-and-vote sites, blogs and forums. “How do I fix this program?” is best suited for forums. Wikis need a structure, so that you can find the right page. A debugging service works differently: there's no good indexing schemes for buggy programs. Share-and-vote is secondary: a debugging service requires content to be provided in the form of solutions to make the program work. Blogs are inadapted because they're completely focused on the initial content, whereas the most important part of a debugging service is the solutions.

For a long time, the about page described Stack Exchange as drawing from wikis, share-and-vote sites, blogs and forums. “How do I fix this program?” is best suited for forums. Wikis need a structure, so that you can find the right page. A debugging service works differently: there's no good indexing schemes for buggy programs. Share-and-vote is secondary: a debugging service requires content to be provided in the form of solutions to make the program work. Blogs are inadapted because they're completely focused on the initial content, whereas the most important part of a debugging service is the solutions.

Migration of MSO links to MSE links
Source Link
Loading
added 159 characters in body
Source Link
Loading
Source Link
Loading