r/AskProgrammers • • 6d ago

Am I missing something about agentic coding?

I’ve been thinking for quite some time about all this „AI writing all the code“, „too many pull requests to review, just let AI review them“, and „we ship so many features a day“ talk...

I’m a SWE with professional experience (pre-AI-era) and currently in my last year of studying CS. I use AI regularly for coding, but only recently started trying agentic coding. It works, but I honestly don’t really see the benefits when it comes to software quality.

A few years ago, everyone kept saying that lines of code are not a meaningful metric for software quality, and now suddenly people are bragging about how many features they shipped or how much code their agent generated.

I’ve recently been working on a project where I code manually and use AI in chat as usual, and honestly I feel like I wouldn’t be faster using agents. Most of the time, I spend thinking about how to design the solution rather than actually implementing it. The coding itself is usually done pretty quickly once I know what I want to do. And when I write it manually, it is exactly how I planned it, and I know every step in the process and exactly what it’s doing (also in regards to safety critical systems).

So I don’t really get why I should use agents for that. From what I’ve experienced, one prompt can trigger changes across many files, and then you obviously have to review all of that, which can easily throw you out of context. I feel like as a professional engineer, the coding part itself is often already quick, and I would argue that you end up spending a similar amount of time tweaking, fixing, and re-prompting an agent to get to the same level of thoroughness and context-awareness you would have had by doing it manually.

Don’t get me wrong, I do think AI is very useful, especially for debugging, fixing errors, finding documentation, or generating examples quickly. In those areas, it definitely accelerates the process for me. But when it comes to just generating code, I really don’t see that much of a benefit.

Am I the only one who feels this way, or does anyone else think about it like this?

188 Upvotes

305 comments sorted by

13

u/MaximumMeaning9728 6d ago

You have professional experience as an SWE but you’re a senior CS student? lol

7

u/Perfect-Mortgage3698 6d ago

Yes, about 8+ years in the field. We do have that in Switzerland

5

u/someRedditUser3012 6d ago

If you already have 8+ years of professional experience, why are you going to school for it?

It is actually professional programming and not hobby programming or helping a friend type experience?

5

u/Perfect-Mortgage3698 5d ago edited 5d ago

No, it‘s what‘s called an apprenticeship in Switzerland. It‘s common that you land a full-time or part-time job after and you can do your bachelors if you‘d like. In the end it‘s an additional degree, in-depth knowledge and more pay

2

u/someRedditUser3012 5d ago

Interesting, ty for sharing

→ More replies (5)

4

u/Great-Use-3149 6d ago

Some jobs may require education too (regulated industries)

1

u/Vizeroth1 6d ago

I never finished my degree and since I work in education it definitely feels like I could benefit from going back. I didn’t learn much in the last CS course I took, but I did learn something and I felt it was worth the time I spent going to classes and doing the work. When you’re mostly self-taught it can be hard to even figure out where the gaps are to go out and fill them.

→ More replies (1)

1

u/sdeptnoob1 6d ago

Some people want to complete that goal

1

u/inighthawki 6d ago

Most college students do internships or coops in a professional/enterprise setting. "I have professional experience" is not the same as "I am a professional"

3

u/Perfect-Mortgage3698 5d ago

No, it‘s not an internship. In Switzerland you can work in a full-/ part-time position and do your bachelors.

1

u/inighthawki 5d ago

That is a good clarification, I appreciate that. Though it is still worth noting that I think the other person's attempt at discrediting someone having no professional experience just because they are in school is more or less just an attack. Many senior students in college or university do in fact have professional experience (many of which intern at big corporations/enterprises, such as big tech companies).

2

u/Perfect-Mortgage3698 5d ago

Absolutely, I agree, and that also wasn’t even the main point of the post. Somehow, this sentence caused a bit of ragebait lol, even though different education systems exist and not everyone is aware of that.

5

u/Raestkjoot 5d ago

I honestly don’t really see the benefits when it comes to software quality.

This is where your confusion is coming from. The benefits are not in software quality, but in quantity. While you've been thinking about what you're doing and making sure your code is of high quality, you could have just pumped out a bunch of stuff using agents.

In my experience quantity often wins over quality as people want to move fast, but I absolutely agree with you. I find coding without agents gives me a much better knowledge of the code base and where it should improve and how things should be implemented.

1

u/blindsdog 5d ago

The benefits are definitely in quality too if you use it right. It has all the knowledge of stack overflow, it’s on you if you don’t use it.

1

u/rando1-6180 4d ago

Yep. Quality is overlooked. It has access to "code samples" at a scale a single human can't. From all of that, it is your opportunity to fine tune and orchestrate the quality you want. You want unit tests? Ask for it. You want convention over configuration? Ask for it. You want to know what will most likely break in 3, 9 and 16 months and the likely cause and how avoid those issues or make them transparent to troubleshoot? Ask for it.

Quantity still plays big as a commerical reality. Customers pay for features, not quality code. Fixing bugs and patching is the cost to the software house/SaaS provider.

1

u/chessto 4d ago

Quantity wins over quality until shit starts crashing and cost starts piling.

1

u/Table-Rich 2d ago

This has been an issue for so long, and we still haven't learned.

1

u/escollera_labs 1d ago

then you fix it, but you can't fix the Perfect Software that was never implemented in any way to begin with

1

u/chessto 15h ago

Of course, you fix a data breach, a missing trail of auditable logs, a random error that allows some foreign agent to scan your db and collect PII from your users and gives some extra work for your legal team.

Or if you're dealing with mission critical systems then you just fix death.

→ More replies (2)

1

u/anm767 7h ago

Microsoft already proved how this works. From very beginning they sell software that sort of works and sometimes crashes, sales allow them to develop further and now they are dominating the market.

While the "perfect" operating system is still in development for 30 years with 0 sales.

→ More replies (2)

1

u/neutrino_boy 16h ago

Don't even think this is quite true. If you use AI effectively you cam improve quality too. We should steer away from these nice saying like "quality over quantity" the facts are when used well they can write better quality code than 99.9% humans too.

16

u/FuggaDucker 6d ago

By myself, I am just one seasoned 30+ year c++ engineer.
With agents, I am an army that can easily do the work of a whole team of engineers.

Without me guiding it, AI will make some stupid crap too.
Keeping it in line seems to be the game.

As of now, I feel like AI writes better code than I do but I design better systems.

4

u/someRedditUser3012 6d ago

The struggle is we have the experience and could code this ourselves. AI for us is an augmentation.

I get the feeling a lot of the newer grads have it more of a crutch. The fact that OP doesnt see any benefits of using AI seems to prove my point that.

Plus ,this account is a whole month old...maybe its coincidence, but this seems to smell of AI

6

u/rafark 5d ago

with agents, I am an army that can easily do the work of a whole team of engineers 

You’re 100% not reading all that code. How do you know it does not have bugs or vulnerabilities. Because every time I generate code I always read it and there’s always at least one thing the ai missed or got wrong that doesn’t show up immediately but will on specific scenarios. You’re not catching these bugs if you don’t read the code and they will pile up with time eventually becoming part of the spec themselves because the ai will use the code as a reference/base for your next prompts. 

9

u/Mabenue 5d ago • This

You don’t know that with code written by hand. It’s a poor argument, anyone who’s worked in software engineering should know that human written code is often full of bugs and that’s it’s really hard to catch them in code review. The most effective way to avoid them is to build systems to prevent bugs in the first place. Which means extensive automated tests and building ways for agents to rapidly verify their work.

6

u/poolback 5d ago

Absolutely right. Automated test, mutation testing, gating minimum quality level. The problem isn't new to AI.

→ More replies (4)

4

u/patmull 5d ago

How do you not loose track of your knowledge then? Are you willing to risk to become just manager of your "agents"? Aren't you little afraid you would become the typical out of touch manager who doesn't understand the field the manager is working in? Human manager can be still good through being good psychologists and motivate knowledge workers right, but LLM platforms don't really need it...

2

u/Mabenue 5d ago

What do mean lose track of your knowledge? In any sufficiently big software project you don’t know how everything works anyway.

You have to think in terms of the whole system. There’s still lots to be involved in when coding with agents but it’s more along the broader strokes. I don’t need to know who every api endpoint that performs a CRUD action works down to minute detail. I do like to know that they’re implemented though consistently through the codebase and are following a pattern I’m happy with.

I think what comes with experience is being comfortable in not understanding everything, but being confident you can quickly gain understanding when needed. It’s something I was pretty good at before AI and with its help it’s even easier.

3

