25

Answering your direct questions first: .... or posting links to GitHub instead of code chunks, etc.? The keyword you use here is 'instead', and the answer is 'no'. You cannot post questions here with links INSTEAD of the code. You can post questions with both the code, and the link though, if you want. Only the code you post in the question is for review ...


16

Short answers: yes whichever works best depends depends. Long answers The code you post has to work and be yours. Debugging things is not the purpose of Code Review. Beyond that, pretty much anything is fair game. So, yes. You can post such a project. There is a technical limitation of 30,000 characters in a post. If your code is longer than that, you ...


9

Your question has been pretty thoroughly answered, but I thought it might benefit the Code Review community if I took a minute to present a few ways in which CR has been used by developers who are working on open source software. Particularly since I inadvertently sparked this discussion to begin with. The Lone Developer: A Case Study Leonel is a lone ...


8

Can such a project be posted for review? There's definitely precedent for this; plenty of questions have been asked which incorporate (for example) HTML, JavaScript, and CSS. If so, how should it be done? One question or several? If it fits in one question reasonably, one question is fine. On the other hand, if it makes more sense to separate it, go for ...


7

25K characters is a large post, but it's well below the maximum of 30K so there should be more than enough room to supply enough plain-English context and "walk" the reader through the code. You can link to the test code for context; I've linked to the code base at a specific commit on GitHub myself, for additional context - the code that's linked to isn't ...


5

It sounds like you want the code to get reviewed. So if you can post an understandable question and explain your project and include the code within the 65536 character limit for posts, then it sounds perfectly on topic for me. (The usual Stack Exchange limit is 30 000 bytes; Code Review allows 65536 bytes as of 2015-08-15.)


5

I believe that first question should be on Programmers. We should flag it and see how well our new moderator handles it.


4

Keep in mind that questions get 5 points per upvote, and answers get 10 points per upvote, regardless of length. Long questions are unlikely to get upvoted, because most voters don't want to have to read that much text before deciding whether you question is good. Long questions usually require long answers. Most reviewers would prefer to work on simpler ...


4

Formulate a question based on the most dubious part of the code. (Bad code is OK, as long as it meets our minimum standard that it works as intended.) When posting the question, embed the excerpt being discussed in the question itself, but also link to the entire codebase, on GitHub, for example. Reviewers can draw on the entire repository for context; ...


4

Not all code posted in a question is always up for review. Questions frequently include context code that isn't intended to be reviewed, and the best way to indicate that the code you're providing isn't meant to be part of the review is by using quote blocks like this: > func fooBar() -> String { > return "fooBar" > } This doesn't show up ...


2

You cannot link to the code as an alternative to posting the code in your question. The code that you want reviewed must be embedded in the question. We actually have a close reason specifically for questions that do not contain any code. Links can rot and your question would be of no value to the community if that happened. I was once told that if the ...


Only top voted, non community-wiki answers of a minimum length are eligible