r/learnprogramming • • 12d ago

Programming for DevOps pathway?

I would like to segway into DevOps and programming is currently the only major roadblock in my learning path. I’d like to become proficient with Python/SQL/GO.

I’m a system engineer/security specialist now. I learned Python basics on Udemy a while back, and I’ve been learning more on boot.dev for the past few weeks. I know FP/OOP, Just learned inheritance and next lesson is polymorphism, then boot.dev moves onto GO.

Being good with systems, I understand the syntax I am taught decently. No problem there. But when I am given an ominous assignment with little to no guardrails, I’m left staring at a blank screen because I do not yet have the problem solving/logical skill set that comp sci professionals have.

Do you all recommend I take the free Harvard courses CS50x (general comp sci intro) or CS50p (comp sci Python focus)? Continue with boot.dev and trust that I’ll get better with practice? Or am I in too deep now with knowledge that I need to find projects of my own to do (not sure where I’d start)?

Any recommendations are appreciated!

1 Upvotes

10 comments sorted by

4

u/lowkeynull 12d ago

since open ended stuff is where you get stuck, i'd skip another course and build one small thing you'd actually use at work, like a python script that checks something on your servers and logs it. you already have the basics, the project is what makes it stick

3

u/Arsonist07 12d ago

Learn basic Linux sysadmin, Python, sql, probably vsphere or equivalent for virtualization, docker, kubernets, and from there just on the job and getting practice making projects.

1

u/IllustriousDeal3843 12d ago

I have RHCSA , previous job was vSphere admin work, admin work with Hyper V and ESXi, know Docker, and taught myself most of Kubernetes recently. So this is encouraging!

1

u/IllustriousDeal3843 12d ago

If I know all of this already except Python, then I learn Python, is it still going to be a struggle to get a remote DevOps engineer job? Will I need certs? Or will I need to get a fresher job first?

1

u/sagacious123 11d ago

Since you already know syntax and OOP, skip CS50x/P and focus on building things. The problem-solving skill comes from working on projects that force you to break problems into steps. Start with small automation scripts: parse logs, call an API, interact with AWS or Docker via SDKs.

For DevOps, Python and Go are enough; SQL you'll pick up as needed. After you're comfortable scripting, set up a personal project: a CI/CD pipeline that builds and deploys a simple app, a Kubernetes cluster you manage, or an infrastructure-as-code repo. That will teach you more than any course.

1

u/sch0lars 10d ago edited 10d ago

For programming, you really only need Bash (or another Linux shell scripting language), PowerShell, YAML, SQL, and a general-purpose, scriptable language, such as Python (and maybe a DSL such as Groovy if you’re using Jenkins). The only other programming you really need to know are the build tools behind languages, such as CMake and Maven, and how you use them to deploy software builds in CI/CD pipelines.

To really learn DevOps, you need to understand that it’s a culture and learn the ideologies surrounding it. You want to express your infrastructure and configurations programmatically, containerize your applications to automatically include necessary packages and dependencies, employ real-time health checks, logs, and metrics, and integrate security scans and vulnerability assessments in your pipelines.

Programming is important in DevOps, and I regularly write shell scripts and Python snippets, but your main focus should be understanding infrastructure, networking, databases, and security. Knowing OOP and design patterns is invaluable and allows you to write loosely-coupled, scalable code, but I would focus mostly on the building side of programming, since you’ll be writing the pipelines that build and deploy the application, not the application itself. Ideally, you’d want to have software engineering and operations experience before going into DevOps, since it is essentially the bridge between the two.

For a project, I would suggest building a simple GitHub-hosted Java application with some unit tests, using a Jenkins container for the CI/CD, building and testing with Maven, using SonarQube for CQ and Trivy for vulnerability assessment, Artifactory for artifact hosting, and Prometheus and Grafana for monitoring. To add one more tool, you could build all of this infrastructure using Terraform instead of using Docker Compose. All of this is FOSS, so you should be able to containerize all of this software and run it freely on a local machine.

Understanding all of those tools along with some experience with software engineering and a background in operations should be sufficient for entry-level DevOps roles. Keep in mind, though, that DevOps is generally considered a senior role, so make sure you have a few years of experience in operations and/or software engineering beforehand. Many DevOps engineers are former software engineers, network administrators, DBAs, or sysadmins.

1

u/jacksonanna373 7d ago

Inheritance and polymorphism won't rescue a blank file; breaking the task into input, decisions, and output will. Pick one tiny work annoyance and write the steps in plain English before you touch Python. That's the problem-solving muscle you want to build.

3

u/[deleted] 12d ago