Hello,
TL:DR Atmospheric scientist with knowledge of cli, python want change to a SRE job
Let me explain my background, I am M.Sc in atmospheric science with a few publications in the field, during my studies I work most of my time working with cli tools so I am confident with shell and cli tools, pipelines, stdout, stderr, tmux, etc. I worked using numerical model that you need to compile, this teach me tools like makefiles, modules and cronjobs to did it operational. I have experience with python and other scientific languages like R, Matlab. During my free time took some course of docker. Even I set up a Nginx webpage that I leave to die for lack of time or setup a raspberry pi to download “linux isos” using docker.
I really enjoy the automation of process, and help other colleagues to setup and install the environment to work.
I know my lack of networking, monitoring, and I’m not sure if my self taught skills (science standards) are comparable with a CS worker.
I want to learn or get the certification needed to get a SRE job to mid 2024.
Any advice, course or certication to help me to get in the road?
Thank you for a elaborate answer,
Yes, I will invest some time to learn about cloud. I’ll search which one is most used in my area
You are right, I never have a administration role, I’m the link between IT and the researchers so I have soft skills of admin in linux but not have exp do it that.
That’s really good, I’m comfortable using Linux and bash
I will let this like an extra, I need to fulfill other foundation skills, but I’ll keep it in mind
Yes I am in the same boat, python tend to slowdown or cause problems when we want get env with the other people in the group that only work with R, we try to use bash as much as possible. I’m thinking to learn golang to replace python.
With this I can make a better plan to leave the academia and get dev role, for me there’s a lot of information, topics, technologies to learn in one year, maybe I was very optimistic.
I think Go is good to learn. Many vetted open source Go tooIs use Makefiles (e.g. kustomize) which may be a good point of entry for DevOps in Go.