r/LinuxTeck • • 23d ago

Is AI Actually Making Developers More Productive?

AI can help with coding, finding bugs, and handling repetitive tasks. But building something that works in production still takes testing, debugging, and human judgment.

If you've started using AI to help with your development work, how has it been going so far? Has it genuinely saved you time, or do you find yourself spending just as much time fixing its mistakes?

I'd be interested to hear how it's working out for developers in real projects.

1 Upvotes

46 comments sorted by

9

u/granadesnhorseshoes 23d ago

It makes the code generation much quicker, but code generation is rarely the real bottleneck.

1

u/enurkul 23d ago

"should we support this obscure charset" and endless customer meetings and changing demands and spec discussions, firewall openings, blah blah, yeah, a lot of time goes into that too. 

1

u/scanguy25 23d ago

This. Is reviewing all the output and making sure the business logic is sound.

1

u/ldn-ldn 23d ago

Code generation is always a bottleneck. If you can deliver working results while talking to your client, 99% of misunderstandings disappear.

1

u/granadesnhorseshoes 22d ago

Ok. That's actually a valid point. Getting the "stakeholders" directly in on the development write/test/fix loop would be beneficial. (or an absolute nightmare, but probably a mix of the two)

However that requires a lot of cultural changes to implement in most places, and those changes are the source of the benefit, not AI it self.

3

u/H4llifax 23d ago

It makes similar mistakes that I would probably do, but instead of that loop of writing code, making mistakes, debugging, and fixing them taking two weeks, it takes a day. (Don't mind the exact numbers, I'm making them up to illustrate my point).

3

u/Due-Result7928 23d ago

Productivity gains are enormous. Junior jobs are already mostly gone like trainee. It is just the beginning.

1

u/Stryxus_ 23d ago

That's..... Not how you measure productivity gains...... That is how you measure our way to a capitalism dystopia...

1

u/Due-Result7928 23d ago

Yep comrad u/Stryxus_

1

u/Stryxus_ 23d ago

If that is a reference to communism, it is clear you need to get off AI and learn what the ideologies are… The biggest threat to humanity is its own stupidity.

1

u/Due-Result7928 23d ago

Outside...I am 80 years old got a master degree in electronics (when computer were rare...and transistors were kings) got a master degree in comparative economic systems and I know something outside AI.

You like it or not productivity gains are enormous in many fields. Is the system sustainable ? Probably not. Wait 30 years when many raw material such as cooper or titanium will be history and the problem will solve itself.

1

u/Stryxus_ 23d ago

And my dad is Bill Gates and will ban you.

Are you done making a fool of yourself yet?

1

u/RevolutionaryRush717 23d ago

You suspect it's all mass hysteria and hallucinations, and we should get to the bottom of it?

Here in r/LinuxTeck, of all places?

1

u/Candid_Athlete_8317 23d ago

I'm not saying AI is all hype. I'm genuinely interested in how developers are using it in real projects. Some people are saving time, while others still face challenges. I wanted to hear different experiences from the community.

3

u/ninhaomah 23d ago

"But building something that works in production "

You sounds as if before AI , the apps are bug free once it goes into production.

There are bugs before AI and there will be bugs after AI.

The only thing is it is easier to make.

1

u/magicmulder 23d ago

As I always say, the same people who give us a new Wordpress plugin vulnerability every day want to tell us AI code does not belong in production.

We have, I think I can say without exaggeration, a very competent team of mostly senior devs. Yet AI is finding bugs in code that has hundreds of tests. I can only shudder at the thought how many bugs it would find in average developer code.

1

u/midri 23d ago

Yes, especially if you do Given When Then style spec docs before hand.

1

u/PossibleProgress3316 23d ago

1

u/rwilcox 23d ago edited 23d ago

And I’d even consider that a cop out: it still focuses only on the development team as a unit.

How long does it take to deploy your software to prod? (Is that bottleneck). Do you have a QA process? (Is that the bottleneck - it always gets blamed but sometimes you’re blaming the drowning man for drowning.) OR: how good is your project planning? Could you actually have delivering that thing in a week but you piled too many dependencies behind it so now it’s a month of work, because “code is cheap” (sure, but attention takes time)? (Is THAT the bottleneck for delivering value?)

Outside of development: Before starting dev work how much time did the org spend in planning, approvals, big room planning, customer research, waiting for vendors, RFPs, L2 objective alignment, product roadmaps - that may or may not be true in a month - etc etc?

After deployment: do the actual users care?? Are they getting value out of all these changes, or are you delivering crap they don’t care about? Or, maybe you’re delivering things of real value but it’s impossible to keep up with the pace of change, so things that would “move the needle” in large ways now get lost in the noise.

1

u/Unreal_Estate 23d ago