u/Wonderful-Habit-139 4d ago

All of your arguments in this thread have been "humans write bugs anyway", "you don't know how everything works anyway".

Just crabs in a bucket, pulling everyone to do worse and worse software engineering.

2

u/met0xff 2d ago

Yeah I think there's a very personal view and an organization view. I have worked on a codebase for a decade and that one was cleaner and better understood by me than the new agent codebases we have.

But from the global view of my org we have thousands of repos that have been written by probably 6-7 work generations of developers. Everyone's long gone and for arcane parts you either had to ask through 15 people to perhaps find someone who still knows about it, or we often spent days tracing behavior of an API call through 4 repos in 3 different languages :).

Now I send Claude to figure out what exactly happens when you send a specific query to one service and it comes back with an analysis over all the code pieces, database queries, services etc. involved ... And documents it.

From the perspective of the organization there's now more insight than ever. For the individual it's worse.

→ More replies (2)
→ More replies (1)

2

u/Particular_Ant7977 5d ago

Exactly. I have an MVP that I started writing with no AI tools a couple years ago. I recently let Opus do a review of the code and it pointed out several issues that I had not thought about before. I hate to admit it, but I am not considering my abilities to be above AI anymore. It writes better than me, refactors better than me, and writes compehensive tests 100 times better than me. I let it work in chunks that I can keep up with reviewing myself, and never gets anything committed that I don't understand. Software development is no art form, it's a very algorithmic engineering process which machines do very well, if instructed so.

→ More replies (3)

3

u/neppo95 5d ago

Newsflash, people don’t write perfect code either. Arguably more often they screw up.

Peer reviewing exists for a reason, something that hasn’t changed with AI.

2

u/JeanCasteaux 5d ago

Not a valid argument. At least people understand what they've done if they have really done it (or they should do another job really). Understanding is important, it's not about generating "perfect" code on the first try.

2

u/Particular_Ant7977 5d ago

What makes you think AI tools don't understand the code they write?

3

u/RetroGrid_io 5d ago

In a literal sense, AI doesn't "understand" anything. Word prediction aka LLM is becoming good enough that it may not matter.

→ More replies (11)
→ More replies (1)
→ More replies (6)

2

u/FuggaDucker 5d ago

Speak for yourself. I read 100% of the code.
As an engineering manager, I read all of the code a team produces anyway.
I do not let it get ahead of me.

1

u/thenextvinnie 4d ago

If that is the case, I promise your delivery rate is abysmal compared to where it could be.

→ More replies (4)

2

u/thenextvinnie 4d ago

I always feel like people who ask questions like yours have extremely limited real-world experience, to be very honest.

My friend, I've been involved over 20 years in several dozens of systems human software devs have created. They are full of bugs and vulnerabilities. They are full of comments like "don't change this, it looks wrong but it works even though we're not sure why".

I have systems I've written myself pre-AI that are so big that span several years to the point where I don't remember how the system works without doing a deep dive.

Perhaps there have been cases where brilliant engineers handcrafted perfect, pristine code that they understood at the assembly level and where they were never under pressures of deadlines or budgets or flawed human teammates. But these are far from new problems.

1

u/met0xff 2d ago

I found that for individuals who work on small, isolated problems it's obviously a downgrade in knowledge about this piece. I've worked for a decade on a small runtime that obviously I knew well and would be worried to lose that knowledge by having an agent roam around there.

But in the org I am in with a couple thousands of repos I found most only knew their little piece, few had the big picture and even worse, most little pieces had no real .. mental owners anymore because the people left a decade ago There are arcane java 1.4 services nobody dares to touch anymore. Or "dared" because now we can have agents roam through the whole thing, document behavior and limitations, from there have tests and finally migrate all that crap. Which was totally infeasible before with hundred engineers drowning in a backlog for 3 years anyways (and no money to hire more besides you can't hope to put 300 people on a huge system tomorrow and they'd solve it in 3 months without drowning in communication overhead).

It even enables product people now to get answers like "how does the system behave when a user does X" whereas before they had to hunt 10 engineers down who might have a guess or would have to simulate it.

Of course that a lot of code gets produced that nobody ever understood AND that it's probably as much code in a year now than in the 15 years before does worry me.

Doesn't mean the stuff that was there was perfect and every little piece was understood in every little detail before. We just had the last dev leave who worked on a C++ video processing pipeline for 10 years. Even though we started onboarding another one a while ago, no way he'll have all the knowledge about it. But working with an agent it becomes manageable.

Of course people will always come with a theoretical "just train more devs, put more owners on each piece" but if you're not google making billions of profit the margins are rarely there and there are always competitors with a cheaper solution. Especially when it's more custom solutions where you can't scale the product as easily

1

u/Engineering_Geek 5d ago

Systems design at the end of the day. How well is your architecture constructed such that each bug that comes up is properly traceable and fixable without requiring major overhauls? What is your testing and CI / CD pipeline like? Testing environment? How well can you explain the high level ideas to those around you? Code won't be perfect, it doesn't have to be. It needs to be fixable and traceable.

There are exceptions to this, namely critical software, like aircraft software, spacecraft guidance, etc., where you can't tolerate bugs and every dollar spent on devs is worth it.

1

u/rafark 5d ago

How well your architecture is constructed doesn’t matter if you’re not reading the changes to the code. The ai will slowly (and maybe not even) start changing it with every pr. 

That codebase will be very different in weeks/months/years if no one reads the code. 

Same thing applies to the testing environment. Your tests won’t matter if no one reads them. Worse they can give you a false sense of security. It’s no secret how AIs like Claude will try to cheat their way to a green test. 

You’re basically trusting the whole thing to ai. And you know what in theory, this could work in a perfect world, but we don’t live in one and AIs hallucinate and make very convincing mistakes all the time. 

When you stop reading the code you can’t tell for sure it works reliably.  

→ More replies (2)

1

u/RangePsychological41 1d ago

Bro has written C++ for 30 years. What he says is pretty much gospel to me.

2

u/niccolololo 6d ago

I don't know about better, but definitely faster

→ More replies (20)

2

u/Aware-Individual-827 5d ago

Every decision left to the AI is a tradeoff that you don't know about. This is pretty bad. I'm talking not only design but also code wise. It constantly misinterpret code, implement good looking code that does what is asked but creates a bug elsewhere, etc. 

Overall you really need to guardrail it aggressively to have good results in a production environment. I'm questionning the gain related to AI as I feel gaslight every now and then by AI. 

2

u/Select-Way-1168 5d ago

It really doesn't though.

1

u/Great-Use-3149 6d ago

What does "better code" mean of your system designs are better? Beautiful looking code?

6

u/FuggaDucker 6d ago

more consistent in every way.
no changes to any paradigms whatsoever.
comments are consistent. function names are polished. refactoring leaves no trail if I ask for it.

AI makes some dumb designs.
I think all of us that use it continually spot and simplify what it came up with.

1

u/poolback 5d ago

You know you have tools to detect this stuff that AI can use to iterate on the code?

1

u/thisismyfavoritename 5d ago

isn't "dumb design" synonym with bad code though

2

u/Superb_Raccoon 5d ago

Oh no, you can have a dumb design with immaculate code. Points at IBM Software

2

u/thisismyfavoritename 5d ago

agreed but if i'd say AI can code better than me then i'd mostly be thinking about that kind of stuff as well, not like syntax naming etc

→ More replies (1)

1

u/Useful-Agency_ 6d ago

What would you redommend to do to be a good systems designer ?

1

u/Great-Use-3149 5d ago

Not use AI for coding and use AI to try to overload your system. Then try to improve the system yourself . You should eventually gain intuition on what works better

1

u/karasko_ 5d ago

Exactly my thoughts! I have 3-4 years less experience than you, but anyway, I totally agree that people massively misunderstand the importance of good design, and the importance of simplest possible solution

1

u/LeDYoM 5d ago

Of course, C++ is a programming language where you dont need to look at the tiny details, no possibility of shooting on your foot. We all know that...

1

u/chessto 4d ago

You're an army of one guy who has nobody to review his output nor check his sanity.

When I play the guitar and nobody is listening I also sound like Joe Satriani.

1

u/FuggaDucker 4d ago

You sound hurt by my confidence.
You really think as a seasoned engineer I work alone?
I am talking about what I can do without help.

I review and refine every last bit of it and I have a team of 5 other engineers that review all pull requests.
Are you aware of ANY commercial software development that takes place in your bubble?

1

u/chessto 4d ago

You confuse arrogance with confidence.

