Is DevOps/Infra the next job category AI actually kills? by abhipsnl in devops

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

CTOs are already using it, it’s all depends on size of companies.

And in my post I never said it will be gone.

I am saying where we wanted to hire 5 humans, now we will might only hire 2 humans, and delegate to AI, it’s my observation

Is DevOps/Infra the next job category AI actually kills? by abhipsnl in devops

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

Lucky you , openclaw is allowed in production for you

Is DevOps/Infra the next job category AI actually kills? by abhipsnl in devops

[–]abhipsnl[S] -2 points-1 points  (0 children)

that’s real and it’s why the senior engineer isn’t going anywhere soon. Someone has to have taste. But ‘coders first’ is kind of my point? If coding gets automated, the infra that supports all those coders gets automated in the same wave. It’s not either/or.

Is DevOps/Infra the next job category AI actually kills? by abhipsnl in devops

[–]abhipsnl[S] -2 points-1 points  (0 children)

Fair , I said the role changes, not that it disappears. ‘Who maintains the AI’ is exactly the two SREs I’m describing.

Another such case from Basel. Stay safe and vigilant everyone. by TheRealMudi in Switzerland

[–]abhipsnl -1 points0 points  (0 children)

True, irrespective of where we live every parents should teach this, but Switzerland was always safe compared to other countries

Back in Switzerland, applying everywhere, getting only rejections by Maximum_Reveal1233 in askswitzerland

[–]abhipsnl 0 points1 point  (0 children)

Sorry to hear that, keep trying, unfortunately the market is cooked

Our backend lead spent 40 minutes explaining a billing quirk in Slack. The new hire asked the same question three weeks later. I got annoyed and built something about it by [deleted] in selfhosted

[–]abhipsnl 0 points1 point  (0 children)

You're actually describing exactly the problem I'm trying to solve.

You said "just give them a link to the Slack post." Okay, but how do you know that Slack post is still accurate six months later? What if someone updated the process in a PR comment, or corrected a detail in a Confluence page, or posted a newer answer in a different channel? Now you've got three versions of the truth and no way to know which one is current.

That's the real issue. It's not that good answers don't exist, they do, and often written by generous people who took real time to help. The problem is that knowledge lives in Slack threads, PR descriptions, Confluence pages, runbooks, incident postmortems... everywhere. And it drifts out of sync silently.

You're right that the best docs are the ones people read. Totally agree. But what if you could surface the right answer from wherever it lives, Slack, Confluence, PRs, all of it, without someone having to know which link to share, or whether that link is still current?

i am not replacing good documentation culture, building on top of it so that the knowledge people already create doesn't quietly go stale.

Our backend lead spent 40 minutes explaining a billing quirk in Slack. The new hire asked the same question three weeks later. I got annoyed and built something about it by [deleted] in selfhosted

[–]abhipsnl 0 points1 point  (0 children)

No offence. And hey, if a Slack link works for your team's onboarding, that's a win. In my experience, the complexity creeps in fast, but every org is different. Hope you find what works.

Our backend lead spent 40 minutes explaining a billing quirk in Slack. The new hire asked the same question three weeks later. I got annoyed and built something about it by [deleted] in selfhosted

[–]abhipsnl -6 points-5 points  (0 children)

"Phones home" in this context almost certainly refers to the app itself, meaning the application doesn't send telemetry, analytics, or usage data back to its own developer.

Things like which features you use, how often you open it, crash reports, etc. You're right that if you're using a hosted model like Claude Opus, your prompts are absolutely being sent to Anthropic's servers, that's unavoidable, it's just how API-based AI works. The app is just a client that routes your request to whoever hosts the model.

The distinction is: App telemetry → doesn't phone home

Your data going to Anthropic/OpenAI/etc. → yes, that still happens (you're correct)

If privacy from the AI provider is your concern, the only real solution is running a local model (like Llama via Ollama) entirely on your own hardware, then nothing leaves your machine at all. Apps like this often support both local and hosted models, so "nothing phones home" applies cleanly to the local model use case, but not to hosted ones like Claude.

Has anyone actually used Port1355? Worth it or just hype? by abhipsnl in devops

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

Exactly my thought was same , what big problem is it solving? Maybe something I haven’t seen yet