276 karma · joined January 25, 2021
You can find me at: https://huwfulcher.com
[ my public key: https://keybase.io/huwfulcher; my proof: https://keybase.io/huwfulcher/sigs/oxU3GC_S7uKggXi5WhVmGcTi9JpDaUoJmw8zC-APRkM ]
It’s a real shame that the e-ink tablet space is so pricey at the moment. I’m in the UK so recent events haven’t helped.
If you we look at Slack as an analogy for the water cooler (when it’s used to discuss company related things but not necessarily work related). It makes sense that sometimes threads will need to be capped to stop unproductive rehashing of arguments over and over.
Maybe there is something I’m missing from this article but it seems like it’s looking for a scandalous angle where there isn’t quite one. Lots of companies are trying to figure out how to moderate an always on, always available communication tool when it’s used by everyone in the business.
Having your services and library code as .py files you can import in is great.
The issue comes with how to move from experimentation to deployment. If you already have services/library code as .py files you make your life a lot easier. The issue comes when everything is spread across multiple, poorly documented notebooks. If you're working with an MLOps team it makes their life a nightmare to take those notebooks and conform them into something usable.
Jupyter is great when it is used in the right way.
When you get into MLOps as well, having .py templates actually makes the Data Scientist’s job easier as they can plug and play their models into a system that tracks inputs, outputs and changes for them
I think notebooks are a great way of presenting findings and showing your workings at the same time. If that was their main use then I wouldn’t have any issues
I don’t know whether it’s the Data Science culture or Jupyter but there is a big lack of discipline in writing maintainable code in DS and non-existent git support is part of that.
I always strongly discouraged developing models using notebooks, instead advocating for using .py files and then using notebooks for sanity checking data.
I don’t have any clever ideas for how we can move past Jupyter but the sooner we do the better.
No, I wouldn’t take an adult believing in Santa Claus seriously. They’re entitled to their beliefs and if they do their job well then I have no reason to have an issue with them.
The issue I take is with the equivocation they have made. Believing in Santa Claus and believing in a divine entity are two drastically different things.
As another commenter has said, many great scientific discoveries over history have been made by Christians. It would be wrong of me to deny that there is an anti-intellectual strain in Christianity but it is not the dominant trend that American media would like to espouse.
Whether you think Christianity is sensible or not, if someone has made it to Google then they must possess at least some level of intelligence. To change your perspective on that based on previously unknown information about that person highlights a prejudice.
I don't mean to sound harsh about other Data Scientists from a non software engineering background but the standard workflow is to fiddle around with a notebook until you can get a result. That's as far as it goes, no real robustness to it.
That's a pretty big generalisation but in organisations where they "home grow" their Data Science capability many of the online courses don't cover production level Data Science.
There were teams of people whose job it was to produce one report over a timeframe and they had the process to a fine art.
The main problem came when members of said teams left. Macros locked behind passwords, magic numbers in formulas, the wheels could come off very fast.
If Excel had a more robust functionality for versioning and documentation it could be even more of a powerhouse than it already is.