>With agents, I am an army that can easily do the work of a whole team of engineers.
No, with agents you're still a seasoned 30+ years C++ engineer but now you can produce more output than anyone can humanely review or check, so you trust your process and believe your own delusion. I'd never trade a fellow engineer for an AI agent nor would I compare them.

> Are you aware of ANY commercial software development that takes place in your bubble?
I don't know what you mean, been working for 25+ years myself in commercial software, I guess I'm aware of some of it.

1

u/ssssssddh 3d ago

This is how I feel as well. Been in web dev for 15 years. Agents crush research and implementation tasks but they'll also happily build the wrong shit and they never leave a PR review saying we should close the PR and rethink our approach.

I was worried about my career for a hot minute, but then I realized it's still just about critical thinking, problem solving, technical knowledge, and experience. But now I've got a robot to wrestle with implementation details for me while I focus on the details I actually care about.

1

u/KevinJRussell 10h ago

With agents, I am an army that can easily do the work of a whole team of engineers.

You can't, but AI is very, very effective at manipulating people into thinking they can.

1

u/FuggaDucker 9h ago

I am sure you know better than I do what I can do using whatever experience you have.

2

u/KevinJRussell 8h ago

Yes, my professional experience has enabled me to spot fakers.

→ More replies (1)

1

u/newyorkerTechie 1h ago

It’s like riding a horse. You can’t sit on it, you have to ride.

4

u/Dazzling-Try-7499 10h ago • Bravo

What you're experiencing is the diminishing returns of the tool. 

At low gear, it's great. Meaning, if you're in the IDE and you have done all the planning and architecture and you need help with a method or a bug, it's very accurate and there's low chance of slop. This is a 2X-5X gain and it's fabulous.

At medium gear, where you give the terminal access to whole repo, ymmv. A long detailed prompt with technical details, the right MCPs and skills, you might get a good response for a whole feature, but it will be making some decisions for you, and those might be good decisions, but they weren't what you would chosen. This could be a 10X gain, and I have seen it, but I've also had to reject some PRs from coworkers where it went in the wrong direction.

Then there's high gear, or vibe coding. This is where you give it very little direction and ask for the moon. This is the mythical 1000X productivity. IMHO as a SWE with 25 years experience, this is a bad idea. This is only ok for quick POCs and testing out new ideas. It seems so cool to watch it throw up a whole house for you in minutes while you drink coffee, but it is making a LOT of decisions for you. And inevitably you will have to change or work around those decisions later.

At the end of the day, I recommend people take the low gear win and move on. Otherwise you're creating work for yourself later. The people who brag about 1000X productivity are not real engineers. They don't have to support these machines year after year and live with the architecture.

Another way to think about it, if you want to get philosophical, is input space vs output space. If you give a tool very little input, how many things could it create? And if it's just a single button that makes a notepad app, wouldn't we already have that?

→ More replies (2)

2

u/Decent_Perception676 5d ago

Correct, output is not the same as outcome. As someone recently said to me: “AI has made it more apparent than ever where we don’t know what to build”. Even seeing arguments to ditch agile and go back to waterfall, to create proper space and time for the design process.

2

u/magick_bandit 5d ago

Is this the thread where I point out that Anthropic software has had a growing number of open issues for the last 6 months.

They have effectively unlimited compute and agents and can’t close issues faster than they’re being reported.

2

u/HugeCannoli 5d ago

Here is the dark secret I learned from 25 years in the business: nobody gives a damn about code quality.

1

u/Independent-Chair-27 5d ago

No but they do care about security issues when they occur. They also care about performance and cost to run. Plus time to resolve live issues.

Meeting objectives etc.

Nobody is an expert yet but my take is that you can crank out code quickly. But you need guardrails to know what you want.

This isn't necessarily what's perceived as traditional code quality in the traditional sense

1

u/Morph_Games 4d ago

nobody gives a damn about code quality

Hey, I do! Has it advanced my career? Definitely not.

1

u/ChainInteresting5972 4d ago

Why so many programmers never make it up the chain

1

u/Nervous-String-7928 7m ago

Yes they do. They just don't call it "code quality". Instead they say " why does this piece of shit keep crashing?".

3

u/Great-Use-3149 6d ago

The reason why people are faster is because they've turned of their thinking, review and maintenance.

I'm sure this will work great in the future /s

2

u/amasterblaster 5d ago

M43 22+ years coding for work. Also masc AI 2013 (very biased)

Skill files, NLP approaches to making decisions, decision networks, and chaining probabilistic transformers together with LLMs is literally what programming is becoming, and it's a massively scalable skill. As one person, I can manager and optimize token usage and get easily better quality and 10x more done per day while ON MY PHONE hanging out with my lady (what I did for 4 hours today).

My setup is
I use Gitea for task management locally, workflow triggers tied to different development stages, and automated processes. I have an A2A connection where my supervisor agent can respond to problems when I'm away (testing now). I usually just manage the manager thread, where I can see agent questions pop up and chime in to control the project.

I also have security and refactoring triggers, as well as API monitors that respond automatically to logs and security concerns. In addition, I scan news and tool ideas and have those added as tickets. I add notes, review key PRs, and coordinate refactors.

This is the PRESENT. I just interviewed for a staff position at a new company, and they are hiring me to set up this process for them. So this will be standard practice in trhe next 12-24 months I really believe.

1

u/JeanCasteaux 5d ago

Let's talk about this setup in 24 months when LLM prices have tripled.

2

u/-Hydro7- 5d ago

Are you even aware of how fast the capability to price ratio is increasing? Rewind back 24 months from now. Sonnet 3.5 was one of the best general programming models available. Today, Quen3.5 9B is roughly on its level of performance.

Similarly, I expect that 24 months from now this setup to work with local models instead of today’s frontier, for dirt cheap. And for the same price point as today in that future’s frontier, we’ll get capabilities that are alien in performance compared to today. Yes, there will likely be even higher tier subs at that point, to provide even more performance, but if you just look at the price as the only variable, you completely miss out on what you get for every dollar.

And this is a linear extrapolation of future capabilities too, which is unrealistically conservative.

1

u/HugeCannoli 5d ago

once they hook you in, they will squeeze. They can't sell ads like google has done for 20 years. Imagine that for every single google search for the past 20 years you had to pay. What do you think the web would look like today?

2

u/amasterblaster 5d ago

My bet -- Lol they wont tripple haha.

LLMs will be DEAD in 24 months. You can pin this comment. This is my bet.

Its too long now to explain why, but they are being distilled down to code and will be replaced by purpose built stochastic networks that are industry specialized, as the higfhest ROI business on earth right now is using LLMS to not use LLMs for sub calls.

SO LLMS will always exist, but usage is being optimized out of every single tool call.

Edit: LLMs are inherently not defensible, as they build their own replacement machines, so the whole industry is going to explode I think, and in the wake we will have a new class of edge focused sub processours that can do 80% of the job of LLMs. I dont think the economy can take LLMs, but I dont think inference and stochastic coordination is going anywhere personally.

1

u/patmull 5d ago

What is the software you applied your workflow? Before the interview, did you applied it for your own projects or other company or you had customers?

1

u/amasterblaster 5d ago

git tea, opencode, are the major drivers. The rest is largely custom code.

I think the fact that I could describe how I built it, and that it took 4 days, was what got me the job. *** Next interview. I do not have the job offer, and I'm not sure I want it! I'm in the middle of launching my product an a recruiter called me for a dev ops role.

1

u/PerformanceThick2232 5d ago

Not all companies have such shit code standards you know

1

u/yung_squeezy 5d ago

Bad take. Opus code is as good as my code with proper examples guidelines. If you are not 4x faster now than a year ago, the problem is you, and you will be replaced by those that are. Cope all you want.

1

u/chessto 4d ago

if opus is as good as your code then your code was shit to begin with.

→ More replies (8)

1

u/ChainInteresting5972 4d ago

all the big ones do lol

1

u/amelech 1d ago

This is way more advanced than what I'm doing but definitely heading this way. I've been building a Claude mod to better manage orchestration settings like agent roles, subagent models, compaction rules and agent prompts. Also a plugin to track work in a visual kanban board that the agents move stuff across. Do you have any resources for recommended reading?

→ More replies (6)

2

u/RatherNott 5d ago

 AI data centers are being constructed at an alarming rate, and there are already 8 billion prompts per day, with billions more planned and on the way.

The effect this has on the climate when we are already so close to irreversible tipping points is often unknown by AI users.

https://www.theguardian.com/environment/ng-interactive/2026/oct/22/finland-google-felling-trees-datacentre

