14

One of the best ways for a website to bump up in the search results is to have other websites link to it. So, I feel that one of the easiest things for us to do spread links back to Code Review. The "share" button at the bottom left hand corner of each question and answer doesn't just provide a URL for referencing internally. It also provides social media ...


11

We could put common issues and deviations from standard idioms. That way we don't have to mention the same thing every time. We could have a boilerplate that we add to the top of new questions with crosses that apply to normal failures and an expansive section on the tag info section on what should be done and why.


10

If I know all versions of Python, the easiest way for me to look at all of the Python questions isn't for me to come up with some complicated search that makes sure I'm including all the possible Python tags. The easiest way is for all of the Python questions to have the python tag. The version specific tag (python-2.7) just provides the additional detail ...


10

I'd like to make it a goal to have Code Review land within the first three pages of Google results for sql injection. We already get plenty of questions from baffled programmers, and we should be able to capitalize on the anxiety out there, especially among PHP programmers. We're already on the first page for sql injection review. IT Security currently ...


7

Yes, it would be a good idea to mention common code review issues in tag wikis. I've done this, for example, with collatz-sequence: These sequences are sometimes called "hailstone sequences" because they can cycle between small and sometimes surprisingly large values before eventually arriving at 1. For example, the Collatz sequence for \$n = 159487\$ ...


4

I managed to reproduce the problem outside the tag wiki. If one takes the regularly working code: $$ a_{i+1} =\begin{cases} \frac{a_i}{2} & \text{if $a_i$ is even}\\[2ex] 3 a_i + 1 & \text{if $a_i$ is odd} \end{cases} $$ $$ a_{i+1} =\begin{cases} \frac{a_i}{2} & \text{if $a_i$ is even}\\[2ex] 3 a_i + 1 & \text{if $a_i$ is odd} \end{cases} $...


4

The tags are synonyms, the question must have predated the synonymization otherwise it couldn't have been tagged with both. Feel free to edit the redundant tag out of the post. The tags were made synonyms for a reason - I'm not familiar with either tech, but if a solid case can be made for de-synonymization then it should be discussed on a dedicated meta ...


3

Your edit is now rejected.


3

There are quite some things problematic with this tag: Tag Excerpt is c/p'd from SO Unclear boundaries and scope Generalistic "problem domain" This tag is really tenaciously avoiding clarification. It can theoretically refer to multiple things: Files on the file-system, with their content being irrelevant Files on the file-system, with the content being ...


3

As far as I can see those questions are about ERB templating. A combination of text with <% %> <%= %> <% -%> <%# %> and Ruby inside those delimiters. This is a far cry from NSString and I think the erb tag should be left alone. Of course, I am in the TPL*, so I am hardly objective ;) * Tag Proliferation League


3

These are the things that we need to do: Blog posts talking about the code and the program it helps create Share questions and answers on Facebook Google+ Twitter In chat on text based MMO's Link the Questions and Answers anywhere and everywhere you can Increase traffic to CodeReview We need to make ourselves center of the web (our portion of it any way) ...


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