|
|
|
|
|
|
by Optimal_Persona
2266 days ago
|
|
|
As a data dude in public/nonprofit healthcare-landia I agree with all this, plus: - It's essential to have/develop domain expertise in your industry. - Beware plausible, but incorrect (or poorly interpreted) data that supports yours (or others') assumptions/biases. - Add on to #4 - at least as bad as this is having well-intentioned people on your team who "know enough (a bit of SQL or low/no-code data tool") to be dangerous. Um, why are you joining unnecessary tables, or using a different alias for the same columns/tables in different queries, with no comments or standard formatting? - Hold your nose, but anything you do in SQL/R/Python/even fancier programming tool/language is going to pass through MS Excel at least once sooner or later which can irreversibly bastardize CSVs (even just opening without saving!), truncate precision to 15 digits, change data types, etc. - So glad for the callout in #7 - there are clearly devs/data folks out there who are happy to take on an "interesting programming project at a great paying job" - that isn't serving the best interests of humanity. |
|
|