https://m.youtube.com/watch?v=5p426fSlYH4

Using it also contributes to a dystopic survailence state.

https://m.youtube.com/watch?v=5lYsO4k7OIY   

1

u/hyperadapted 5d ago

stop the cap

1

u/RatherNott 5d ago

Will do boss.

1

u/SeenTooMuchToo 6d ago

I’m glad to see this question, because I feel the same way. But I think it’s probably because most of my use is for small features or bug fixes on the order of 100 or 200 lines of code in an 80,000 line mature application.

I can see how on a greenfield project, or major refacing, or making substantial changes over many different files in a large application could benefit more from agents than I think I would.

But I’m speaking from inexperienced and ignorance here so I’m not sure

1

u/laxika 6d ago

The amount of features you can pump out with AI is incredible. Especially in the startup phase. It is not lines of code that matter, nor PRs but features.

It takes some skill though. You need to be good at reviewing, reading code and architecture (to be able to orchestrate the work in parallel). Albeit knowing what to read is more important than actual reading speed.

1

u/Great-Use-3149 6d ago

And then you end up with longer review times, technical debt and inability to reason about anything as you have no mental model of the codebass.

2

u/laxika 6d ago

You need to have a mental model of the codebase. You need to refactor and ask around with the AI tooling if needed. Coding with AI is not vibecoding where you do zero reviews. You should generally know where things are (which module, etc).

1

u/Great-Use-3149 6d ago

Reading the output of someone (virtual person) elses code doesn't really build a model, firstly because physical actions (writing/typing) cause much more retention and focus, and secondly because the logic being written isn't your own — only the ideas and general requirements are.

Are you sure this holds up in the long run, especially when the agents can no longer reason through the large code base (at least not in a short-tims manner)? How do you even think anything about the project then?

→ More replies (4)

1

u/Superb_Raccoon 5d ago

You need to have a mental model of the codebase.

No I don't because I had the AI make one as it built the code. And I track code to contract, contract to code.

1

u/SaltCusp 6d ago

You need a portfolio of your code if you want your agents to write in your style and you need quality semantics to articulate your query.

It's not that ai can write better code than you can, it's that it can write similar code faster.

1

u/Great-Use-3149 6d ago

Uhh, what is it with other accounts' comments in this post. They all sound the same like bots  despite their age being a few years.

Has everyone really turned off thinking? Or are the only people commenting people who haven't written code in the kast 5+ years, even before AI?

1

u/yuehuang 6d ago

Have some fun by building something hard, for example, build bootstrap a text base OS, or build a personal shopify store front and backend, or build photoshop. These are just one month pet projects with AI.

Since it is a pet project, skip the code review part or focus on design. Enjoy cheap tokens we have today because it won't last forever.

1

u/Serializedrequests 6d ago edited 6d ago

Use a really good model like Opus 5.5 when it isn't being actively screwed up, and for better or for worse you will see a difference. A very exciting, addictive and depressing difference. It can find all references to something across an entire codebase as quickly and as intelligently as an IDE, and perform a much safer refactor than I can on a feature I half forget. And flag important bugs and security issues while it's at it, then tie it up with a bow with a great commit message. Not using them to at least check your work is crazy. You can treat them like code calculators for many use cases now.

Some models really struggle with English, so I often rewrite the commit messages and such, or have special prompts that produce more legible output, but still.

It is the same with writing a feature: If you actually spell out the feature in enough detail, a good model will now not miss things that the average competent human would. The issue is more that it is very difficult to specify a large feature in enough detail, so you often need to rework all the details the agent guessed on and end up not saving much time.

Otherwise yes, I completely agree with you. In most businesses, somebody has to own it. It really depends on the project. The agent swarms people are talking about would be a total disaster at my job and trash the project instantly in spite of my efforts to keep good context documents. We have infinitely more trouble validating code than writing it, because the domain is difficult and we are responsible, and still given enough authority to write code in the way that allows us to be responsible. So we do take a lot of time thinking about solutions, and just a few hours to write it, such that who does the writing doesn't make much difference. I agree with you - just learn to type lol, even if it's just prompts. (But now you can simply dictate prompts, which I refuse to do.)

Swarms of features is usually a terrible idea. More code != better product. More features != better product. IMO where agents really help the most is with stuff at the edge of your domain that doesn't matter. Like CI pipeline YAML files. Eff ever writing one of those again. Bash - I've studied bash my entire life, and any model can write better bash than me as of two years ago. There are plenty of domains where it just doesn't matter, so use an agent and move on. There are also domains with a lot of small details than an agent might miss if you don't take your time, but you also might miss details. Use the agent as a second set of eyes.

If I were to tie this up with a bow, I would say:

  • Different businesses have vastly different goals and incentives. The people sh*tting out hundreds of features are more likely at startup-like environments. A lot of us already had massive piles of tech debt, and don't need humans or agents adding to it.

  • Think creatively. Send agents on research projects to find out things you want to know. Use them to check your work. Write a supremely lazy PR that touches way too much stuff, and have an agent pare it back for you.

1

u/Professional_Mood_62 6d ago

Perhaps you need to see a seasoned engineer working with agents? I feel a lot of people think like this until they learn to properly use the available tools, including myself

1

u/HaMMeReD 6d ago

I literally run some of my github's on autopilot using my coordinator. It'll audit the code, create a scorecard (both by objective and subjective reasoning) create a list of issues to resolve to raise that score, triage and cull those tickets, intake them, work, validate and merge them, all on their own.

My autopilot is repo-specified, so if I want to focus on some area, I can easily just point it, and it'll research and iterate in that direction on it's own.

It's a fork of Open AI Symphony, works with Codex. It has it's own machine, runs 24/7. Does pretty good work imo, frequently fixes bugs I recognize before I tell it, and makes general improvements in the directions I point it.

GitHub - ahammer/crescendo: Crescendo runs autonomous coding agents across several repositories from one local service. Based on OpenAI's Symphony. · GitHub

1

u/Exact_Ad942 6d ago

It is normal that you don't feel faster when you are working on a project that you are familiar with. Because you already have the knowledge and instantly know exactly where to make change, while AI takes some time to read and pick up. But that flips when you work on a project you are unfamiliar with, or using a new library, etc. AI reads and picks up much faster than you, they know the best fit API, data types, algorithms, tools which you might not already know exist. And you can easily verify and learn new stuff along with it. It is important to make the prompt in manageable scope, make the changes incremental so that you don't get overwhelmed when reviewing.

1

u/Illustrious-Lime-878 6d ago

Yes, software companies sell products, not lines of code. More abstractly, software quantity should actually be its magnitude of practical value not LoC. BUT individual contributors are often judged by metrics like commits or lines of code.

Similar to back in the days where it was popular to assign "points" to tasks many people tried to sandbag every task they thought would inevitably be assigned to them to maximize the amount of points they were finishing, despite of course the amount of points being completely functionally meaningless, this lead to the rate of points a given team tending to increase and looking good on charts execs would use to track performance, and then tended to make them want to increase the adoption of those processes.

Such is the case with AI, which has an amazing ability to make it appear like the one using it it doing a massive amount of work, even if in reality the work is pushed to other areas like review or testing (or often its taking credit for what would be considered "copying" before - like using an existing 3rd party solution). It is largely "bench maxing" performance metrics essentially. And since individuals are incentivized to maximize these metrics, so they are maximized in aggregate. And so is the push from higher levels to increase the usage. The resulting "magnitude" of software value isn't necessarily related (although likely increased at a much smaller rate - it is a useful tool in the end).

1

u/GreenBlueStar 6d ago

I’ve recently been working on a project where I code manually and use AI in chat as usual, and honestly I feel like I wouldn’t be faster using agents. Most of the time, I spend thinking about how to design the solution rather than actually implementing it. The coding itself is usually done pretty quickly once I know what I want to do. And when I write it manually, it is exactly how I planned it, and I know every step in the process and exactly what it’s doing (also in regards to safety critical systems).
^
Key word..."A Project"

Try working with 4 projects, simultaneously, the context switching..and having to deliver in 2.5 week deadlines.

Yeah...not practical.

1

u/Luneriazz 6d ago

What is the goal anyway

More feature? Better stability?, backward support? More secure? optimized resources? user friendly? 

Its neither of those, everyone just ship code and pray one of those update works.

The real metrics is more user and higher revenue...

Now how you translate those 2 metrics into software development? Diagram? System requirement?, planning? Thats the neat part you dont. It does not matter anymore, everyone just brute force their way out.

