3,798 karma · joined September 2, 2013
Ever since Fable and Sol level LLMs/agents came online, I have ceased to look at the code. I recently launched a project for a client that integrated many many systems, has considerable traffic with low latency requirements and everything just.. works. I've never had to do this little firefighting when launching a project of that complexity and scale. It's been liberating and I was able to focus mostly on polish and QoL improvements of the stack and systems. What a time to be alive for a technical builder.
Sidenote, I've not had a single one of my smartphones crack a screen since 2008 when I got my first smartphone, take that for what it's worth.
I like the plane example from the article,but I think in reality it will be like code. 1.5 years ago engineers would routinely say that they still write code by hand here or there to keep their skills sharp, and that's just not something you hear much if at all.
If an SRE is faced with a situation an AI can't solve, then said SRE will use the AI systems to triage further, point it to different places and so on.
This works for SREs with pre-AI experience and intuition, possibly less so with new recruits coming in post-AI. I don't know what the solution to this is, maybe practice drills is it, but I have a hunch the entire field will be subsumed, same as many other engineering fields.
There is only so much need for taste and judgement, before even that has been incorporated into the models.
And why compare to the brain? Mostly because of complexity. I can't interface with a bacteria in any meaningful way, but I can interface with an LLM to a significant degree.
AI doesn't exist in a vacuum, it's the sum of training, inputs and outputs. If I give it novel inputs, the outputs won't be solely within the limits of their training. If I use it as part of a pipeline, the end result of the pipeline too won't be forced within the limits of AI training.