News for hackers. Stuff that matters.
Re:The Data Science loop: the day-to-day work of a data scie... by pav3l on Tuesday September 25, 2012 @02:15PM (#4571798)
I would be interested to see more "low level" posts about how people approach their data analysis workflow. I do data analysis for a living and find that efficient workflow has just as much impact on your productivity and results as the choice in technologies that you use.
Re:The Data Science loop: the day-to-day work of a data scie... by dude_abides on Tuesday September 25, 2012 @02:31PM (#4571883)
That's a good idea; I will try and write up such a "low level" post this week. As a preview, the things that will prominently feature in the post are - RStudio, custom functions/aggregates in Postgres PL/R, and Sweave. (yes I am a R fanboy).
Re:The Data Science loop: the day-to-day work of a data scie... by pav3l on Tuesday September 25, 2012 @02:56PM (#4572021)
Would definitely like to read it!

I personally find the need to go back and forth quite a bit between different tools when working even on a single dataset. Say, i'll do some work with text part of the dataset in Python, then use Matlab for some basic quantitative analysis, then use R for some advanced statistics if I have to, port those results back to Matlab/Python for speed, then back to R to sweave, maybe some spreadsheet stuff too, etc... So for me, for every project I need to have my dataset in easily accessible format (csv/someSQL/etc) and I need scripts in every language that I use, that would communicate with the data source and get "up to speed" right away.

It's little tips like that I think people should be sharing more.

Re:The Data Science loop: the day-to-day work of a data scie... by washedup on Tuesday September 25, 2012 @05:59PM (#4572913)
RStudio for life. I would like to hear about your experience with Sweave.
Re:The Data Science loop: the day-to-day work of a data scie... by Create on Tuesday September 25, 2012 @02:46PM (#4571971)
http://www.r-bloggers.com/

make sure you look at some older posts

Re:The Data Science loop: the day-to-day work of a data scie... by sadga on Tuesday September 25, 2012 @05:48PM (#4572873)
Double your salary: call what you do "science", not "analysis".
Re:The Data Science loop: the day-to-day work of a data scie... by jmmcd on Tuesday September 25, 2012 @07:04PM (#4573218)
Maybe, but double it again by calling it "analytics".
Re:The Data Science loop: the day-to-day work of a data scie... by mark_integerdsv on Wednesday September 26, 2012 @03:11AM (#4574516)
Can someone explain the affront to your sensibilities that is caused when one of our own (technologists) finds new ways to make money, rebrand and evolve a given subject area or just generally find new, better ways of explaining a thing?

...I'm baffled at the sarc and outrage every time something like this comes up.

Data analyst is a massively broad term that could be anyone from a junior ad-hoc SQL script writer to a guy who sits on a DWH generating leads using complex models and algorithms.

There is a need to distinguish these things from one another and the new definitions and tags are trying to suffice this need... what's your boggle?

Re:The Data Science loop: the day-to-day work of a data scie... by jmmcd on Wednesday September 26, 2012 @10:07AM (#4575668)
No outrage, sarc, or boggle in my comment.

New names are all good if they name new concepts. But new names for old things just sound like buzzwords.