I'm not in DevOps at all, though I've worked with quite a few in my current position. I'm in production support, so I do quite a bit of troubleshooting and change management on behalf of internal and external users. Plus plenty of scripting and API integrations for myself and my team.
Automation is my personal mantra. I've been using the CLI and scripting since I was 12 years old (dragged kicking and screaming into the GUI world, and never felt quite at home in it). I now have a pretty bespoke Linux UI I built myself, and use desktop automation like a fiend on both Linux and macOS (can you tell I'm a UNIX guy at heart?).
I think DevOps would be a great fit for my skill set, I use git and can program in Bash, zsh, and Python (among familiarity with quite a few other languages). I also have some solid training and experience with AWS and GCP.
Your description of ClickOps sounds very foreign to me, it seems GUIs for managing this stuff can be quite limited especially if you want to do things in ways the GUI developer didn't envision.
I just don't have experience with a lot of the CI/CD technologies, Infrastructure as Code, and collaborating with more than one other developer on any moderately sized code project. I'm interested in learning more on how to get into this space, seeing as I don't feel I fit in the spectrum you gave.
Azure Technical Leader with extensive backend experience in .NET.
Enthusiastic about all types of automation.
Passionate about writing - and striving to find more time for it.
Well, the terminology changed throughout years; and DevOps became a buzzword lately, which for some is easier to understand.
However it simply translates into
Development (Dev) and Operations (Ops)
Are you already developing some automations, setting them up and troubleshooting production systems?
Well, bravo! 👏 In the sense already explained above, you might already be a "DevOps", but you just don't know it (yet) 😉
Personally, I still prefer to use GUI on desktop, for mundane tasks. 🤔 However, when we're discussing about automations, then CLI is the way 🤘
On the other hand, when I was talking about ClickOps, I was referring more to the manual tasks/operations that can be done within a browser for setting up or configuring some cloud resources (a few examples: repositories, permissions; container registries, key vaults, etc)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm not in DevOps at all, though I've worked with quite a few in my current position. I'm in production support, so I do quite a bit of troubleshooting and change management on behalf of internal and external users. Plus plenty of scripting and API integrations for myself and my team.
Automation is my personal mantra. I've been using the CLI and scripting since I was 12 years old (dragged kicking and screaming into the GUI world, and never felt quite at home in it). I now have a pretty bespoke Linux UI I built myself, and use desktop automation like a fiend on both Linux and macOS (can you tell I'm a UNIX guy at heart?).
I think DevOps would be a great fit for my skill set, I use git and can program in Bash, zsh, and Python (among familiarity with quite a few other languages). I also have some solid training and experience with AWS and GCP.
Your description of ClickOps sounds very foreign to me, it seems GUIs for managing this stuff can be quite limited especially if you want to do things in ways the GUI developer didn't envision.
I just don't have experience with a lot of the CI/CD technologies, Infrastructure as Code, and collaborating with more than one other developer on any moderately sized code project. I'm interested in learning more on how to get into this space, seeing as I don't feel I fit in the spectrum you gave.
Well, the terminology changed throughout years; and DevOps became a buzzword lately, which for some is easier to understand.
However it simply translates into
Development (Dev) and Operations (Ops)
Are you already developing some automations, setting them up and troubleshooting production systems?
Well, bravo! 👏 In the sense already explained above, you might already be a "DevOps", but you just don't know it (yet) 😉
Personally, I still prefer to use GUI on desktop, for mundane tasks. 🤔 However, when we're discussing about automations, then CLI is the way 🤘
On the other hand, when I was talking about ClickOps, I was referring more to the manual tasks/operations that can be done within a browser for setting up or configuring some cloud resources (a few examples: repositories, permissions; container registries, key vaults, etc)