So mu company has asked me to learn Jenkians. Which tutorials or playlist would you suggest to learn jenkins? Please give your suggestions.

Also, how much time does it require to learn so that I can start writing basic CI/CD pipelines.

Hey guys,

I recently got the opportunity to move to a DevOps team, and I’m looking for some advice on how to prepare.

I have around 5 years of experience working in infrastructure and systems. Most of my experience is with:

• VMware/vSphere and virtualization
• Windows and Linux administration
• Networking and troubleshooting
• NetApp and storage
• PowerShell scripting and automation
• Monitoring, backups, and general infrastructure operations

I also have some beginner-level experience with Docker, Kubernetes, Git, GitLab, Argo CD, Ansible, and Terraform. I’ve built some labs and worked with them a little, but I definitely wouldn’t consider myself experienced with them yet.

I’m starting the new DevOps role next month, so I want to use this month to prepare as much as possible.

For people who moved from infrastructure/sysadmin into DevOps, what would you recommend focusing on first?

I’m mainly looking for a good Udemy course, YouTube course/playlist, or structured learning path that is practical and focused on skills I’ll actually use at work.

If I move to devops should I accept that I won't get to celebrate weekends and new year's?

How has been your experience?

Hi everyone,

I recently watched a podcast featuring a senior developer from EPAM, where he explained the different phases of the SDLC. He mentioned that he built a pipeline covering the entire software development lifecycle—from planning and design to development, testing, deployment, and maintenance—with each stage flowing into the next.

I really liked that idea, and now I'm wondering how to build a pipeline like that myself. Does anyone have any good resources, guides, or examples to learn from?

Thanks!

I'm a student targeting DevSecOps / Cloud Security internship opportunities.

I've tried to position the CV around DevSecOps rather than generic DevOps or cybersecurity.

I'd appreciate feedback on:

• Is the DevSecOps positioning clear?
• Are the projects strong/relevant enough?
• Is the Skills section too crowded?
• Does anything look unnecessary or exaggerated?
• What would make you reject this CV at first glance?
• If you were a recruiter, what would make you reject this CV?
• What would you change first?
• - Is the CV ATS-friendly and likely to be parsed correctly by applicant tracking systems?

I signed up for blacksmith about a week in I’ve got a $7 bill already. I’m also getting you’ve hit 80% of your free mins and you should add a payment method.

I’m seriously confused after being extremely impressed by how fast their runners are. Now I’m wondering what the heck is going on.

I tried to reach out to them but need a payment method to contact billing and no reply on the support@ email.

I’m happy to pay as the service is good but really surprised how they work/do business. I feel I could easily be in for future bull shocks.

Has this happened to anyone else.

Looks like I’m not the only one hit by this - https://forestwalk.ai/blog/surprise-blacksmith-costs/

I recently came across a post on Reddit from someone looking to connect with other DevOps professionals. I reached out, and we ended up moving the conversation to Discord.

It's been pretty nice having a place where we can talk about things we're working on, exchange ideas, troubleshoot things, and share what we've learned.

But the conversations haven't really stayed limited to DevOps - which is actually what I've enjoyed most.

We sometimes end up talking about things like:

• How DevOps/tech work differs between countries
• Differences in workplace and engineering culture
• How people got into the industry and how their careers have developed
• Tools, practices, and technologies people are using
• Interesting things we're currently learning or building
• And occasionally just completely random stuff 😄

I'd like to meet more people from different parts of the world and have more of these conversations.

You don't need to be a DevOps expert or have 10+ years of experience. If you work somewhere around DevOps, SRE, cloud, infrastructure, platform engineering, sysadmin, or software engineering - or you're simply learning in that direction - feel free to reach out.

We're currently a small group, and we'd like to keep it that way rather than turn it into a huge server full of people who never talk.

If you'd be interested in chatting and getting to know some other people in the space, leave a comment or send me a DM. Happy to connect.

