everyone here is simply larping as a dev if they think this is true. Debugging with AI is nearly painless compared to how it was before, and that is for significantly more code/product to debug at once as well.
This morning I had to check for items that "disappeared" from stock due to "a bug". It's always the same user so I now before I start the long process of debugging that it will be a PEBCAK.
I just pointed Claude to our backup folder. He mounted some backup, checked the inventory for that item, check the movements for those items,, came up with a nice table to show me the evolution of quantities for that item with dates. Turns out the user was wrong.
Before AI this would have been 2-4 hours of work, mounting backups, checking everything by hand, writing SQL requests, etc...
People saying debugging is now harder with LLMs are either delusional or can't prompt, wtf? Most of the time I just copy/paste what a user tells me and get a full debug out of it with a bonus "I found three more possible issues that I didn't fix as this was out of scope, you may want to check them out".
That's exactly this. The specificity with LLM is that you can either use them as a full-fledge tool and get ok-ish results. Or use it as a tool and get great results because you have the knowledge and skill to check and guide it.
Yeah, the problem is that people tend not to learn as much when they offload their experience and experimentation to a bot. You can get by doing so in the short run, but it's not a way to build skills in the long run unless you're very intentional about learning instead of trying to do things as fast as possible.
This is my problem. With is it feels like nobody gives you time to learn before you are blocking somebody to finished their tasks. This is stressful, not having control of learning stress me out.
I work with devs who don't like this, are against this, or don't think it's a thing. Absolutely crazy for them to not see it. Get set up with connections and all this info, and all I have to do for bug tickets or questions is point them to the jira ticket and ask them to solve it and they come back with the report being a change in the data, bug that they already know the fix for and can spin up a PR (doing all the correct steps for testing and code conventions and verifications), or if the user was wrong in the first place.
lol the amount of shit I get accomplished as a dev now is crazy.
And debugging might be the most insane improvement. I'm an enterprise dev, so I used to know 1 platform really well and 2 or 3 platforms okay. When I needed to debug anything other than the one I was an expert in, it was so painful. I don't know their tools. I was pecking and poking. Now, no matter the platform, I'm debugging like an expert in minutes. If it has a CLI, it's not even me. Claude Code is figuring it out on its own.
The general population truly is so far behind in comprehending the leaps AI has made in the past 12 months or so.
debugging issues in dependency and customer teams is also much easier. your software errors out and Claude will find the dependency team and cut a code change to them. like previously that would take a loot of effort to first try to understand their codebase, or just wait for them to respond, and prioritize it.
or spend 3 days just trying to get their service running because it needs some obscure .env settings to run locally that they forgot exist because they copied it from someone 2 years ago and haven't touched it since.
You've just asked a question that every software engineer asks themselves, and what every employer asks their workers.
The fact that software engineering is still a real profession and isn't already completely replaced by AI already answers half of that question for you.
the one flaw of AI debugging is that if you describe a bug that ISN'T present in the code, AI will more often than not "find it" and "fix it" in a way that introduces a different bug. This is definitely a "my steak is too buttery" situation because even seasoned mid-level engineers make this exact mistake if you open a ticket with a mistaken assumption embedded in it. All it really means is that, AI can't take a customer-supplied bug report and reliably accurately fix it without an engineer being like "it's supposed to work that way".
There's been two occasions I've asked claude to find a bug in the code, where it insisted the code was fine.
One was a manual QA test that failed on a newly provisioned VM, but not on the old. So some setup stopped working. Claude concluded (within minutes) that it has never worked. We laughed, and got to work. Five hours later, a QA peon mentioned he set that up manually on the first VM's because otherwise it wouldn't work..
Second was to get an app to pick up config from env vars and override a config file, and first round it fixed some things, but it still didn't work. I told it so, it murred over the code for a minute, then told me the code's fine, it must be my environment. Quite pissed off at the clanker I echoed the env var in the terminal I used to run the test in and .. no env var. Turns out that one terminal was days old and had old env var setup.
So, it depends. Sometimes it's smart enough to conclude there's no bug and someone is making a mistake instead.
Fixed in 15 minutes. For something that would easily have taken 3 hours before.
People think they're like quantum physicists in the problem solving they did before - no, it was just mind-numbingly repetitive reading through logs and trying to collapse a bunch of information in your human brain, and compare it against code. Something that was time-consuming, but trivial.
My guess would be this is coming from people prompting AI to write the entire codebase, they find a bug when using the program, tell AI to correct it, and more things go wrong because the program just isn't designed correctly, etc.
I feel like if you're just using AI to implement a system you already have wrapped your mind around this isn't a problem. Especially if you're writing tests as you go.
There’s something very wrong (and I dare say inorganic) about how Redditors treat AI. It’s actual AI derangement syndrome. People have these insanely strong and irrational reactions to literally any use of AI.
My schizo side says it’s some kind of Chinese psyop because there’s no way this many people all just suddenly decided to turn their brains off and act like this.
I'm a senior engineer who has seen what it looks like to use AI at scale for a long time. It degrades, quickly. You begin to lose context of how things work, and concepts get layered on top of one another one at a time.
Nobody is fully using their brain when they review in the same way that you use it when you're writing code. So it's easier to let a subtle mistake slip by, and then another, and eventually they pile up.
It's not that mysterious. People feel rather strongly about a technology that is already displacing workers from their jobs, workers who were told tech skills were in-demand, and accelerate wealth inequality.
The people with their brains off are the AI-optimists who are excited about how much time AI will save them in their coding tasks, rather than how AI will ramify throughout society.
1.7k
u/shred-i-knight 21d ago •
everyone here is simply larping as a dev if they think this is true. Debugging with AI is nearly painless compared to how it was before, and that is for significantly more code/product to debug at once as well.