66 karma · joined March 19, 2025
The level of scale and complexity a big tech SRE has to deal with on a constant day-to-day is a very imbalanced proposition. A lot of people, in my experience, are not fully comprehending.
You have to be a jack-of-all-trades and a master of all.
I wrote this to start a conversation and as I get a better idea ill try to share that as well
https://research.google/blog/turboquant-redefining-ai-effici...
I 100% agree with this in a individual person sense, but in a humanity sense someone does understand linux very deeply and is very intentional on how they change it which to me is how I gain trust in it.
does trust change when the entire SLDC is AI?
I wanted to touch on this point but then this post started getting WAY too long.
>the only change AI brings is that even first person developers don't know anymore what the fuck they just deployed.
This to me is going to make your first point 100x worse in every damn way
Don't get me wrong. I think the future is very bright for software. I have friends who are scientist and biomedical professionals and I am excited to see what they are able to do with the powers of software where they don't need to care about syntax and can only lead with their intentions.
The rage bait part is mainly my frustrations manifesting. As an SRE my annoyances came off a little bit when it comes to how fast developers are shipping vs how fast our rails can maintain things.
>How are you handling the drift problem? Auto-discovery polling, change events from cloud providers, or something else?
We built a pretty awesome approach to handling the drift problem. We do a combination of indexing, change even capture and then user behavior. So if a user is looking for a information we pull the live value first.
I will check that tool out.
People want it to be significantly more proactive over time, things like root cause analysis, security-style probing, or guided investigations rather than just visibility.
There’s interest in going deeper on telemetry and using it to surface higher-level insights, not just raw data or links out to other tools.
A lot of people ask whether it can eventually write to environments. The direction that’s resonated most is doing this first for new or greenfield environments. For example, going from a prototype to a production-ready AWS setup in a more agentic way. For existing environments, trust and safety are still the gating factors.
My takeaway is that read-only context earns trust first, and write access has to be very deliberate and staged.