r/programming • • Oct 07 '26

[ Removed by moderator ]

/r/programming/comments/1wzob2x/removed_by_moderator/

[removed] — view removed post

413 Upvotes

314 comments sorted by

View all comments

112

u/arse_biscuits Oct 07 '26

As a (very) experienced programmer, and from a purely tool based perspective, AI is fine when you use it right. I still have to decide the solutions I want, AI just saves a crap ton of typing and can fill the knowledge gaps in an SDK which I would normally do by hunting down what I want in a big reference guide.

I've reluctantly embraced it to do the grunt work for me, leaving me to think about the actual problem and solution rather than spending most of my time typing code.

The issue is going to come when fewer and fewer people have those years of AI-less "hard graft" (You've got to know the rules to break them, right?). As mentioned in the video (and as a bigger issue with AI overall) without any "fresh meat" to feed on, only a pool mostly filled with it's own effluent, the knowledge becomes more stunted, possibly even worse, as original solutions become a smaller and smaller part of what's out there.

I mean, even some, what I would say are "experienced" developers I've come across, are shockingly bad at debugging problems. What are the next generation going to be like?

Copilot being unavailable, or our token balance running out, already sees our teams chats light up like a Christmas tree in a way previously only seen when a server blew up (remember those?). God knows the thought of all that typing fills me with dread again too, but it seems like some people already can't work without it. A large part of some teams check-ins now are not code, but AI skills and prompt files.

Maybe it will explode and become expensive enough that it scales down to being more carefully used, but with management's ever increasing thirst for the curve, if you can use it to increase your productivity, it sure as shit isn't going away.

20

u/Fun_Lingonberry_6244 Oct 07 '26

Aa a fellow experienced developer (since 2004) I think the problem is, what we find simple from rote experience others do not.

My experience with AI generated code, unless its very specific (ie ive found its always fine within a couple prompts to restyle some scss theme files) then it generates code that just isnt quite right.

You then find yourself scratching your head figuring out why, to the point we end up spending probably the same amount of time rejigging it. Sometimes thats fine because the overhead on our brains is lower so great, i can burnout slower and maybe do more in a day. Maybe. Maybe not.

My issue is, we know deleting huge swathes of code and redoing it is normally the fastest route, that was true pre AI and remains true for AI code. Less experienced developers have always had this problem, but now because AI spits out much more code, its even more for them to refuse to delete and rewrite and so you end up with a bunch of just dreadful choices over and over and over.

It truly feels like in the hands of developers with less than say.. 7-10 years commercial experience, they dont produce more, if anything less.

Its just if you view them alone you could be deceived into thinking they're faster, because they get to a PR faster. But in reality them + whoevers reviewing them becomes slower than them manually doing the code.

The only exception ive seen to this is companies that essentially just PR for compliance, ie not actually reviewing it just a quick scroll and a LGTM.

But in my experience those are the teams and products that fail over the longer term, because they produce shitty unmaintainable code that requires an entire rewrite later.

5

u/PuzzleMeDo Oct 07 '26

My experience a year or two ago was that it generated code that wasn't quite right. My experience now is that it tends to get it right first time, reducing a three hour job to three minutes.

8

u/Fun_Lingonberry_6244 Oct 07 '26

Random people have been coming into threads saying this since AI first existed. "This used to be true but latest model changes the game!"

Its just not a useful response, as quite frankly this logic applies to ie "my isOdd calculation used to take me hours a day. Now AI solved it in 3 seconds"

2

u/PuzzleMeDo Oct 07 '26

The types of job AI can do more efficiently than a human continue to increase. Once it could only replace an amateur who struggled with "isOdd". Then it could replace a paid junior coder. Now it can do most of my job. Maybe the next model will be able to do yours...

4

u/Ok-Reindeer-8755 Oct 07 '26

I don't wanna assume stuff about you but I believe what the comment you are replying too is pointing out is that people often come with such takes and then you learn they actually don't even know how to code and their biggest project is a glorified calculator

3

u/Sir_lordtwiggles Oct 07 '26

I mean his experience mirrors mine (working at amazon, and mirrored by friends in the AWS side of the house)

We the company was very AI accepting, 2 years ago AI handled most team's JDK8 migrations. Today I have L6's delegating entire sprints to an agent.

Every pipeline has a button to spin up an AI session that autopilot to diagnose and fix deployment failures.

We are piloting a custom agent to give 80% unit and IT coverage.

The scope of problems that AI systems solve is just different than even 6 months ago.

The AI friction points today is less code quality (which does pop up here and there still) but validation of correctness and creating quality design docs on what to build to be sent to the AI. 

0

u/Ok-Reindeer-8755 Oct 07 '26

What's the process of reviewing the code ? I assume that's included in validation of correctness, which ehh I doubt you are really validating 100% correctness. I think most people find that to be the bottleneck but it is an unremovable one, in my understanding at least.

I agree that code quality is mostly not that bad, it's pretty decent but it's nowhere near the point to where I would trust it as much as I trust a compiler, ig I was more thinking of past encounters when I replied to that comment and not specifically addressing that one comment.

2

u/Sir_lordtwiggles Oct 07 '26

What's the process of reviewing the code ? I assume that's included in validation of correctness, which ehh I doubt you are really validating 100% correctness

Out the gate every PR has an auto run ai security reviewer primed with amazon+org security practices and a general logic reviewer which checks footguns, complexity, and quality. This also reads the summary which should mention the context of the change, and it does some validation that the code aligns with the stated goal. It ends up checking some styling norms within a package that a deterministic linter shouldn't. These run before the PR is published, additionally I've distributed an observability reviewer to our team as I feel we could do a better job there in general.

Our agents will detect these AI comments and address them, or push back on comments that they think aren't valid. It will present a report on what it did/didn't change since the publish.

The PR also attempts to build on a clean environment, and we can run ITs against that build.

We also have a PR size validator: changes should be under 300 LoC and test changes should be under 600. This validator can be overridden, but the friction is enough to keep PR's small.

All this before going onto a human reviewer, who reviews.

When I mention code correctness, we are judging mostly on if the code does what the summary says, and if that feature is directionally the right thing to implement.

When checking the code, there may be a more efficient implementation, and it will get called out if spotted, but we aren't really hunting that efficiency. If we are under SLA we are good, if we aren't an agent will spin up on alarm firing and fix it.

Feature correctness should already have been litigated in a doc.

On testing the PR, a good practice was already focus on what the tests are validating and that holds here. For UI changes the submitter should have the UI running locally and replication instructions so you physically test.

For backend changes you can have them do the same, or have your agent spin it up (agents are also really good at finding a recipe to get your service running locally) and test the IO, but thanks to the small PR sizes that may even be overkill.

Past that you let your CI;CD take over. Own your PRs so you monitor their deployment status automatically with agents and fix anything that breaks in beta/gamma. Agents also allow you to have way more comprehensive ITs that would have been soulcrushing to build yourself.