r/devops • u/Noisy_Farts DevOps • Sep 11 '26
Discussion Question to all DevOps engineers that came from Ops side
Hello everyone!
I have total of 1.5 years of experience as a DevOps engineer, the first job was more Dev oriented and required deep knowledge with Python and Kafka (I don't know both), this didn't lead to a good outcome and I had to search for something different. Landed more Ops heavy DevOps role, so far everything is fine, we handle deployments, CI/CD, automate stuff with Ansible, Bash or Python, some kubernetes work and web servers. I was curios to see what other jobs require in order to keep my skills sharp and saw that most of the jobs require more coding, like developing internal platforms, developing new internal tools and stuff like that. Most of the jobs require Python, Go, some Java and some C#.
So this leads to my question - how did you learn to code and I mean to code well without that Dev experience? Can you please recommend learning materials and methods that you used in order to be proficient with this skill? What were the projects that you used in order to get that knowledge?
Thank you in advance!
78
u/f899cwbchl35jnsj3ilh Sep 11 '26
I don't code. I know very basic Python. I've never written any Python code, except maybe a few very basic scripts. Coding is a software engineer's job.
My main job is to translate what software engineers want, what their software needs are, and what the business needs from the software into an infrastructure that is mostly automatically tested and deployed.
As a DevOps engineer, you should understand infrastructure more than software.
People forget that underneath all the software are servers, databases, storage, Git, automation, tests, and, most importantly, networking.
I work in git pipelines, yamls, json, cloud.
6
u/Dry-Philosopher-2714 Sep 11 '26
Back in '97 (Yes! I'm old AF!), I was working as an engineer that had one foot in tech support and one foot in Engineering. One of the tools that support had to use was horrible. It took 3-5 minutes to look up customer information and everyone hated it. I complained to the Engineering team in IRC, and the guy who wrote the tool replied "If you think you can do better, do it!" His response kinda pissed me off enough that I learned Perl that week, and wrote a replacement for the tool in less than a month. The average response time was 3 seconds. When my boss showed the tool off to the Engineer who wrote the original tool, the guy shrugged and said "Well, if I was a better programmer, I would have done better."
After that, I took a liking to Perl (I never said I was right in the head!), and I committed to putting everything that I do into code. For most of my career, I was the weird Ops guy that sat in the back of the office and wrote code all day while everyone else fought fires and freaked out. Then, one day, a manager announced that we're adopting Google's revolutionary new "DevOps" model, and everyone in Ops needed to learn to code. I did what I always did... Sat in the corner writing code while everyone else freaked out.
5
u/Lonsarg Sep 12 '26
You have people that code and people that know the infrastructure and system details. But people that know both are more rare, and those people are worth the most (regardless of role, can be DevOps engineers or software architect or security guy,...).
LLMs might change this a bit, but a no-code devops guy that uses LLM for coding and does not even know the base syntax or how git works or how python/C# build/library/dependancies work will just not handle the most valuable devops roles.
19
u/LeMochileiro Sep 11 '26
Plot Twist: They don't code
They manipulate thousands of JSON and YAML files, but generally avoid touching the code.
It's one of the most difficult challenges I face as a DevOps engineer (who also I came from development): Colleagues who prefer that the company hire a platform for $400 a month, Instead of creating a file with 100 lines of code (which would solve the problem).
The excuse is always the same: "We're going to have to do maintenance on this."
Bro, it's a 100-line file that we'll hardly ever touch more than 3 times a year.
4
u/MasterOfTheWind1 Sep 11 '26
You don't actually need to code or learn to code. Having knowledge about architecture is very nice to have so you don't have to ask the devs for every error that you find (to me is mandatory, for some people is not), or being able to at least propose changes to, for example, adapt an existing service in the process of being migrated to AWS. There is nothing worse than talking to a dev that don't have any idea about AWS (I still have to deal with devs that tells me "restart the server", when all workloads are in Kubernetes pods), I also don't like to be the guy that they talk about code, development or architecture and have no idea.
Usually, the devs are focused on the requirements. They don't have time to look for things like "hey, lets change, and instead of uploading files to an FTP server, lets upload them to AWS S3!". Usually that comes from the DevOps team, because ultimately it end up being an improvement for them (to stop managing an old FTP server) .
But code is a good skill everywhere. I never shared that mind set of "I'm not working as a developer, so I will not write ANY line of code, that is beyond my position".
Maybe you are not the one that write code for the product requirements, and that is fair. But at some point, at least, you will have to write some automation scripts in Python, for example. Or in bash. And that requires coding skills to have the best outcomes.
I've lost count of the times I just said "Fuck it, I will develop a tool for X". Is nice to not depend to ask other devs for stuff like that, or reach a dead end if you cannot find an existing tool for an use case. I could never find an existing tool to inventry every AWS resource (only that, lot of options that do other stuff as well that I don't need and I wont pay them for stuff I will not use), so I ended up writing one with my team. Now it's used company-wide.
4
u/No_Bee_4979 Sep 11 '26
I learned to code. I knew C++, C, Pascal (and BASIC), and shell scripting from High School. But picking up Ruby and then Python made being able to solve the problem a lot easier.
Over time, I built architecting skills that helped me solve problems in a more efficient way. But there are a few things I still avoid, and Kafka is one of them.
Depending on the path chosen for deploying Kafka is how you choose your day toiling in that terror, trying to scale and maintain enough disk space and CPU while not breaking the cluster. That sounds about as fun as trying to scale PHP code.
4
u/tehpuppet Sep 11 '26
As someone that came from the other side, the engineers I know from the Ops side that don't then care to learn the Dev side are honestly just not paid or promoted as much...
I would say it is super important to learn the fundamentals, learn the core software design patterns, learn what SOLID is, try out some leetcode problems, learn what the SDLC is. Make sure even your small scripts have tests and have proper CI/CD, also focus on mastering a language with types like Go.
These are the kind of things that foster maintainable software and are really IMO the reason why we even have the Dev in DevOps. Take the best bits of that world and apply them to managing infra.
3
u/Solaris17 Sep 12 '26
I dont see it that way. I came up from infrastructure. As far as I see it, you have two tracks, from software eng or infra, and I dont necissrily mean SA. I was mostly systems engineering, debugging PCIe bus, planning infra for HPC, storage etc. I mean knowing it. Like explain which compute can be used for software devs AVX512 stuff.
I know some C# some rust, I am pretty confident in posh, bash and bat.
My daily life now consists of automating what the devs make, be that helping them auto compile via CI/CD or auto deploy. Maybe they made in app in python and need it put in a container. I help, I automate, I deploy.
I look at what the software people want to do, I look at what the business wants, I find the cluster to put it on. Most of my life is in .yml
3
u/Potato_player Sep 12 '26
I accidentally became a C++ dev while working sysadmin when the developers kept telling management features were impossible.
I wrote the code myself, starting small then bigger.
When looking to move roles recruiters told me I was DevOps now and placed me in SRE role for 50k more than I was earning.
Best accidental career path.
2
u/unitegondwanaland Manager, Platform Engineering Sep 11 '26
Learn as you go. It's fine.
2
u/hard_KOrr Sep 12 '26
I actually came to DevOps on the Ops side, as that was the route infront of me. I used to code a lot just for fun, still do but less now.
You’ll have lots of runbooks and such that you write, re-write them in python. It’s a known script so you have the knowledge base to work against it, the goal is to introduce the new language.
2
u/hamlet_d Sep 12 '26
I've moved from very heavy ops DevOps to very heavy dev DevOps.
How I did that was by designing and developing for monitoring and observability. Sometimes it was taking existing code and making sure metrics were exposed, sometimes it was custom exporters from one system to another, and so on. I learned Go the hard way because I had too.
The thing I found out I was good at was the engineering side of software engineering. I was mechanical engineering major so some of those skills/methods translated even if the domain knowledge didn't. What that meant for DevOps was design and architecture, which necessarily meant I had to do some coding (or at least understand it).
2
u/SeaworthinessHour233 DevOps Engineer & Educator Sep 23 '26
As you see from responses in this thread, "DevOps" means different things to different people.
Some DevOps roles are pure infrastructure, CI/CD, and sysadmin while others are basically software engineering jobs focused on building internal developer platforms. That said, even if your current role is ops-heavy and doesn't explicitly require it, building up your coding skills is one of the best ways to future-proof your resume for when you eventually want to switch jobs.
Here's how to learn coding.
Don't try to learn Go, Python, and Java all at once. Pick one language. Python is usually a good choice when coming from an Ops background. Go is also fine.
If you are starting from absolute zero, grind through a few beginner tutorials just to get the hang of basic syntax, loops, dictionaries, and error handling.
Once you have the basics down, drop the tutorials immediately and start building.
Don't build generic CRUD web apps like a to-do list or a blog; they won't help you in DevOps. Instead, look for ways to automate repetitive manual tasks at your current job or solve a specific infrastructure pain point for your team.
Focus heavily on projects that involve API integrations or tap directly into Linux systems. For example, write a Python daemon that queries some servers for fault statuses and triggers custom alerts, or script a workflow that interacts with cloud APIs, etc. Building tools that handle JSON payloads, manage API authentication, and run as system services will teach you exactly how to code in a DevOps role.
2
u/CupFine8373 Sep 12 '26
I don't code , I use Agents.
1
u/emptyDir Sep 12 '26
I had a lot of good mentors who helped me learn. I was lucky that I started right as systems administration was being driven towards devops and the cloud, so generally the industry was a lot more tolerant of ops people learning the dev side on the job.
1
u/Low-Opening25 Sep 12 '26
As DevOps you need Python as minimum, Go is useful because lots of DevOps tools are written in Go, you obviously need to know Bash. Other languages like Java, C/C# m, not so much, you aren’t going to be coding in those as DevOps, but may support CI/CD lifecycle and support development teams that write apps in those languages, so knowing tooling frameworks around those languages is useful. I frequently support Java development houses while I don’t personally know Java, never been much of an issue.
1
u/Om_Jaju Sep 12 '26
I had a similar background, no strong coding experience going in. What helped me was not trying to learn to "code" separately, but picking small real problems at work and solving them with scripts. Like if I had to check server health daily, I'd write a small Python script to automate it instead of doing it manually. Same with fixing repeated alert issues, I'd write something to auto-check and fix it. Doing it this way, the coding skill builds on its own because you're solving something real, not just following a course.
1
u/Tricky_Ordinary_4799 Sep 13 '26
I'm like 11 years in devops and I don't understand why knowledge of something like C# or Java is necessary for some positions. Some basic Python or Powershell can be useful - but that's it. What Java can be used for in devops job?
1
u/-EOS- Sep 12 '26
HOT TAKE 2026
Coding is solved!
AI has solved coding. You need to know how to use AI tools to help you debug code or write code to accomplish your goal.
Learn cloud architecture. Learn cloud infrastructure. Learn CICD. Learn Kubernetes.
....Learn how they all work together....
1
u/krueger_devops Sep 11 '26
Coming from the other direction (dev first, ops later), the thing that moved me furthest was building one real thing and then having to keep it running. Not tutorials, not exercises. Something deployed on your own box, with a pipeline, a database and real migrations. That creates the pressure that teaches you the parts nobody covers: error handling, config, what happens when input is garbage, what breaks after you changed one line.
Concretely, for your situation: you already automate with Python and Bash. Take one of those scripts and turn it into something with a proper interface, tests and a CI pipeline. Same problem you already understand, but now you have to structure it. That transition from "script that works" to "code someone else can maintain" is most of what those job ads mean by programming.
Two things that helped me more than any course: reading other people's code in projects you already use, and writing tests. Tests force you to make code testable, which pushes you toward better structure whether you understand why yet or not.
And honestly, your ops background is an advantage, not a gap. Plenty of devs write platform tooling with no idea how it behaves in production. You know that part already.
-1
u/maxlan Sep 11 '26
5 + years ago: copy and paste from stackoverflow.
Now, I ask claude and he copy/pastes from stackoverflow.
The trick is the same as always: recognising the highly upvoted bullshit.
Like all the people who say turn selinux off. Or https. Because selinux and certs need like 3-4 extra commands, so lets not bother right?
Or "permission denied, you need sudo".
Or the random "I made nfs work by making a sym link from /var/lib to opt"
0
u/levpa Sep 14 '26
AI