Does low level devops mean you’re looking into server configs and yaml files, and ensuring deploys go out correctly?
Because that easily transitions into IT work with physical servers or managing cloud servers.
Look into compTIA certs for IT. Or getting AWS certs.
As a engineer, I know very little of devops beyond the basics, and see you wizards as masters of those domains. And the team who manages my department’s devops also handle a bunch of other “closer-to-the-metal” asks and that can’t be replaced with AI in the near future.
That’s pretty much exactly what I do and why I call myself a glorified script kiddy. I don’t understand any of it either, I’ve just learned to memorize how to deploy.
In essence, I literally don’t know what I’m doing.
My only professional credentials in IT is a single non-binding sysadmin cert from a local college. Don’t ask me how I got this job in the first place, I couldn’t explain it if my life depended on it.
Does low level devops mean you’re looking into server configs and yaml files, and ensuring deploys go out correctly?
Because that easily transitions into IT work with physical servers or managing cloud servers.
Look into compTIA certs for IT. Or getting AWS certs.
As a engineer, I know very little of devops beyond the basics, and see you wizards as masters of those domains. And the team who manages my department’s devops also handle a bunch of other “closer-to-the-metal” asks and that can’t be replaced with AI in the near future.
That’s pretty much exactly what I do and why I call myself a glorified script kiddy. I don’t understand any of it either, I’ve just learned to memorize how to deploy. In essence, I literally don’t know what I’m doing.
My only professional credentials in IT is a single non-binding sysadmin cert from a local college. Don’t ask me how I got this job in the first place, I couldn’t explain it if my life depended on it.