Nick Heitzman 📊📈 retweeted
The “Data Horror Stories Song”, inspired by a tweet by @rogierK and commissioned by @LisaDeBruine
Any of these ever happened to you?
#rstats #Statistics #DataScience
Nick Heitzman 📊📈 retweeted
AIgos/AI are UNIQUELY BAD at predicting rare events. They model the world via patterns in data, and by def sudden ruptures aren't marked by such patterns.
While this won't work, it will expand surveillance & likely conflate street protest & insurrection.
washingtonpost.com/technolog…
Nick Heitzman 📊📈 retweeted
oh you have a weighted blanket? haha that's cute, I sleep with the crushing weight of all the shitty code I wrote years ago still running in production
Nick Heitzman 📊📈 retweeted
Am very, very ready for the deep learning hype curve to start dying down. 😅
*So much* business value can be claimed with basic statistics, exploratory data analysis, and traditional machine learning–and those techniques require just a fraction of the time and complexity of DL. – at Austin, TX
Nick Heitzman 📊📈 retweeted
Holy Shit: CDC now saying that fully vaccinated people no longer need to switch doors in the Monty Hall Problem!
Nick Heitzman 📊📈 retweeted
Top terms searched on Google in 2020. #dataviz
Source: reddit.com/r/dataisbeautiful…
Nick Heitzman 📊📈 retweeted
Learning how and which business problems to solve with machine learning takes practice. I ask myself Qs like these:
- How might I use ML to solve this? What would the deliverable be? Who would use it, when, and how?
And just as important:
- How could I solve this without ML?
Nick Heitzman 📊📈 retweeted
🤖⚡ scikit-learn tip #37:
New in version 0.23: Create interactive diagrams of Pipelines (and other estimators) in Jupyter!
Click on any element to see more details. You can even export the diagram to a file!
See example 👇
#sklearntips #MachineLearning #Python #DataScience
Nick Heitzman 📊📈 retweeted
Did I spend entirely too long this weekend on this #tidytuesday on #thatswhatshesaid jokes from #TheOffice? Yes, almost certainly, but it's a pandemic- just let me be myself! #rstats
Nick Heitzman 📊📈 retweeted
Tonight it's a Bloomberg chart for the win. Good luck deciphering the starting axis and the gridline increments on this one.
Nick Heitzman 📊📈 retweeted
Some work-in-progress illustrations to gently introduce some concepts for 2-sample t-tests & how to think about p-values. Meant as teaching aids, not as a comprehensive standalone lesson. Caveats & assumptions abound. 🧵
Nick Heitzman 📊📈 retweeted
OK boomR!!
After discussing base vs tidyverse in the context of generational conflicts with @RStudioJoe, I will from here on out refer to base R as "boom-R". #rstudioconf #rstats @SHaymondSays @srmaster @ibddoctor @DrDanHolmes
Nick Heitzman 📊📈 retweeted
1st blog post: takes a month, attempts to be perfect, read by no-one
.
.
.
100th blog post: takes 2 hours, realize done > perfect, read by lots
You get better by writing a lot, not by trying to be perfect.
Let go and press publish.
Then start your next one.
Nick Heitzman 📊📈 retweeted
[Nickelback voice] Look at this infograph!
This quoted post is unavailable.
Nick Heitzman 📊📈 retweeted
| ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄|
You've got what it
takes to be a data
scientist if you
want to be✨
|________|
\ (•◡•) /
\ /
---
| |
Nick Heitzman 📊📈 retweeted
just learned with horror that deleting any of the "family" emojis in google slides does not remove the emoji, but rather kills off each individual family member one by one, starting with the children
Nick Heitzman 📊📈 retweeted
When something in a piece of software makes you say "what were the developers thinking?"
...they were probably thinking of constraints you're not considering.
Nick Heitzman 📊📈 retweeted
I don't see any good reason for the modifier "domestic" in "domestic terrorism".
Is it lesser than international terrorism, somehow? Is "domestic" meant to soften and make it sound less scary, like "racially charged" in lieu of racist?
Just call it terrorism if it's terrorism.
Nick Heitzman 📊📈 retweeted
The most important thing you can do as an industry data scientist is have regular code reviews/knowledge shares w/ your data warehouse team. They know exactly what/where all the data is and all the little details that others don't. Do this early and prevent a bunch of headaches.



























