Some Lessons

To call in the statistician after the experiment is done may be no more than asking him to perform a post-mortem examination: he may be able to say what the experiment died of.
~ Sir Ronald Aylmer Fisher

The plural of anecdote is not data.
~ Roger Brinner

The combination of some data and an aching desire for an answer does not ensure that a reasonable answer can be extracted from a given body of data.
~ John Tukey

Via r-help.

ProPublica’s Guide to Mechanical Turk

ProPublica’s Guide to Mechanical Turk seems to definitely be worth a read.

Use your space appropriately

When facing a decision of how to utilize space it is sometimes easy.
Choosing between allocating land for a water purification plant vs
a donut shop might not be an easy choice but it is an obvious one.
How then do we allocate our internal or mental space?

Inside us the space is limitless. Most of the time though we don’t feel that way.
Instead there seems to be little free space, and that results in a feeling of
being overwhelmed and unable to cope with life. That is normal and all humans
experience this phenomenon.

The good news is that we are in charge of our internal landscape. Even better,
it is always with us! We can tidy it up whenever wish. We can open up more space.
Perhaps it is more like discovering it then opening it up, because it is already there.

That new space can help to accommodate new investments, like learning how to knit
for example. It may also simply be observed, and left alone. That is really
helpful for “making space” for all of the surprise trials that inevitably will
occur in life. Usually they aren’t very surprising though, given the nature of
this reality. Nonetheless, it makes everything easier when you have a lot of
room to breathe!

Edit a source block with its name shown in org

My preference is to rely upon heading property inheritance to define source block
names. That way, you can just do your work knowing “where” you are working and
keep it simple by not having to name everything. That was just fine until I
wrote a document where I needed to name each source block.
It gets easy to forget the source block’s name. Not the end of the world, but very nice to know.

(defun gcr/org-edit-src-code-plus-name ()
  "Edit the well-described source code block.
Attribution: URL `https://lists.gnu.org/archive/html/emacs-orgmode/2014-09/msg00778.html'"
  (interactive)
  (let* ((eop  (org-element-at-point))
         (name (or (org-element-property :name (org-element-context eop))
                  "ॐ"))
         (lang (org-element-property :language eop))
         (buff-name (concat "*Org Src " name "[" lang "]*")))
    (org-edit-src-code nil nil buff-name)))

quantmod Quantitative Financial Modelling & Trading Framework for R

The quantmod package for R is designed to assist the quantitative trader in the development, testing, and deployment of statistically based trading models.
What quantmod IS
A rapid prototyping environment, where quant traders can quickly and cleanly explore and build trading models.
What quantmod is NOT
A replacement for anything statistical. It has no ‘new’ modelling routines or analysis tool to speak of. It does now offer charting not currently available elsewhere in R, but most everything else is more of a wrapper to what you already know and love about the language and packages you currently use.
quantmod makes modelling easier by removing the repetitive workflow issues surrounding data management, modelling interfaces, and performance analysis.