4 ms·
From a data analysis perspective (which seems like some of her rules are related to), my number one rule that I always try to follow is to: work with the data,
by daemonk 10y ago
From a data analysis perspective (which seems like some of her rules are related to), my number one rule that I always try to follow is to: work with the data, not with the tools. It can be really easy to go down the rabbit hole of messing about with the perfect tool for your analysis and end up with no results.
Optimization is important so far as you need it. If I can launch a bunch of aws instances to get a single-run job done in an hour, then I'll throw hardware at the problem instead of worrying about my code. I care about the analysis results, not necessarily how performant my method is.
If I'll need to run the analysis multiple times or I plan to publish it as a tool, then thats another story.
- gwbas1c 10y agoA common recurring theme in my career are horribly-performing applications because the original programmers worked with an ORM instead of the database. Database code isn't hard! An HBM file is just as complicated as handling a data reader! Stored procedures (or in-line SQL) are simpler in the long run!
- ansgri 10y agoI also don't get the ORM stuff: typically you work either (1) with lots of different objects organized in some kind of document (in NoSQL sense), and you want all these objects to be predictable, free from side effects and clearly serializable to e.g. JSON, or (2) with bulk data which you transform and aggregate to come with a small collection of fully constructed (also, denormalized) objects, and for this purpose SQL is beautiful. Or else they wouldn't've invented Linq to Collections.