Thats why AI come in, it makes the brute force 10x faster.

1

u/Gnaxe 5d ago

Have you tried Fable 5.2 yet? No? Then you probably don't know what you are talking about. They are getting a lot smarter than whatever you have been using. What's cooking in the lab is generations ahead of even that already. Agents can do more than code. They can help with planning and design.

Yes, it's easy to produce large volumes of low-quality (slop) code, especially with the older, stupider AIs. But whatever engineering discipline you use to keep code quality high, you can also direct the models to do, and they're enabling even higher quality practices like formal verification that were simply too expensive to be feasible before. You become less of a coder and more of a project manager. The project manager is not reviewing all the PRs. With high enough volume, you can't either. Maybe you spot check, or intervene in specific problem areas. Or maybe you throw the whole thing out and start over with what you've learned.

To really get the full power of delegation, as with human teams, you have to not mind the details too much and trust the expertise of your employees. Don't micromanage. It's the same with AI agents. They're not totally trustworthy/competent (humans either), but the smarter ones are more competent (but maybe actually less trustworthy).

2

u/JeanCasteaux 5d ago

So sick of this overusef answer. "But you haven't used this exact brand new model that is completely different !" 

I've been hearing that for 2 years now, and every time it's more close to an increment than a revolution. (And yes, I have actually tried it).

Thing is, only humans are accountable and have a true world model. Trusting agents blindly is dangerous.

1

u/thenextvinnie 4d ago

The fact that hype masters exist out there does not mean genuinely competent AI-tool-centric AI development is a myth.

- signed, a former ai tool skeptic who still loathes ai hype masters

2

u/KevinJRussell 5d ago

Have you tried Fable 5.2 yet? No? Then you probably don't know what you are talking about.

Lmfao, people say this every time a new model comes out, which is like every couple months. I can't imagine how gullible you'd have to be to fall for it.

2

u/DepthMagician 5d ago

But but but Sam Altman said their new model feels fundamentally different. How are you not convinced?

2

u/Mysterious_Net_1029 5d ago

The machine god will be created any day now 🙄

2

u/blindsdog 5d ago

What’s there to fall for? Of course you should judge AI capability by the latest models

1

u/doyouevencompile 5d ago

And it’s true to some extent. If you compare the models from today to the ones from last year, there’s a massive difference. 

They still don’t make all the right choices, but they make better choices than last year and they’re so much more capable. 

1

u/mxsifr 9h ago

Oh my god shut up...

1

u/ImmaturePrune 5d ago

Lines of code *werent* a meaningful metric, because they were bottlenecked by a persons ability to think and type.
Those bottlenecks are gone, so sufficiently high LOC can tell you something now.

3

u/JeanCasteaux 5d ago

Uh, what? Sometimes, the same feature can ve written in 500 or in 50 LOC. The count means nothing in terms of usefulness and end result. I'd even say that the less lines, the better.

1

u/ImmaturePrune 5d ago

Again, that's why they *WERENT* a meaningful metric.
It's not a matter of 500 vs 50 LOC anymore, though. It's 500 vs 500,000.

2

u/mightshade 5d ago

Code is still a liability. This boils down to "we can generate liability orders of magnitude faster now".

I'm super excited. /s

→ More replies (5)

1

u/No-Consequence-1863 5d ago

More code is still worse. Takes more RAM to run a program with more code, takes more time to load and distribute, takes more time to compile, takes more disk space to store.

Less is always better than more if the same functionality is achieved.

→ More replies (5)

2

u/KevinJRussell 5d ago

That's true. AI has gotten sloppy enough that they're now taking thousands of lines to do what a human could in ten. High LOC is definitely a red flag.

1

u/ImmaturePrune 4d ago

Ten thousand lines to do what a human could in ten...
My guy, lay off the copium. It's making you hallucinate more than GPT 3.0 😬

1

u/newyorkerTechie 1h ago

If it does thousands in what you can do in ten, it’s on your for not having reviewed the plan

1

u/No-Consequence-1863 5d ago

LOC was a bad metric not because of some bottleneck, but because the # of lines of code has basically no inherent connection to quality, functionality, or quality of features.

Nothing has changed it’s still a bad metric.

1

u/ImmaturePrune 4d ago

No connection to functionality?
😬

1

u/No-Consequence-1863 3d ago

Yea. You can write the same feature with 10x the lines and it wont do anything different.

You can write 10 features and have them all copy the same code over and over again or factor it out into a utility function. Same functionality, but the former has tons of waste.

→ More replies (1)

1

u/Better-Avocado-8818 5d ago

It’s not better in terms of quality. For quality using AI to plan and then problem solve one small task at a time is better. But that’s like a small speed boost to one engineer.

Embracing the AI slop and pretending your skills and multi agent review pipeline are just as good is worse but much faster. So much faster that many businesses are choosing this over the other higher quality process.

It’s not better all around it’s just that businesses and builder type people are either ignorant of the compromise or actively choosing speed over quality.

1

u/karasko_ 5d ago

No, you're not the only one. As professional developer for more than 25 years I can tell you that I have very hard time believing the how that Ai can replace developers... not 8f you to keep the same quality, anyway. I also use Ai agents everyday, but they help me, they don't replace me.

1

u/StrikeTechnical9429 5d ago

one prompt can trigger changes across many files

If you have to make changes in many files to implement something, it is a sure sign that the code is bad. It's literally a definition of a bad code. It was like this before AI programming, and it stays true now.

1

u/Miserable_Ad7246 5d ago

Core issue is that you apply same patterns to agentic development. Try working on bigger things, so reviews are longer and you have less context switching. Also bake in validation and verification into your plan. Let agent write the e2e tests and mutate them so it can prove that they work.

Agentic coding is rather trickly because it requires you to think like a lead developer. You basically, plan and validate.

1

u/Alternative_Win_6638 5d ago

Hi, speaking of SQA: you should rely on AI the way a mechanical engineer designing a mechanical system relies on a subcontractor to build it.

For a mechanical engineer, quality is determined by the ability to hand off quality requirements and acceptance criteria, review and agree on the delivery plan, and validate the delivery.

So think of yourself as a mechanical engineer, or an engineer in any discipline other than software, with the AI acting as your subcontractor. You can find more details in this video: https://youtu.be/Qd-gsgiXGD4

1

u/Any-Blacksmith-2054 5d ago

My agents are not only developing code, but also communicate to colleagues, do analysis, testing, full sdlc

1

u/BoBoBearDev 5d ago edited 5d ago

I believe what you are describing, is echo chamber. Because if you write everything yourself, you are just giving yourself a medal. If you ask AI to critique your interfaces, AI probably will find problems. Not all the problem are legitimate, but I am certain it will find many legitimate problems.

I suspected a lot of dev just run AI once to make a change, but never ask AI to critique it. They just assune the AI did it perfectly immediately, but that's not the case in my experience. The AI can find problem on code that it generated.

1

u/dizekat 5d ago edited 5d ago

It’s the plagiarism. Consider a simple hypothetical. Making Tetris in a world where it was never invented. 

You would have to describe it in enough detail in English to get the bot to produce the right code.

The bot is non deterministic. It is even less repeatable than mere non determinism because what worked most of the time one week would not work on another week - it gets changed behind the scenes. A lot.

The bot knows connect four, it tries to do that on slightest ambiguity.

It would be a very frustrating experience. You wouldn’t even be able to learn how to describe things exactly enough on existing things because AI does not require exact description if the thing exists.

Of course, what every AI using programmer reports is nothing like that. Because for the most parr they don’t have new ideas to implement, so they never have to describe anything in great detail.

There are some situations that avoid having to describe things, of course - code constrained by other code, or maybe by common sense of not triggering universally incorrect behaviors - where LLMs are reasonably effective. But outside those situations they are a lot less helpful.

1

u/zouxin6112 5d ago

我觉得ai其实是很有用的,现在代理越来越流行,是大趋势,但是我觉得更多应该当成工具,一旦习惯了代理,反而会变得懒惰,虽然或许你可以有更多的时间去完成别的事,但是写程序这件事本来就是一个乐趣不是么

1

u/MailLabRat 5d ago

I think the biggest difference is between generating code and actually understanding what you're building. Agents can be great for repetitive tasks, boilerplate, or writing tests, but they're not making the architectural decisions for you. And reviewing a huge AI-generated diff can easily take longer than writing the code yourself.

I wouldn't measure productivity by how much code an agent produces. I'd measure it by how much working, maintainable code actually makes it into production.

1

