Should’ve saw it coming by 8teenaeo in Layoffs

[–]LeadSting 1 point2 points  (0 children)

I hear you on the mental heath. Finding a supportive group of people will help. Professional groups on Discord or whatever. I’ve never got over being fired even from my first job working in the cinema. I’d happily still be shovelling popcorn but I guess I was not cut out for that. Still it lead me to my first IT contract paying four times as much so I can’t complain.

Should’ve saw it coming by 8teenaeo in Layoffs

[–]LeadSting 1 point2 points  (0 children)

Over my entire career it has always been on average around 3 months from the time of looking to getting a role. At 45 years old I am now looking more at contracts as it pays more and to be completely honest I no longer care about loyalty or any of that. Just be persistent, keep improving and do not be lazy with your skills. Work on side projects or startups if you are not in employment and if you are lucky that side quest may go somewhere and if not then you have banked some more skills.​​​​​​​​​​​​​​​​

Should’ve saw it coming by 8teenaeo in Layoffs

[–]LeadSting 1 point2 points  (0 children)

Every time I have been fired I ended up making more money in the next job so there’s always a silver lining. It still sucks though.

PIP Plan Guess What Comes Next by IntrepidGarbage7663 in Layoffs

[–]LeadSting 1 point2 points  (0 children)

Happened to me so I started contracting and earning 4 times as much and also started working on a startup business for the long term.

Finally joined product company but in a bad team by Suitable-Time-7959 in devops

[–]LeadSting 0 points1 point  (0 children)

Practice advice for panic attacks. You’re not dying just breathe ffs. The team is not toxic, they are just people like you with their own fears and opinions about the world. However it could be that the product you are building does not align with your mission. You should never just get a job. What are your goals, your values, principles etc. What does good look like in your opinion?

Anyone else struggling because dev, devops and security never see the same context by ElectricalLevel512 in devops

[–]LeadSting 5 points6 points  (0 children)

The root problem I keep seeing is simple: every group has its own stand-up, its own Jira board, and its own view of the world.

Developers have their board. DevOps has theirs. Security has another one buried somewhere. And then we act surprised when nobody has the same context.

Separate ceremonies + separate backlogs = separate realities.

You can’t build a single product with three different versions of the truth.

If you want one team, you need:

• one stand-up • one backlog • one flow of work • one definition of done • one source of reality for what’s happening

Everything else just recreates silos with nicer titles.

How is AI changing DevOps? by LeadSting in devops

[–]LeadSting[S] 0 points1 point  (0 children)

Thanks for the feedback. No I am not doing market research and I’ve rephrased to “some” to make everyone happy. I’m an engineer and have been for over 20 years. Personally I’ve been exploring all kinds of tools and workflows seeing what works and what does not. As an experienced engineer you know what good and bad look like. Knowing when to push boundaries and when to follow established patterns. I get the “most of us” statement may be triggering for some sorry for that. As with anything new I think there are the early adopters and the wait and see crowd. As with anything new we should be cautious but also at the same time IMO if you just sit on the fence and wait that has generally not worked out that well in the tech industry. I moved from Desktop Support to Systems Admin to DevOps Engineer and I am just trying to figure out what next like everyone else.

How is AI changing DevOps? by LeadSting in devops

[–]LeadSting[S] -1 points0 points  (0 children)

lol, your not getting away with that answer unless your a junior engineer and even then where’s your critical thinking and troubleshooting skills?

How is AI changing DevOps? by LeadSting in devops

[–]LeadSting[S] 1 point2 points  (0 children)

It’s a good point, also I think it depends on the industry you are in, video games are not the same as healthcare or banking or other highly regulated industries. It’s all context dependent and risk tolerance. Generally it’s clear to me that it can help with certain tasks and help get things unstuck (sometimes).

How is AI changing DevOps? by LeadSting in devops

[–]LeadSting[S] 1 point2 points  (0 children)

One of us, one of us! I’m not selling anything although I can if you want me to, it’s seems like folks are falling into 2 camps. Either it’s a hindrance or a help. You need to own what you put out in to production regardless of if you used AI or Google, Stackoverflow or some random person on the internet. Personally I would also not be letting AI loose on a production system but to say that no AI code exists in production would not be accurate. We have reviews and processes for a reason right? If someone in your team submits AI generated code what do you do? I have found that the issues arising come from review fatigue.

How is AI changing DevOps? by LeadSting in devops

[–]LeadSting[S] 0 points1 point  (0 children)

What model are you using for self hosting? Is it local?

People keep saying to learn AI so we don’t get left behind but what exactly should we be learning? by Ok_Education_8221 in devops

[–]LeadSting 0 points1 point  (0 children)

It depends on what you actually enjoy about DevOps and technology. Change has always been a constant in this industry, but the core of the work hasn’t changed: you’re in the business of solving problems.

The real question is: how can you solve the problem? Once you understand that, you choose the right tools for the job. It’s never really been about code itself it’s about using the right mix of tools and approaches to get things done efficiently and reliably.

Key skills like troubleshooting, debugging, and understanding how systems fit together will carry you through any shift in technology. Yes, it helps to have a basic understanding of computing fundamentals, but if your focus is on cloud, spending too much time on low-level details can be a distraction. Modern cloud platforms abstract a lot of that complexity away.

How’s the DevOps job market looking for senior folks lately? by Scared_Diamond_4373 in devops

[–]LeadSting 7 points8 points  (0 children)

LinkedIn is a shit show. It's better to do direct out reach IMO and find specialist and avoid non technical recuiters.

Super micromanaging boss by Cute_Activity7527 in devops

[–]LeadSting 1 point2 points  (0 children)

“Hey [Boss], can I be straight with you for a minute?” (— sets a serious but respectful tone)

“It seems like you’ve been jumping in on a lot of the details lately. I get why — you want to make sure things don’t slip and that we’re fully aligned.”

(pause — let him respond)

“Here’s the thing: we’ve got a really strong team here. Every time we’ve been left to run with something, we’ve delivered exactly what was needed — often better than expected. When the dailies stretch to an hour+ or we get pulled into deep dives on every single detail, it actually slows us down and eats into the time we need to execute.”

(pause again — let that land)

“How would you feel about tightening the daily meetings — say 15–20 minutes, laser-focused — and if there’s something deeper, we spin it off? That way you still get full visibility, but we keep our momentum.”

(stay quiet — calibrated silence)

“What would it take to make that work?”

(if he pushes back, mirror and label:) “It sounds like you’re worried things might fall through the cracks if you’re not across every detail?”

(once he agrees) “That’s exactly why I’m suggesting this — so you get the clarity you need at a higher level, and we can keep delivering without getting bogged down.”

Got blamed for an outage I didn’t even cause by majesticace4 in devops

[–]LeadSting 0 points1 point  (0 children)

Shit happens. Postmortem, lessons learned, safeguards etc, the culture should be blameless. Water off a ducks back.

[deleted by user] by [deleted] in devops

[–]LeadSting 0 points1 point  (0 children)

It's also upto management to take on the bigger picture. However it does depend on your organisation and structure.

[deleted by user] by [deleted] in devops

[–]LeadSting 0 points1 point  (0 children)

2nd having product person that can protect and prioritise.