3 ms·

Kubernetes, Linux, CI/CD pipelines, unit testing...<insert tech here/> To be honest the landscape is constantly changing and people should learn as much as the

Kubernetes, Linux, CI/CD pipelines, unit testing...<insert tech here/> To be honest the landscape is constantly changing and people should learn as much as they can. I call ignorance on these kinds of posts.

etaioinshrdlu 5y ago
I don't want to learn just anything, I want to be careful to learn things that won't go out of date quickly.
- tedk-42 5y ago
  OK PHP is great for you then. C and Java won't go out of date quickly. Not the hottest tech out there but they have a long used-by date if that's what your major concern is. If you believe k8s will just 'go away', you don't really have a good clue about what it tries to solve and instead, get confused in its complexity. Having been around the block, i can see it sticking around for at least 10 years.
strzibny 5y ago
Learn more of the underlying knowledge (which is what I teach in https://deploymentfromscratch.com/ https://deploymentfromscratch.com/) and your knowledge will last longer. Ansible YAMLs or your CI/CD provider YAMLs are just abstractions. But forcing anyone, especially data scientists into a specific and quite complex tool of the day? Pass.
- rc_hackernews 5y ago
  Bought your book awhile ago from someone that mentioned it on my Twitter feed. I’m really enjoying it! You did a great job on it. I especially liked the chapter on networking since it was always something I was weak in.
  - strzibny 5y ago
    Thanks a lot for your kind words. Super happy you are enjoying it!
- tedk-42 5y ago
  No-one is forcing anyone to do anything. Tools are built by people that use them. If your team chooses to deploy their applications on a k8s stack, it's on them to own that and not treat it like a black box. I'm completely against the entitled belief that a person 'shouldnt need to know how to <x>'. I can stretch the example in many ways: 1) if you're commit secrets into your source code and claiming a 'data scientist shouldnt need to know about secrets management' 2) if you're building a data analysis script and you leave it as an undocumented mess that's not got no unit tests and one day it breaks, you shouldn't claim that 'a data scientist shouldnt need to know about testing' Oh cry cry there's a tech that everyone is using but i don't want to learn it / i dislike doing that particular thing / working with that piece of tech. Build your own damn tech stack/computer if you think you can do it better. Or ask in the job interview if your team is running their data science platform on k8s if you dislike operating apps on it so much and deny the job.

etaioinshrdlu 5y ago

I don't want to learn just anything, I want to be careful to learn things that won't go out of date quickly.

tedk-42 5y ago
OK PHP is great for you then. C and Java won't go out of date quickly. Not the hottest tech out there but they have a long used-by date if that's what your major concern is. If you believe k8s will just 'go away', you don't really have a good clue about what it tries to solve and instead, get confused in its complexity. Having been around the block, i can see it sticking around for at least 10 years.

strzibny 5y ago

Learn more of the underlying knowledge (which is what I teach in https://deploymentfromscratch.com/ https://deploymentfromscratch.com/) and your knowledge will last longer. Ansible YAMLs or your CI/CD provider YAMLs are just abstractions. But forcing anyone, especially data scientists into a specific and quite complex tool of the day? Pass.

rc_hackernews 5y ago
Bought your book awhile ago from someone that mentioned it on my Twitter feed. I’m really enjoying it! You did a great job on it. I especially liked the chapter on networking since it was always something I was weak in.
- strzibny 5y ago
  Thanks a lot for your kind words. Super happy you are enjoying it!
tedk-42 5y ago
No-one is forcing anyone to do anything. Tools are built by people that use them. If your team chooses to deploy their applications on a k8s stack, it's on them to own that and not treat it like a black box. I'm completely against the entitled belief that a person 'shouldnt need to know how to <x>'. I can stretch the example in many ways: 1) if you're commit secrets into your source code and claiming a 'data scientist shouldnt need to know about secrets management' 2) if you're building a data analysis script and you leave it as an undocumented mess that's not got no unit tests and one day it breaks, you shouldn't claim that 'a data scientist shouldnt need to know about testing' Oh cry cry there's a tech that everyone is using but i don't want to learn it / i dislike doing that particular thing / working with that piece of tech. Build your own damn tech stack/computer if you think you can do it better. Or ask in the job interview if your team is running their data science platform on k8s if you dislike operating apps on it so much and deny the job.