Return to Answer

###Comparative reviews should be written in the same language.

###Comparative reviews should not be performance or optimization reviews.

###Comparative reviews should not be too broad.

###Comparative reviews might be better asked as two separate questions.

###So, what would make for a good comparative review?

Comparative reviews should be written in the same language.

Comparative reviews should not be performance or optimization reviews.

Comparative reviews should not be too broad.

Comparative reviews might be better asked as two separate questions.

So, what would make for a good comparative review?

Java method - levels of abstraction

Java method - levels of abstraction

The user could've posted snippet A as "Is this abstract enough? How can I make it more abstract?" and snippet B as "Is this too abstract? How can I make it more abstract?" but then the answers will focus as much or more on how to make the snippets more/less abstract and less on how to decide on the right balance. It would be essentially impossible for the user to receive the same answer on both questions if he posted the snippets separately! In fact, it seems likely that question A is the answer to question B and question B is the answer to question A!

The user could've posted snippet A as "Is this abstract enough? How can I make it more abstract?" and snippet B as "Is this too abstract? How can I make it less abstract?" but then the answers will focus as much or more on how to make the snippets more/less abstract and less on how to decide on the right balance. It would be essentially impossible for the user to receive the same answer on both questions if he posted the snippets separately! In fact, it seems likely that question A is the answer to question B and question B is the answer to question A!