I'm interning for free and I bluffed to my boss that patch management seemed easy. I got put in charge of making sure that an AI can automate patch management in 3 days.
I can't code for shit and I was brought on to do RPA stuff. DId I make a mistake or is Patching easy enough for a total beginner moron to Cybersec(ks) like me to do?
I still have the chance to turn down the assignment and go back to what I was doing before.
lol your boss called you on your bullshit in the most painful way possible. just tell him that you overestimated yourself but that you can still do it albeit with a lot of time spent learning. you can learn new things, right?
Yeah, I can. I just told my supervisor that I bit off a bit more than I could chew. My issue wasn't the deadline, I could probably nolife for 72 hours and figure it out but the problem is that the guy im going to directly work under is a pajeet in india and I have to wait until he's awake to start learning. I was going to just go along with it but I just got a fever today and my entire workflow is fricked.
Hm, OK, I see. From what you describe, it doesn't seem too difficult, but the timeframe worries me. I'll ask my supervisor to keep me in consideration for patching work, but frick man, I really loose cannoned there in the noon meeting.
Thanks for the help lads.
The thing that makes no sense as to what you actually fricking mean for AI automation for patch management since automation is basically built into any patch servers.
AI is the newest tool anon, we need to internally align around it and put our whole weight behind implementation of AI technology in all of our core competencies. Do your best effort to raise this up the flagpole before it's time for pencils down.
But you don't know how to do it...
It's do or don't. Are you a team player or not, anon?
Yes which is why I have an SOP created for our Jr. Admins to follow along with a documented process for what updates when, maintenance windows for patching, the timeline of when updates are pulled->approved->pushed, and management approval of said process.
>My guess is they saw some article about "Using AI to automate your patching process will bring your company into the future and help seal up cracks!" or something like that and now they want to do that.
The thing is patching basically is automated, the whole have AI add to it doesn't make sense. This is basically a process issue that's resolved by setting up auto-approval roles.
Good luck I seriously dunno what the frick you mean AI managing unless you are going to model an AI to test applications and patches to validate services running.
that's some other anon shitposting
I couldn't have summed it up better myself, sir. I'm on it!
I don't actually have an answer for that. The DevOps people are working on making a medical chatbot, and another team is working on some ai in banking shit so I guess shoehorning AI into all the processes is what management is trying to do, but this is the first time I've worked at a tech company and I just kinda bullshitted my way into it.
My guess is they saw some article about "Using AI to automate your patching process will bring your company into the future and help seal up cracks!" or something like that and now they want to do that.
Sorry if this makes no sense. I'm kinda delirious from a fever at the moment.
I dunno man, it just seems like a gimmick for now until some else figures it out
>so I guess shoehorning AI into all the processes is what management is trying to do, but this is the first time I've worked at a tech company and I just kinda bullshitted my way into it.
Jesus christ i can't wait for an entire economy to fricking crumble.
>The DevOps people are working on a medical chatbot
You do not work at a company. You work in an insane asylum run by Indians pretending to do things (which is now 40% of our economy). Just say you already did the needful and it's done. No one actually checks on anything, you'll be fine.
>AI in charge of patch management
Well at least you got some busy work. Funfact:patch management is super fricking boring the person who assigned it to you knew the person who told them to look into it was full of shit and passed off that product to you.
Patch management in a nutshell is
>have group of OS's receive updates early, usually being dev/test and for desktops some subset of users
>roll out patches via WSUS to windows and run scripts for your linux stuff
>have WSUS auto approve updates after 30 days so bad patches get pulled from release when needed
>PDQ or whatever for app management updates
>check to make sure shit isn't fricked
>check backups are on prod machines
>roll out to prod during your approved maintenance windows or dates
>rinse and repeat
AI automating that is kinda dumb because most update services will just "auto approve" and push after X days unless stopped.
>I'm going to add AI as the corner stone for my first tech job!
holy frick anon hope you will learn your lesson.
UNDER PROMISE
OVER DELIVER
>holy frick anon hope you will learn your lesson.
I think I will lol. I'm going to try to get the deadline extended instead or just go back to RPA. But there's a chance I can just learn from the guy I'll be working under, and from what the other anon described, it really doesn't seem too hard, I'm just dogshit at coding with anything but Data Science shit.
Patch management of what, anon? If you want to make it hard, increase the scope to include everything. If you want to make it easy decrease the scope to include nothing.
>Patch management of what, anon?
Making sure that the comapny's Virtual Machines and shit are all updated and don't break anything. I think.
Im just interning here so I can get somewhere better and get paid down the line.