u/sichidze 5d ago

I guess people find agentic coding very efficient when they use it on web applications, where the job is mainly to layout UI and connect it to CRUD operations. Most projects are not state of the art, developers indeed do repetitive work, following the same patterns. That's exactly where LLMs succeed. I view AI tools as a very advanced scaffolding. And I find the code LLMs generate of poor quality or requiring more time to direct AI where I need than to write code manually where my task is less typical.

1

u/MyNimples 5d ago

“Obviously have to review all of that”. lol no.

1

u/pvera 5d ago

Agentic is a blanket term, it doesn't necessarily mean that everyone uses as a swarm of bots doing your work while you browse reddit.

Real world example: I have been using a PR skill that spins out multiple agents to spread out the load for a large PR. Then it takes the findings and hands them to a Fable agent to try to disprove them. It works great and the additional token burn is reasonable when you weigh it against the higher error detection.

Another real world example: I have a peer elsewhere that basically aims Claude at a ticket and tells it how many agents can work it at a time, test conditions, even automatic PRs, etc. It doesn't work for any kind of work, but for his particular work load it's definitely a way to keep a high workload while allowing him some room to breathe to do work that isn't as easy to automate.

1

u/heavy-minium 5d ago edited 5d ago

Well, yes, you must be missing something about it.

We can't tell what it is from this post. But a few guesses could be made - like for example, at which level of abstraction you instruct the agent, whether you are good at putting your requirements into words, what models and harnesses you are using, whether you just use it as it is or try to establish a more elaborate setup, etc...

And last but not least, there are definitely roles, processes and goals that conflict with agentic coding. If you have little freedom in what you do in a job, the agent can't do much either - for example only working on a very specific part of a small project/plattform, only coding, not doing requirements engineering, not doing support, not testing, not documenting, not touching CI/CD, not touching infra, etc.

It doesn't work well either for people who learn as they go - language, SDKs, libraries, APIs, tools, etc... Because then you need to learn how things work as you review the agent's code, and you ain't able to set proper expectations either because you don't know about them beforehand.

There are so many factors that come into play, shaping the experience and increasing or decreasing productivity.

1

u/RetroGrid_io 5d ago

It's the wild west, man. Ain't nobody really knows what they're doing because this has never happened before and the situation is evolving quickly.

As of last Spring, AI generated code was awful and cursory audits showed terrible flaws. AI has become better, and so have people.

Just in the last 30 days, my relationship with AI has flipped: a month ago, I did nearly all the writing and used AI to challenge and find bugs in my work, and now the roles have reversed: AI is doing nearly all the coding and I challenge and find bugs in the work, in my project to build the world's largest database of Operating System History.

suddenly people are bragging about how many features they shipped or how much code their agent generated.

Yep. I don't understand anyone who'd really let AI "take the wheel". I find terrible architectural bugs today, although I've either learned how to prompt, or my Claude Code agent has learned how to do a vastly better job now than a month or two ago.

I personally review every single change, and I am strict about rejecting anything that I wouldn't accept from another human.

You don't have to accept:

  • Huge refactors that effectively make simple changes

  • Code Slop

  • Poor architecture

  • Badly documented

  • Un-normalized database

  • Not following coding layout guidelines

... in short, anything you wouldn't accept from another human. It's entirely doable to have the speed of AI and maintain high code quality.

1

u/seizethemeansnchill 5d ago

I think your instincts are right.

Agentic coding is optimized to displace human labor not enhance human capability. Which is a shame because there’s a lot of potential to enhance and create better software.

There are gestures towards and hooks into helping a SWE do better more interesting work but the seduction to surrender and the demoralizing effects of the shock and awe of code output.

1

u/Frequent-Owl-5748 5d ago

I still can’t really use agents at work, so I don’t really have experience with them. However, I do have already have a problem with context switching, and need to focus on one or two tasks at a time. So I can’t understand why you would have an army of agents to do the work of a team.

That being said, I do believe they could be useful for a couple of mundane tasks I don’t like doing myself, but you have to be very specific and make sure to plan the changes you let the agents write. (At least that seems to be the common practice)

1

u/JohnSane 5d ago

It works, but I honestly don’t really see the benefits when it comes to software quality.

Probably because quantity is the target atm.

1

u/shan23 5d ago

I really, REALLY doubt you are faster at doing anything remotely related to coding than someone who ACTUALLY knows how to use Claude OPTIMALLY (important distinction here)

First find a way to verify that - you need to be convinced thoroughly about it.

Then we can talk about next steps (few get here lol)

1

u/Zendental 5d ago

Once you stop looking at every line of code you’ll see the benefit. You’re still attached to the code

1

u/aznattackr1337 5d ago

read the blog posts from anthropic and openai. watch the youtube videos on ai engineering channel, esp the ones about software factory. you'll get it. nowadays people engineer the factory and define the requirements and whatnot and the agents do the rest, no looking at code or any of that

1

u/KamikazeArchon 4d ago

Lines of code are not a meaningful metric - but features certainly are.

1

u/sleep_deficit 4d ago

tl;dr: coding is not engineering, and you're an engineer.

Coders seem perfectly accepting of the cadence, volume, and quality of LLM output.

Engineers see the usefulness but recognize the massive debt and risks being introduced.

1

u/chessto 4d ago

If you care about the code, not just about its quality but understanding what it does and why then AI doesn't really speed you up, it may allow you to rubber-duck or validate some concepts, but the uncertainty on its output (hallucination) makes you have to double check almost everything it produces so there's no gains there.

If you don't give a fuck about what's going on under the hood, then you'll move really fast.

1

u/Necessary_Weight 4d ago

Couple of things here from a perspective of working in a large enterprise where software is not the product we sell but an enabling function to how we sell our products. We have 6k+ tech function, spread across four countries. About 2k engineers are now more or less agentic AI users, and we are slowly transitioning the rest:
- average overall quality improves. Cross service integrations have become better and more manageable;
- average security quality has improved. Our app security teams burn the most tokens;
- average incident response time and effectiveness have improved substantially on key services.

Volume of code is also through the roof, but that is not surprising.

In a business like ours, these averages improvement lift up the whole business. Yes there are issues and new problems, which are familiar to anyone who has managed 3+ agentic teams working on different contexts - cognitive burnout is real and draining. But, for a large function like ours it is a win for the business.

1

u/dismantlr3256 4d ago

If it’s not better than you now, it will be in short while. with agents, one can be many.

1

u/Money-University4481 3d ago

I work in a small shop with just a few developers. I have 25 years professional experience. Have been coding for 35 years. Software development has become so much harder over the years. More tooling, higher demands on testing, security, apis, compliance and compatibility. Don’t let me started on ui, the difference there. On top of that you have so many libraries now that update in different times, tools that update, languages change and update. My role is the same but now i have to manage so much more.
With ai tools i am back to being productive and on top of all of this that a small shop would never manage to do. I can adress the security with a review, document the apis, manage the tooling around and be on top of the latest development.

1

u/son-of-chadwardenn 3d ago

The tradeoff for a significant speed boost with agentic coding is some loss of complete understanding of the final product. So the question becomes what are the risks introduced by that lack of understanding? This depends on what the intended use case and environment of your app is. I suspect the software industry will develop new design patterns to mitigate the risks of ai code by isolating and sandboxing code modules.

1

u/americandilemma 3d ago

Agentic coding lets you work on multiple things at once. Even if you could code at the same speed as the agent, you would only be working on one task.

1

u/PitifulAppearance509 3d ago edited 3d ago

Before, you had limited time, limited staff, limited budget, limited knowledge in implementing certain things. So people made shortcuts. Which meant fewer automated tests, more technical debts, features were simplified. No time for test automisation and let's not talk about proper documentation.

Now coding/building is so fast, a feature is done just in a couple of minutes. You have time to do the unit test, automated e2e test, mutation tests and maybe more since all this is also Vibecoded in a few minutes as well. Even the LLM Reviewer reviews code better than most humans. So I totally believe a ping pong between a builder agent and a reviewer agent will create a better result than the average SWE.

In all honestly, Just a couple of weeks ago, I had to do a fairly complicated multi drag and drop component. I honestly would have never been able to implemented it better than the AI even given a week or two. And it would have been a freaking drag to implement myself.

1

u/moseeds 3d ago

when you say you can write code as fast as the agent once you figured it all out... are you including test harnesses, enabling tools, edge case detection, end-to-end integration tests, rollout plans, ad-hoc spec changes, etc?! and the model you use has an enormous impact on the quality of the output. a year ago I may have agreed with you. not today and definitely not this time next year.

