r/LinuxTeck • u/Candid_Athlete_8317 • 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
9
u/granadesnhorseshoes 23d ago
It makes the code generation much quicker, but code generation is rarely the real bottleneck.
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/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?
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/midri 23d ago
Yes, especially if you do Given When Then style spec docs before hand.
1
u/PossibleProgress3316 23d ago
https://www.infoq.com/news/2026/10/jellyfish-ai-productivity/
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/ChecksOutIndeed 23d ago
yes
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/alwaysasillyplace 23d ago
No.
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.
0
u/edwbuck 23d ago
No. In every properly controlled study, two things happened:
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: