Why data scientists shouldn’t need to know Kubernetes
Recently, there have been many heated discussions on what the job of a data scientist should entail [1, 2, 3]. Many companies expect data scientists to be fu...
[ Hacker News discussion , Twitter thread ] Recently, there have been many heated discussions on what the job of a data scientist should entail [ 1 , 2 , 3 ]. Many companies expect data scientists to be full-stack, which includes knowing lower-level infrastructure tools such as Kubernetes (K8s) and resource management. This post is to argue that while it’s good for data scientists to own the entire stack, they can do so without having to know K8s if they leverage a good infrastructure abstraction tool that allows them to focus on actual data science instead of getting YAML files to work . The
saved by
related reading
- k8s-1m Overviewbchess.github.io
- What we learned after running Airflow on Kubernetes for 2 years | by Alexandre Magno Lima Martins | Apache Airflow | Mediummedium.com
- What job interviews taught me about Kubernetesnotnotp.com
- GitHub - jackyzha0/docker-explained: 🐋 wtf is docker and why is everyone talking about itgithub.com
- Deploying R with kubernetes – Notes from a data witchblog.djnavarro.net
- Machine learning needs better tools – Replicate blogreplicate.com
- Learning Containers From The Bottom Upiximiuz.com
- Towards Data Sciencetowardsdatascience.com
- From Data Engineer to YAML Engineerjuhache.substack.com
- Paul Butler – The hater’s guide to Kubernetespaulbutler.org
- The Portfolio that Got Me a Data Scientist Job | Towards Data Sciencetowardsdatascience.com
- Goodbye, Data Science – r y x, rryxcommar.com