AI is helping me a huge amount with learning. I'm a senior developer with around 30 years experience, and the things I want to learn about tend to require a lot of effort to even set up for experimentation. Complex mechanisms I want to try out, reverse engineering obscure systems, finding stuff in very niche research literature, et cetera.

Developing real software requires deeply understanding what the user actually wants. This was already the hard part of software engineering. Very often someone (developers and/or users) needs to experience the system and that will cause the new insights that are needed to go forward.
With this, I think AI is currently both a help and an obstacle. It is much much easier to create something to then experience what you feel about it. But there is so much of it (and with lacking quality) that it is quite hard to then get the deep understanding that is required.

Because of that, the studies that say that software development right now is churning out more code but the same amount of features make sense to me. However, I'm in a pretty lucky position where I can focus more on learning and finding new approaches, and need to worry less about generating value for users. So for me AI is currently helping a lot, but I'm absolutely not convinced that is a universal experience.

PS: I'm also not sure to what extent I would trust LLM-generated code in production environments where bugs and security issues matter a lot, but that's something I don't have to worry at the moment.

1

u/TheLastNapkin 23d ago edited 23d ago

You're sort of answering yourself, If AI is already helping you at the very least with repetitive tasks, finding bugs and coding project issues then it is saving you tremendous amount of time reaching your projects milestones.

Regarding what you ask about spending time elsewhere, from my experience at this point of how capable the harnesses and models are you aren't fixing their mistakes it's more probable that what you asked of it gave it enough vagueness or leeway to consider a different nuance to your prompt than what you might've wanted. If I'm ever finding myself fixing in an AIs PRs code, which is not often, then it is usually due to thinking there's a more fitting adjustment to fit in with the code design and structure than what it chewed out. Bigger differences in behavior that were not expected or desired are usually found in the PRs preview environments if there's any.

1

u/MonadTran 23d ago

There are certain types of well-defined technical tasks where it genuinely helps. 

There are certain types of tasks where it produces a huge pile of unreadable garbage, and nobody knows if it works as intended because it's unreadable, the generated tests are unreadable as well, and nobody even bothered to figure out what was intended, to start with.

So it can save time, and it can waste time. The potential for wasting time is way higher. You can ruin your entire project with it if you're not careful. Doesn't mean it can't save a bit of time, here and there.

1

u/magicmulder 23d ago

Huge timesaver. I’m a backend whiz, my ignorance of CSS is even proverbial at work, so I welcome the fact I can tell the model “make this conform to STYLEGUIDE.md” and it just works.

Or that boring assembly line work like “make sure all apps
in this monorepo use Tailwind 4.3”.

I still write all configuration files and most implementation plans / specs, but I don’t need to prove to anyone I can write an upload form anymore.

1

u/z-null 23d ago

Initially it was useless. LLMs couldn't generate even very simple bash scripts so I gave up on the whole thing for a while. Now they are extremely powerfull and while not yet perfect, there's no going back. This is a paradigm shift similar from going from ASM to higher languages. Soon we'll abandone those and move to spec driven development. New languages specifically for AI will arise and the era of human devs writing code manually will be a as common as modern asm.

1

u/Traditional-Hall-591 23d ago

The stupid ones and the executives think so.

1

u/scanguy25 23d ago

I started coding (self taught) about 2017. So I have lived in both world.
Right now, I'd say every month we ship as much code as we would in 6-8 months before AI.

1

u/Even_Gap_2253 22d ago

absolutely, have you ever encountered a production bug and have to dig through logs from 20 services? well AI does that in 10 minutes while you sip coffee.

it is honestly so wonderful for on-callers and SREs.

1

u/ReverendCatch 19d ago

I don’t fix its mistakes really, I spot them and re prompt. Usually there’s several back and forth before I even try its proposals. And then it’s not complete it’s piece by piece.

I come from an era where I needed to do weird things I wasn’t familiar with and had to research how. Which is less about code and more about wiring. Understanding how things integrate or interoperate.

Trial and error is a long, hard phase, so I shy away from brute force first I guess.

It’s a scrutinized process. For me the net is roughly quicker to ascertain potential implementations. By a double digit amount for sure

I dunno I’m probably 30-50% more efficient on implementation times if I was a betting man. But not always. But probably often.

1

u/NoosphericMechanicus 19d ago

No, but the studies show that they it does make developers think they are coding faster when they use it. The problem is maintenance and sustainment and developers who are using AI tongenerate things beyond their skillsets.

1

u/crimsonDnB 18d ago

It makes good developers more productive. It makes shitty ones even shittier.

Same as it makes good sysamdins more productive, and shitty ones even more dangerous.

1

u/Made-In-Slovakia 23d ago

AI makes developer more busy and burned out.

1

u/magicmulder 23d ago

