This is related to an earlier question on code review at CV.
While 'code review' itself is understandably out of scope, I wonder about questions like this one which I asked on SO, and this question on plotting nicely.
I imagine that there is a methodological gradient that goes from theory to programming mechanics, but I'm curious where CV stops. This answer seems particularly salient.
Here are some examples of possible edge cases I thought up and the site they border on:
- Plotting results effectively ("data-to-ink" ratio) -- SO, TeX?
- Keeping data organized throughout scaling and transformations (for example, keeping track of categorical variables so they still match the transformed features) -- SO
- Extending existing statistical packages without creating kludge (both etiquette and methodology here) -- SO
- Implementation of a stochastic algorithm (is this the right way to code this, or is there a better algebraic expression for X?) -- MSE
- Reporting results in limited space; how to prioritize? (i.e., papers etc.) -- Academia
- Preparing chains of statistical analysis elements so that reports can be made mostly agnostic to input data -- SO
- What's the best way to store data you're going to start/continue analysis work on in
<this language>
? -- SO - Basic checklist of "things to try" on data when exploring/classifying (CW) -- SO
- If I want to do X, when should I format my data like A? If I'm trying to do Y, should I transform my data to B? What's the best way to go about that in
<this language>
? -- SO
These are all methodological questions, and I'd like to ask some of them, in fact. I'd like these questions to be allowable in the context of review specifically, because that's really the best way to learn.