this post was submitted on 08 Jul 2023
6 points (100.0% liked)
DevOps
1686 readers
1 users here now
DevOps integrates and automates the work of software development (Dev) and IT operations (Ops) as a means for improving and shortening the systems development life cycle.
Rules:
- Posts must be relevant to DevOps
- No NSFW content
- No hate speech, bigotry, etc
- Try to keep discussions on topic
- No spam of tools/companies/advertisements
- It’s OK to post your own stuff part of the time, but the primary use of the community should not be promotional content.
Icon base by Lorc under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In my opinion, it really depends on what type of place you would want to work. There are a lot of options out there, but (specifically for SRE) "cloud knowledge" is a must most places.
I would consider someone with an SRE title more ops than dev, and wouldn't expect much in terms of writing code. I would more expect things like advanced knowledge of availablility, reliability, performance and observability on whatever cloud provider is being used. A Site Reliability Engineer is responsible for realiability of the deployed site, so it is dependent on the site/company on what the actual day to day would look like.
This isn't to say you wouldn't have a place in DevOps with your current skills. However, it may be an easier route to start more on the dev side than the ops side as, in my experience, ops are harder to learn generically because every shop has different processes and operations.
The dev side includes things like you mentioned (e.g. build/test execution/package/artifact publish/code release) and then mixes heavy into ops during deployment which then turns into SRE type stuff when the app is deployed to a real place. Often the dev side is done by people with Software Engineer type titles (potentially a DevOps team), and may even be done directly by the developers themselves.
A lot of these processes include a developer needing to execute locally as well as repeatable execution by an automated system of some type (CI). Linux and bash knowledge is very useful for these types of things, as most of the time end deployment will be on a Linux distro, although development happens on OSx or Windows.
The industry is already trying to change buzzwords, from DevOps to DevSecOps, so it is never bad to know security as well. Things like security vulnerability detection and remediation are very valuable and part of the "shift left" in terms of software delivery.
You are welcome to read my comment history to see my feelings about python in DevOps, but they are not positive, and should just use bash, unless it is actually a python shop and other people know how to use python, or else it will most likely become a security vulnerability in and of itself.
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.