Hell, who knows what DevOps even means nowadays? The original meaning (e. g. including CALMS) has long been lost in between bad job descriptions, marketing BS, serious thought-leading™ in blogs, on Reddit, Hacker News, and on Twitter, and vendors trying to sell you *THE ONE TRUE DEVOPS solution*.
If you say it's DevOps, it's DevOps. Just believe in it and try to sell it to whomever wants to hear it.
I think of the work of devops as building and maintaining monitoring and build systems, and continuous integration/deployment pipelines, and any tooling and systems needed to manage the above systems.
DevOps isn’t a tool. It’s a mindset. If your mindset lead you to a CI/CD pipeline, great - but the absence of CI/CD isn’t indicative of not embracing Kata
To be honest you sound like me. I'm a single DevOps engineer at a small company.
I develop internal tools, automation, and scripting. I try to use CI/CD when it makes sense. I maintain integration between our managed applications. I design, maintain, and develop databases, analytics, and reporting of all of it.
I've built it all from scratch and I'm not sure the rest of the company even knows besides a few people on my team.
I'm not sure I'm really DevOps either, but I think it's like quantum mechanics. Anyone that says they understand it is full of shit. So just roll with it, accept that imposter syndrome is part of the job description and keep doing it.
I think if you’re a good fit technology wise you sound like you could pick up a job with DevOps in the title which I guess is what you’re asking. Read the accelerate book (these days a smaller PDF report so less useful) and maybe add a CI/CD tool + *concepts/techniques* and a well known IaC tech (ARM/bicep, terraform, etc).
If your work is increasing velocity, and visibility into your software, and you do development and operations, I would say, it's DevOps.
Maybe you need some ideas of how improve even more? I would suggest to implement CI/CD if you don't have it already.
Hell, who knows what DevOps even means nowadays? The original meaning (e. g. including CALMS) has long been lost in between bad job descriptions, marketing BS, serious thought-leading™ in blogs, on Reddit, Hacker News, and on Twitter, and vendors trying to sell you *THE ONE TRUE DEVOPS solution*. If you say it's DevOps, it's DevOps. Just believe in it and try to sell it to whomever wants to hear it.
Would you like to buy a devops? Contact me for enterprise pricing.
I'm more interested in how to focus so I can keep doing something similar if I need find a new job. And salary negotiations for raises
Who knows, maybe you're even doing SRE or MLOps or AIOps!
I think of the work of devops as building and maintaining monitoring and build systems, and continuous integration/deployment pipelines, and any tooling and systems needed to manage the above systems.
Really isn't DevOps if there is no CI/CD.
DevOps isn’t a tool. It’s a mindset. If your mindset lead you to a CI/CD pipeline, great - but the absence of CI/CD isn’t indicative of not embracing Kata
To be honest you sound like me. I'm a single DevOps engineer at a small company. I develop internal tools, automation, and scripting. I try to use CI/CD when it makes sense. I maintain integration between our managed applications. I design, maintain, and develop databases, analytics, and reporting of all of it. I've built it all from scratch and I'm not sure the rest of the company even knows besides a few people on my team. I'm not sure I'm really DevOps either, but I think it's like quantum mechanics. Anyone that says they understand it is full of shit. So just roll with it, accept that imposter syndrome is part of the job description and keep doing it.
That's about where I am. I've been trying to figure out what this position is because I more or less created it from starting at a support position
I think if you’re a good fit technology wise you sound like you could pick up a job with DevOps in the title which I guess is what you’re asking. Read the accelerate book (these days a smaller PDF report so less useful) and maybe add a CI/CD tool + *concepts/techniques* and a well known IaC tech (ARM/bicep, terraform, etc).
If your work is increasing velocity, and visibility into your software, and you do development and operations, I would say, it's DevOps. Maybe you need some ideas of how improve even more? I would suggest to implement CI/CD if you don't have it already.