99
LLM Idolatrine: Why no one wants your agentic PRs
(blog.magosomni.com)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
Yeah that's a real good point. I focused a lot on the short term issues of agentic slop but you're right the long term impact of this is going to be staggering.
100%. Something I wanted to touch on in my post but cut because I couldn't weave it in well was more on the relationship with "The Problem" and "The Code". Pre-AI coding acted as a forcing function for the problem context. It's really hard to effectively build software without understanding what you're ultimately driving towards. With agentic coding we're stripping that forcing function out.
Institutional knowledge is already something that's been hard to quantify and value by C-suites and now you're ripping out the crucial mechanism for building that.
I see a lot of memes with people being like "in 5 years we're just gonna press yes and not understand what the agent is doing" and I keep thinking "why do people think this is funny?"
I understand why you cut it. There is a lot that you could dig into there, and you would really have to go into detail it you wanna convince the suits that can only think in terms of KPIs.
The forcing function is a good way of looking at it. We’re not really doing the same thing but faster. We’re doing less, and that naturally takes less time. AI made understanding optional.
I kinda wonder to what extent coding is actually a domain that AI is uniquely “good at” vs simply how well coding activities are able to survive on artifacts which are produced but not understood.
It seems like something we were already exceptionally capable of tolerating, compared to other sectors.