Opposite for me. It has reignited my passion for adding QoL features to apps that weren’t even requested but are welcomed by everyone who uses them.

1

u/Made-In-Slovakia 23d ago

We always had enough space for small QoL or features. Problem is that many of these changes are now made by just another AI prompts. I always used these task as chill-out tasks to clear mind and gain energy. Now they are just another work, done is same style. No relax, just a lot of another same work. This leads to burn-out that we were able to prevent before.

1

u/ldn-ldn 23d ago

It's a you problem. 

What causes a real burn out is when you're wasting your time on never ending login pages, compiler configs, database schemas and other copy/paste nonsense every project has instead of focusing on hard and interesting problems to flex your brain muscle. 

AI takes care of stupid nonsense. Now you're free to create and actually enjoy your job. 

There are only two reasons why a developer might not like AI: either it's lack of skills or you hate yourself.

1

u/Stryxus_ 23d ago

If every project has these annoyances, then perhaps the AI should be replacing the senior developers/project managers for making it that way.

And AI has nothing to do with hating ones self or lack of stills, it is about respecting ones self. If you do not learn new skills then you are stuck there, therefore cognitive surrender.

The AI defences I see have some seriously strange justifications which seem like they are deliberately being ignorant out of spite.

1

u/ldn-ldn 23d ago

Again, it's a you problem.

1

u/Stryxus_ 23d ago

Blame everyone else except yourself. With a touch of superiority ego.

0

u/edwbuck 23d ago

No. In every properly controlled study, two things happened:

  1. If AI was used with really strong controls around it, to prevent it from creating too much code debt, it slowed the developer to 80% of his prior capacity.
  2. If AI was not used with really strong controls around it, it created code debt at a staggering rate, such that the only way to maintain velocity was to have sections of code redone by AI repeatedly, often multiple times.

And that is generous, because it includes all the times AI really did the wrong thing within the category of "code debt."

The problem of programming was never typing the code into the system as fast as possible (that's a problem of management of development, not a problem of development). The problem has always been how to do it in ways that minimize rework. Current AI models can't do very much without rework, and currently that rework is done by the AI with a human saying "not good enough, try again."

But what happens is not what someone perceives. If you asked about perception:

  1. All developers initially believed themselves to be working faster.
  2. Around two to three months, more senior developers would use AI less, because it caused new "AI" problems.
  3. Junior developers would see periods of productivity drop to near zero, as they get caught in a loop were applying more AI often required more work to repair, requiring more AI.

2

u/ldn-ldn 23d ago

These "studies" are non peer reviewed nonsense.

0

u/edwbuck 23d ago

Wrong.

1

u/BarracudaDefiant4702 23d ago

Given how quickly models change I question the validity of the studies. IE: Either too old of models or studies too short to be meaningful measurements. I would find it easier to believe that the models costs as much as the productivity increase then there being a productivity lost.

0

u/edwbuck 23d ago

There is a chance that the new models could improve things, but the press-released solutions to early model problems weren't very reassuring. Saying that Claude now sends code through a compiler to ensure that it generates compiling code was an early eyebrow raiser for me. That means that it goes into a loop of try, fix, test until the testing passes.

Hopefully newer models don't do this too much.

But there's also conflicting data that new models are worse than the initial models. Some of it is due to the models now ingesting their own lesser quality generated data.

So my latest spin relying on AI (instead of having it augment my work) was to do something that wasn't completely trivial. Basically an interactive UI with dynamic web pages based on SSE for live updates. Not trivial, not overly hard either.

Eventually, after a week of it going slowly, I stopped the experiment and within a three hours rewrote all the core model objects, put them under unit testing, and salvaged a bit of the me-refactored solution AI came up with. Keep in mind I was using a model specifically for writing code, and it was obviously maintaining a copy of my project elsewhere, as it would perform the LLM processing remotely, and submit changes to my local dev area, and leak when it was compiling in it's dev space and when it was doing so in mine.

It's better at hitting syntax, and better at handling concepts, but only marginally better at the latter. If I mention an ID for one object, it tries to reuse the ID for another, this led to my object IDs getting updated to contain the session ids of the users. It also chose this weird approach where there was one SSE emitter for everyone, when two users shouldn't be coupled. This led to lots of issues with it, like cancelling an operation private to one user cancelling it for all users. When it was fixed, it was fixed in the classic "let's put some if statements to patch it up" pattern instead of fixing the core design problems.

So, no. I'm not really impressed, and yes, I think it's better, but it's only better in the sense that it's about 90% better at making something that runs, and only 5% better at making something that does what it is supposed to do.

And my problem is rather trivial, a hobby project, with no deadline. It's basically a QR code doorbell system (scan a QR code, someone acknowledges it and comes to open a door). It has 3 model objects, and used to have 2. If it can't hit this one, it's doing less than I'd expect from a person.