41–50 of 114 posts
This is not devops, this is someone managing yaml to allow an org to avoid doing devops.
Devops is practiced by everyone. If there are people asking the same questions over and over there is a feedback loop / education / automation problem and THAT is the part that makes a job devops.
This isn’t “DevOps”. This is “IT Support”.
But honestly, if you aren’t embedded into a team where developers and infrastructure folks are working together - you aren’t doing anything differently than old school operations people did 25 years ago
I really loathe that sales engineers stole the term Solutions Engineer which was previously used to basically mean support/services engineer (technical generalist), a mostly post-sales role. It's pedantic, but I watched it happen in real time, my company's HR even asked if we could change our team titles to help out the sales team since they wanted the more appealing title to use. The reason it annoys me so much is t…
I am post sales, billable staff consultant who leads projects. I’m “delivery”. I focus on one project at a time and dig deep into requirements and the implementation and/or strategy docs.
Earlier quoted context omitted.
Use " Solutions architect " maybe instead ?
That title has long been used as a post sales analyst (custom work for $)
ProServe consultants (full time employees) are never called SAs
Earlier quoted context omitted.
> I'd still classify what they're doing as DevOps type of work. This is very, very wrong. Why do you think that?
devops means a lot of different things to different people
I am a software developer. I went to college to learn software development. Two years ago, they tried to tack DevOps on to my job description. I told them "no thanks", then had to find another job. I found one and am MUCH happier not having to do that DevOps crap. No offense, but it a soul-draining undertaking, and I like writing code ... ONLY!
Earlier quoted context omitted.
I have a different opinion. :) DevOps is great feedback to the engineering team. Too many alarms or alarms at unsocial hours? The engineering team should feel that pain. Too hard to push? The engineering team should feel that pain. Strange hard to diagnose alarms? Yep, the engineering team should feel that pain! The feedback is very important to keeping the opex costs under control. However, I think the author and I…
This sounds very adversarial to me. I’m glad our devops team doesn’t think like you.
Earlier quoted context omitted.
Sales is amazing but if your companies sales people require engineering to build POCs a lot of the times or always have to sell some custom solutions, then it wastes a lot of resources and it usually indicates the company is losing product market fit.
That is true. My current work is in bespoke environments with mainly non-technical buyers who have been burned in the past. Our POCs are pretty minor lifts to build credibility and have worked extremely well. If you're working in SaaS or commodity products and have to run POCs a lot, you're totally correct.
There are people willing to pay for convenience AND security at the same time (hire someone else to manage the problem, and they're the 'key').
My path went from engineering-aligned (math) to engineering management back to engineering to product to program management to solutions engineering to account executive. Honestly I had a negative connotation about sales for most of my career, but turns out I really love it. The exposure to different problems every day is awesome and more like a puzzle than work to me. I feel a bit of reverse imposter syndrome though…
Earlier quoted context omitted.
This sounds very adversarial to me. I’m glad our devops team doesn’t think like you.
If you have a “DevOps team” - they are operations and you aren’t getting any of the benefits of a DevOps mindset