@Mustachius_Grumpius@thelemmy.club
2026-09-23 14:31 UTC
Replies (8)
-
@Kaligalis@lemmy.world 2026-09-24 03:22
AI code assistants currently are like that senior dev who knows everything, has experience in everything, and always likes to help everyone. But sadly he does a lot of shrooms in his spare time and sees things that aren’t there. He also has quite the opinionated ideas about what good code should look like. That implies that you just can’t let him do the quality assurance. He can write code. You can ask him stuff. And he excels at debugging. But you can’t let him plan the architecture. You can ask him about his ideas and select the ones that are actually good, though. And you definitely can’t let him review his own code. Someone else has to do that. So if they literally just let the AI do everything, there is absolutely no way anyone has a chance to ever review the result because AI code is harder to review (for now), and AI loves to repeat itself (for now). And sure, they can tell it to write tests. But AI is dogshit at writing tests. It tends to forget the important cases, test the wrong thing, and/or obsess about completely irrelevant implementation details. I also tried the multi-round approach with a committee of agents trying to iteratively find and fix flaws. It only works well for finding bugs, not fixing them (for now). But while AI can’t replace me, it is really nice to have as a tool - just like I have syntax highlighting in the IDE, I have a code assistant that can autocomplete a few lines of code, find out why my code misbehaves, or tell me what some library method is supposed to do. Sure, I have to still verify the results. But often, finding the bug or information was the hard part. Coding assistants are great. Just don’t let them write too much code at once. You need someone who still actually understands the codebase. That sadly can’t be an AI (yet).
-
@criss_cross@lemmy.world 2026-09-23 20:09
I don’t hate Claude Code or whatever. I hate the company pushing you to constantly churn out shit so you need to turn to these tools to keep up pace or get fired. Architecture decisions or code quality? Fuck it just ship. You have concerns about an approach? You’re the enemy to your coworker’s promotion. Get out of the way. It’s all just so depressing. It will all come crumbling down. It’s a matter of when not if. But god I hate this ride right now.
-
@schipelblorp@sh.itjust.works 2026-09-23 14:40
Reminder here that the culprit is capitalism, not LLMs. Voxium said he wouldn’t mind the situation if workers were given more time to check the code. “Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude,” he added. “There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore.” Some people might look at this and wonder what the problem is – who wouldn’t want to be paid to do very little? But most people struggle when their work has no meaning. Voxium told Business Insider that if engineers lose the opportunity to understand the code and solve difficult problems, “there is nothing left … Not even our soul. There will be no purpose.” He added that the real problem is corporate leaders’ obsession with pushing out more features. He said management often judges success by sprint cycles, pull requests, and the sheer number of features shipped, even when those additions do little to improve the product for users.
-
@BillyClark@piefed.social 2026-09-24 01:59
The engineer added that employees are now pressured to ship products as fast as possible, leaving them with little time to review Claude’s output or understand the code being created. Companies have always pressured software teams to ship products as fast as possible. What’s new is the part where all of the worst coders can shit out code a lot faster and pretend like they’re doing a good job. It used to take them a while to write garbage that they didn’t understand or review themselves, but now they can do it so quickly that it makes the actual good coders look like they’re taking a long time. This is why you absolutely have to have documented coding and review standards. The idea that you’d ship any code that has never been reviewed by a human is horrifying. The idea that you’d work 12 hour days is so stupid to start with. I’ve seen people consistently work that long and… surprise, they don’t actually work that long. They work about the same as anybody else and goof off the rest of the time. I doubt you can even just press enter for that long. People just don’t work that way.
-
@xia@lemmy.ca 2026-09-23 23:28
-
@BassTurd@lemmy.world 2026-09-23 19:13
If I’m forced into Claude Code or something similar, I will be looking for a new job. Ideally a different role in my company to keep my benefits and not have to completely start over, but if I have to jump ship, I will. Fortunately, our security and GRC teams have explicitly blocked Claude Code for the time being. I still have the tools built into Visual Studio, but I seldomly use them, and when I do it’s basically as stack overflow, and that only when I can’t find what I’m looking for through web searches first. We had someone from our Networking team come over the other day and say that he could tell our summer interns were gone because our AI usage dropped by over $1000 / month.
-
@404found@lemmy.zip 2026-09-23 20:39
I would like to apply for this software engineer job where all you do is press enter. I’m willing to work from home or go to the office everyday. I will press enter on holidays and weekends as well.
-
@Modern_medicine_isnt@lemmy.world 2026-09-23 16:15
One… use --dangerously… they asked for speed, thats how you get it. Two… if you have great tests, you don’t really need to know every detail of the code. The risk just shifts from a dev designing bad code, to a dev designing bad tests.