1

u/gplgang 3d ago

Same experience for me

1

u/jimh12345 3d ago

Well now you're trying to bring common sense into the discussion.  Didn't you drink the KoolAid like everyone else?

1

u/beachandbyte 2d ago

I’m sure many people think like that. But it’s like someone who knows basic algebra saying you know I just don’t see why calculus is that useful. I can add and subtract numbers just fine on my own.

1

u/Anxious-Insurance-91 2d ago

Programing before AI and after AI has always been iterative, meaning you ship you test how it looks in prod, and then you pivot as the business changes, or fix bugs or add new features faster. Now it depends on what area you are working on, the web beeing the simplest one. As for the lines of code, you need to look at it like this, you get done in an hour what used to take, depending on the task and techstack 1-3 days.

One thing you also need to understand is that between COVID and the AI era there have been a lot of REDUNDANT people hired or reprofiled, basically anybody that could send ma email, a lot of untalented people, not average, just untalented, bearly knew how to code etc and most of the time they were drinking lattes. Also a lot of people were OVERESTIMATING, how much it would take them to do certain things like a margin of 10x.

There are many things that mix and match in regards to AI usage

1

u/ABCosmos 2d ago

Lines of code isn't a good metric, but features shipped absolutely is. For all things being equal if you can ship features faster that's better. Now if they are lower quality or break things that's obviously a problem and worse than benefit of being fast. But shipping features is not meaningless like lines of code is.

1

u/Potatus_Maximus 1d ago

You are doing it right. People who simply take AI-vomited code have no idea how to check any part of the code and it won’t end well.

1

u/orbital_trace 1d ago

I treat coding now as setting up an experiment following the scientific method. It's so easy to generate code, but if you work with the agents to set up an experiment, you don't have to look at the code, but you can verify it is correct.

The velocity is undeniable, it's easy to hit 3k prs a week on your own with a team of agents, and have them all be meaningful. I've been writing about what I'm seeing here

if you are curious about what a full on agentic all looks like and can do. Check it out

1

u/RangePsychological41 1d ago

You haven’t worked on a very large software system. A hundred repos. Many teams. Multiple Kubernetes clusters. Dozens of massive Aurora DB clusters. RBAC for every queue, bucket, Kafka topic. Terraform everything. WAFs and Cilium and security teams hacking your code apart for their weekly report. Teleport integration for everything. Sophisticated monitors and observability. Being on call. Ugh let me stop.

Point is you don’t get it because you don’t have experience so you have no idea how it is used on serious software platforms.

Accurate?

1

u/unski_ukuli 1d ago

You know I hate to do this (I don’t actually) but you post in nofap and some strange anti cat subreddit. You are not a serious person.

1

u/RangePsychological41 1d ago

I’m a nature conservationist and founder of an NPO. Cats are an ecological disaster and cat people are batshit insane when confronted with that fact. No amount of extinctions will sober them up. I live in a forest and a few other off-grid people here think their cats are cute and harmless and belong here. I see how the cats disrupt the birds/reptiles/mammals. I have no other outlet whatsoever.

I’m also actually a very long time vegan but joke about how tasty sweet and sour cat is. Maybe you should let a man have some innocent fun before accusing them of not being serious.

1

u/neutrino_boy 16h ago

You are just behind. Probably lack the creativity and resourcefulness that others have developed over months of using it more intensively to make the time savings. Someone, somewhere else was saying the same thing 12 months ago and have now realised its a dead end.

1

u/Few-Information8369 16h ago

just let the AI do all your work for you and do no thinking, don't look at the code and you will be faster.

1

u/therealslimshady1234 11h ago

Youre not missing anything. AI is garbage at programming, its inherent to the LLM technology

It might get the job done but in the long term is just makes everything worse. Be very careful of people who claim the opposite, these are either clown engineers (AKA script kiddies) or worse, non-engineers, who wouldnt be able to do fizzbuzz without Claude if their lives depended on it

1

u/_________FU_________ 11h ago

A lot of people who complain about AI output are usually just bad at it. However the AI companies are training on you and will ultimately make the hard parts easier. What is important is context management and defining your infrastructure so the tools know where everything is located. Then each time a new model drops you should have it audit your context docs and specs to ensure everything is up to date and clean. This is where most people fail. They assume it's easy and when it buckles they assume it sucks.

AI isn't going anywhere and I strongly suggest learning how to use it. The business ops side are submitting code, agents are reviewing code, it's a Wild West. I spend most of my time tuning context docs and specs to ensure we fix gaps. Someone submitted code that has an awful sql query then I need to patch what allowed that by adding new "do this, don't do that" type rules

1

u/snozzd 5h ago

You're not missing anything, I've had the exact same experience. I've been arguing with AI fanatics about this for months.

1

u/Stetto 4h ago edited 4h ago

I feel like I wouldn’t be faster using agents. Most of the time, I spend thinking about how to design the solution rather than actually implementing it.

That's because you're still just using agents as pair programmer, instead of actually coding agentically. You're just skipping the writing part and remote-control your colleague as if it were in a Zoom-call with screens-sharing.

When you're doing Agentic Coding, you build a workflow that allows you to stop specifying and reviewing every single detail about the code base.

You build (or adapt) an agent harness and CI/CD pipeline where you trust agents to implement the majority of changes with some guidance and initial input.

And then you're very picky about what you actually review and have an increasing amount of parallel agent or multi-hour agents running.

I would argue that you end up spending a similar amount of time tweaking, fixing, and re-prompting an agent to get to the same level of thoroughness and context-awareness you would have had by doing it manually.

If you re-prompt the agent, then you're spot on. You're probably even slower.

But in Agentic Coding you don't prompt the agent do it properly.

You extend your harness with a rule or guidance, that ensures future agents implement it properly, so you don't have to check this yourself anymore

Sooner or later the trust in your harness increases, that you review less and less.

You're now the software architect for a team of agents. Architects also don't review every single line of code.

Am I the only one who feels this way, or does anyone else think about it like this?

You're not alone. You're just at the beginning of your agentic coding journey as an opinionated, experience software engineer.

You now need to tackle your orchestration workflow as the engineering challenge, instead of individual features and solutions.

And pretty much any software quality metric that you cannot make measurable becomes almost obsolete.

and I know every step in the process and exactly what it’s doing (also in regards to safety critical systems)

This is the crucial problem, that you'll struggle with next. The more you automate, the more difficult it becomes to still understand what the system does and form a correct mental model.

But for now your challenge is building a harness that you trust.

1

u/kincaidDev 6d ago

Code quality matters but it doesn't matter as much as people used to think. What matters is the impact of the software.

There's not an easy way to talk about impact so we use LOC, prs and features shipped until we have a standardized way to measure impact.

Once you get good at agentic development, it's physically impossible to type at the same speed as agents can do useful work for you

5

u/Great-Use-3149 6d ago edited 6d ago

Why would you need to type faster? Since when was code really the bottleneck?

My typing is limited by my thinking and decisions. The raw typing speed I have is actually faster than frontier LLMs. The only reason I'm not realistically faster is due to former. What will happen is you'll end up not knowing how things fit together if you delegate everything to the machine (and yes, you're also using it for making decisions and design, otherwise you wouldn't be much faster)

3

u/Cybyss 6d ago edited 6d ago

What will happen is you'll end up not knowing how things fot together if you delegate everything to the machine

Theoretically you're supposed to review the code the LLM generates so you understand what it's doing. But that's not going to happen in practice.

I find that LLMs tend to ridiculously over-engineer things, writing huge amounts of boilerplate code to account for wild edge cases when I'm pretty sure none of those edge cases will ever apply. Or they write lots of weird redundant utility/helper methods. At least, that's been my experience working with Codex.

If you write code yourself, you understand every line of it. Every line has a clear reason to exist since it was written with intent.

When reading someone else's code or LLM-generated code, you're simply never going to understand it at that depth. Maybe you'll have a vague high level idea of what it does, you see it passes your (likely also LLM-generated) tests, then you approve those changes because there's nothing obviously bad that stands out to you.

A few rounds of this, and you'll have a giant convoluted fragile system that nobody can understand or maintain.

1

u/amasterblaster 5d ago

I mean ... I think this just means learning about context engineering in 2026 really ...

1

u/mightshade 5d ago

 If you write code yourself, you understand every line of it. (...) When reading someone else's code or LLM-generated code, you're simply never going to understand it at that depth.

