1. Daily Digest for June 29th

    06-29-2010 by dan
    googlereader (feed #2)
    Shared Learned Helplessness In Macro.
    googlereader (feed #2)
    Shared The Conventional Superstition.
    • Share/Bookmark

    Comments (0)

  2. Daily Digest for June 25th

    06-25-2010 by dan
    twitter (feed #4)
    do people really use xcelsius to make interactive datavis? seems really clunky… [d_2]
    • Share/Bookmark

    Comments (0)

  3. Daily Digest for June 23rd

    06-23-2010 by dan
    googlereader (feed #2)
    Shared Worst Home Sales Numbers Ever.
    • Share/Bookmark

    Comments (0)

  4. Daily Digest for June 16th

    06-16-2010 by dan
    googlereader (feed #2)
    Shared This much money will buy you happiness.
    • Share/Bookmark

    Comments (0)

  5. Daily Digest for June 11th

    06-11-2010 by dan
    googlereader (feed #2)
    Shared Free online course in multilevel modeling.
    googlereader (feed #2)
    Shared Histories.
    googlereader (feed #2)
    Shared Report: FBI to "arrest hundreds of people" next week for Mortgage Fraud.
    • Share/Bookmark

    Comments (0)

  6. Daily Digest for June 8th

    06-08-2010 by dan
    googlereader (feed #2)
    Shared Fundamental indexing: A magic formula?.
    • Share/Bookmark

    Comments (0)

  7. Daily Digest for June 4th

    06-04-2010 by dan
    twitter (feed #4)
    New blog post: Moving Data is Like Moving Mountains http://dandube.com/blog/?p=558 #fb [d_2]
    • Share/Bookmark

    Comments (0)

  8. Moving Data is Like Moving Mountains

    by dan

    Why is moving data the hardest thing to do in the world?

    All databases/database apps should have:

    • Easy connection for raw data.  Not a web service connection, but a permissioned, live, SQL interface that requires no special software other than maybe a driver.  The data should be in a readily accessible, universal format once it gets to the app, not converted to Excel or CSV or XML (but these should continue to be options).
    • Fast data transfer.  If my data is bigger than X, it should be compressed before transferring.  Both sides of the connection should handle this seamlessly.
    • Some method for persisting application views of data between apps/users/computers — for example, if my Ajax app pulls out a bunch of data for a table, my Protovis app should be able to read it with minimal (or zero) data movement.
    • For extra credit, my database should have an easy to use semantic layer that can dynamically generate queries (based on a data model I build), and my apps can interface with this to create queries, but use the “easy connection” mentioned above for extracting data.

    SAP and Oracle and Microsoft don’t understand this.  Or, if they do, they hide it because they want to sell you more software.  The problem is that the more complicated the chain of software to get the data, the more likely something fails or the data is bad.  Please — someone build an app-friendly database!

    (as an aside, I wonder how much programming would be required to get some of these things built as interfaces to MySQL or PostGres?  Do the pieces exist, but they just need to be interconnected properly?)

    • Share/Bookmark

    Tags: , , | Comments (0)

  9. Daily Digest for June 3rd

    06-03-2010 by dan
    googlereader (feed #2)
    Shared Supercharging business analytics with R.
    googlereader (feed #2)
    Shared BP Admits to Being “Not Prepared” (”Low Odds” Fallacy Edition).
    googlereader (feed #2)
    Shared Things Everyone In Chicago Knows.
    • Share/Bookmark

    Comments (0)

  10. Daily Digest for June 2nd

    06-02-2010 by dan
    googlereader (feed #2)
    Shared How to get rid of your lawn.
    googlereader (feed #2)
    Shared Prepaid Cell Phones Can Save You Money.
    • Share/Bookmark

    Comments (0)