I work in a small team that deploys some internal products. No big user pool or database for me! We build small web apps that automate inner processes, and some scripts and jobs. Most of it runs on k8s, the apps and the jobs. We mostly run everyting on Azure. And everyting is managed by code, obviously, so we've build GitHub actions pipeline that live with the code to deploy our infra via bicep and the code via a test-build-deploy-promote pipeline, started on push.

But I've seen some platforms that propose full CI/CD as a services, and it feels like managing the pipeline yourself these days is a bad thing. To me, deploying a solution, especially in the containerization era, is simple; Run the tests, build the image, deploy the workload. Add some customization related to the app if needed (specific parameters, logging or testing jobs, etc). But is managing this code yourself a bad practice? I have to say, it does make for a lot of duplicate code in a lot of repos. The pipelines are very similar.

Should we always aim to use a standardized CI/CD platform? What tools do you use for CI/CD? How different do you handle it from a small project to a more important service?

Hii Guys!,we built an MVP.

Offered the services to three specific clients and got a good response, we are planning to advertise and bring more signups in the next two months

Initially the server bill was roughly 5-8 dollars but now it's increasing so wanted to check

-how do you optimise your server billing?? -Should I move the infra to AWS,will that be cost effective??

We all know that large organizations tend to have a lot of meetings, bureaucratic processes and are in general slow moving. That was true for a long time and I experienced that myself, having worked in multiple different companies from startups, scaleups and large corperations.

However since everyone now adopts AI and implementation speed is undeniable multiples faster. I mean it's not just implementation, but also a good part of DevOps. But the rest of the organization moves in the same speed as before. Even if the company uses AI in the other departments (my company does basically throw AI at everything, I guess you know what I mean), they still can't competet with the productivity change in software development.

The blockers are now decisions, requirements and communication. That's not completly new, but now its >95% of the time. I implement features in hours that would have taken days before (I am not a pure DevOps Engineer). And it's not the review process itself that blocks us (We use AI in reviews as well, because otherwise it would be impossible), it's the normal company processes and pace.

Don't get me wrong here, I kind of enjoy it a bit, because I can use a lot of time for learning, building stuff that I think is worth improving, but I think we have a general problem here that is basically systematic to every large organization. And I see that so called "AI native organizations" (what ever that means), will probably overtake tech companies in the long term.

I have a really good comparsion, because I am working with a startup as a side gig and my main job is in a mid-sized tech company. In the Startup we (2 devs) built a product that would have taken several months by a 5-person team in the past and the reason is mostly: decisions and communication.

Do you see that in your company?

My conclusion is that we need to make engineers owners of the feature/product + infra, otherwise we won't see much productivity gains and this means also that management layers need to be cut, because they are the bottleneck currently. The idea of centralized DevOps will is going to die I guess.

I wrote a browser extension that adds a "you're in PROD, are you sure?" confirm to destructive AWS Console clicks. Capture-phase listener cancels the click, shows a dialog, replays the click if you confirm.

Trouble: some actions re-render their menu between confirm and replay, so the replayed click hit a detached node and did nothing. My fix was a short bypass window after confirming — for a few seconds, clicks pass straight through so the replay works.

The window wasn't scoped to the action you confirmed. It was global. So for ~6 seconds after confirming any destructive action, every other one was unguarded. Confirm a Lambda delete, click Terminate on an EC2 instance three seconds later, and it just goes.

A tester reported it as "the popup stops appearing sometimes." Not a UI glitch — the guardrail was switching itself off, on a timer, every time it ran.

Fix is one line — scope the window to the confirmed action:

// before
if (Date.now() < bypassUntil) return;
// after
if (Date.now() < bypassUntil && rule.label === bypassLabel) return;

The lesson that stuck: a bypass is a security control too. I wrote mine as a UI workaround, so I reviewed it like a rendering bug, not a security decision. Anything that turns your protection off — even briefly — deserves the same scrutiny as the protection itself.

Anyone else hit this class of bug — a temporary exception that was broader than intended — in auth caches, feature flags, rate-limit bypasses?