True, and I'd like to add a point that's often overlooked: Without LLMs, even if you didn't understand the code in depth, at least someone did (most of the time at least). That's no longer true with LLM-generated code.

1

u/kincaidDev 6d ago

Why does it matter if you know every tiny detail of how something was built? That’s not something people did pre-ai, what matters is being able to quickly understand the system when it matters.

If you’re only working on things you fully understand you’re going to be limiting yourself to low impact problems

1

u/Great-Use-3149 6d ago

Not every tiny detail. The problem with using LLMs to be much faster, you end up having only vague idea or very shorter-term memory. This then also leads to worse decisions on human side. 

Im any case, LLMs won't be able to get certified like compilers and too many people using LLMs will leave very few who can do critical regulated works

→ More replies (1)

1

u/kultcher 6d ago

Typing speed aside, are you saying that you always construct every function perfectly, write every line correctly the first time, remember every bit of syntax and language quirk, etc.?

1

u/Great-Use-3149 6d ago

After a few years of experience with a language and constant practice, yes, I never look up syntax or quirks.

I may not write everything *correctly* the first time, but I usually get it the second time afterwards, and that teaches me on what not to do, which inherently leads me to think better in the future. I i had anything fairly new and complex to do, I usually thought about it first and even went on paper (talking about some math related things here) . In any case, if I wanted to improve it afterwards, it was very easy, because I knew how everything was.

Actual tools were never much of a problem (most of the time), but the thinking and design part was.

1

u/amasterblaster 5d ago

"Why would you need to type faster? Since when was code really the bottleneck?" The dawn of coding? lol what?

Dont get me wrong, I dont mean MORE. I mean finished code that works. Thats HARD, and agents make that fast and easier? (for me at least!)

The one single aspect i LOVE about agents, is they generate a whole solution right away, I can see the whole thing (at a file level) prompt one idea, and the WHOLE FILE updates in real time with my rerfactor note. This is like moving at the speed of my voice -- its insanely productive.

In addition smaller ideas I can just delegate straight to the PR stage and just comment on the commits and see them update in real time.

So yeah this is like ... so so so so so productive for me personally.

1

u/Nervous_Designer_894 6d ago

You're describing AI coding workflows from two or three years ago. Modern agentic development is considerably more sophisticated.

The key is context engineering, upfront architectural planning, clearly defined requirements and proper task decomposition. Once you've established those, there's no reason to have a single agent implement everything sequentially.

You can orchestrate multiple agents working in parallel, much like a software engineering team, with separate Git worktrees, branches, PRs and well-defined responsibilities. Integration tests and reviews keep everything aligned.

I'm currently building a fairly complex product with numerous interconnected components using this approach. What would traditionally have taken considerably longer has taken me roughly five days to get working.

The real skill is increasingly shifting from writing every line of code to designing the architecture, orchestrating agents and validating what they produce.

2

u/Great-Use-3149 6d ago

The real skill is increasingly shifting from writing every line of code to designing the architecture, orchestrating agents and validating what they produce.

And you somehow weren't doing that before agents? Typing code is very fast if you know what exactly to writer unless you're a fairly slow typist.

1

u/DubiousLogik 6d ago

my experience matches what nervous_designer_894 said. yes i was doing that before but the cognitive load of tying off all those interfaces and dependency injection etc is not just typing. I had agents write 5k lines of code in 3 days that worked. took me a bit longer to get the test coverage, but that is not just a 'typing' thing. it scales differently

1

u/Nervous_Designer_894 5d ago

Yes but before that, that wasn't always my main focus, as we had other team memmbers (DevOps and Cloud Infra) doing that.

1

u/rafark 5d ago

you can orchestrate multiple agents working in parallel 

Yeah you’re not reading any of their code. How do you know it works and it’s not buggy? You don’t because the AIs also write the tests and you’re not reading those either.

And let’s not act like the AIs aren’t designing the architecture either. 

1

u/Nervous_Designer_894 5d ago

So AI reduces tonnes of work and complexity (of writing code and debugging upfront, but then adds a load of work in testing and ensuring the product is working as intented,

1

u/HiderDK 5d ago

Even the architecture you can partially outsource ai. What humans need is to specify the criteriaand agents developing the architecture that meets those criteria is part of that.

1

u/AciusPrime 6d ago

I agree that “how much code the agent generated” is a terrible metric (especially because it feels good), but isn’t “features shipped” a pretty good definition of success?

I mean, I do sympathize. I’ve spent the last two days fighting with an agent and it’s like arguing with a stubborn autistic puppy. We’ve been playing with OpenSpec, and I am seeing some signs that this helps the long-term memory problem, but I haven’t proven that out yet.

So far the big wins have come from the kind of stuff you’re talking about. It’s pretty good at tools and automations. It’s also really good at finding vaguely described things (“can you tell me what kinds of things this class is used for”). Sometimes it’s good at debugging but it seems to depend a lot on the bug.

1

u/Great-Use-3149 6d ago

Features aren't a good metric themselves either as they can end up being very fragmented for something that should be the same thing. If you just ship fast, you have no time to reason and no time to build a memory map of the implementation.

"slow and steady wins the race" — continuous consistent progress gets ahead of "ship fast, break things" .

I mean cmon, when was typing boilerplate in code the thing the thing that took the most. Most of the times were due to thinking and reasoning and deciding how to implement things, and then after that much longer times to review. 

1

u/AciusPrime 4d ago

I live in a world where “feature” = “specifically requested project based on customer interviews and tracked by a project manager.” Shipping it means “QA approved it, the beta testers tried it, and it has been merged to trunk in the stable product.”

I work for a big company.

Your definition seems to equate “feature” with some kind of closed loop where the developer gets to decide what feature to make, make the feature, then decide whether it’s been shipped. That’s pretty accurate in a badly run startup, but when I say “feature” I mean the other thing.

1

u/someRedditUser3012 6d ago

True, but I'd argue any time you set ANY metric you're going to have ways to manipulate them. Even eons ago when I worked fast food, we'd have cars pull ahead to stop timers to make service times look better. I often joke that the easiest way to turn a red project green is to just change the due date. Bam. Now you're ahead of schedule.

I agree completed features and maybe add in complexity somehow would be on the better side of what to track. You meed some way to measure value and velocity to deliver said value.

What metrics would you track instead (honest question)?

1

u/Great-Use-3149 6d ago

In terms of productivity perhaps number of fully completed projects, divided by the number of fixes needed after project "completion". Although that can be be manipulated as well by simply dropping quality.

If a tool is forced in a company, the only reason a company should have is profit. If the tool is forced by technical people, then it should be for quality and growth of employee skills and happiness . I'm not sure if any of these last metrics increased.

1

u/gajop 5d ago

Some 12 months ago, this statement had some merit, and depending on the tool you were using, agentic truly wasn't worth it in some cases.

Today? I really doubt there are many use cases where you don't really benefit from it. The technology has advanced significantly, to the point you don't need to read the code often. My guess is you just aren't familiar with them enough. It doesn't take a lot of skill to use them, but it takes some. I'm going to guess you're approving every action or nitpicking every line, and thus killing any productivity gain you might get from it.

1

u/abednego-gomes 4d ago

I don't think it takes a good holistic overall view of the application you're building. It's better in bite sized chunks. And if it does do big system wide changes, you'll be using so much context and AI credits your wallet will be on fire.

And at the end of the day, no-one will know how the application works at the code level anymore. They'll hook your company's developers like heroin and then rug pull you in a few years when they hike the prices.

1

u/gajop 4d ago

Cost is high but you're multiple times more productive, it easily pays off, although higher ups need to understand that.

I'll also admit that code understanding will be weak, even if you read it all (and now you're the bottleneck), it just won't sink in, seeing how much code you're reading. You need to let go a bit.. kinda how your manager does. Not all lines matter.

I don't think cost will go up much higher. At my company we're already paying API prices and those have only been going down - quite drastically when you look at things like Luna. The other thing that will keep it down is the ability to run local models. "They" can't take this away from you.

0

u/rmanisbored 6h ago

For fucks sake please find another arguments against AI and we listen but saying "AI is bad at coding" at 2026 either means you're not smart enough to leverage it or you're not using the right models or you're just simply coping.

1

u/Perfect-Mortgage3698 5h ago

Did you read the post?

0

u/niccolololo 6d ago

Code quality--we found out--doesn't really matter. Quality in general is going downhill nowadays, whether it's code or a washing machine

0

u/Leading-Deer-7084 5d ago

Where agents clicked for me was the boring stuff, migrations, test scaffolding, renaming something across 40 files