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).I really love when I ask the AI to do something, and it gives me 40-50 lines to do it, and I tell it there’s no way something like that should take that much code, and it’s like oh, ya you’re right, here’s a 5 line version using something from from the standard sdk.
I’ve tried to put in its memory to not do things like that, but it keeps doing it.
Even without external libraries, it routinely comes up with solutions that are at least 3-4x the complexity and LOC than how I would implement it.
It’s because the average quality of code that they are trained on is like that. Most code that is written by humans is slop, and the models represent that.
Producing overly complicated solutions to uncomplicated problems
It often can do it better if you prod it though. Its just so weird that its really hard to get it to do that. It knows how even if it is trained on poor over complicated stuff.
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.
AI in engineering is an accelerator. If you are producing slop software, which most teams are, then it’s just going to accelerate the rate at which you can produce shitty software and bad code.
If teams are producing high-quality software, then it accelerates those teams’ ability to deliver that quality.
This is exactly it. I’ve worked with 2 different teams in this new era. One has all strong engineers and good review and testing standards. The other has 20% bad engineers that should have been fired years ago and’s weaker testing culture. The result is the strong team is delivering higher quantity software faster than ever, and the other team is going fast with much worse results. The quality is very bad, and the good engineers still there are quitting.
The good engineers spend their whole days just trying to keep the ship afloat and minimizing the harm from the bad engineers. They hate it and are burning out fast.
If you’re just hitting enter you’re doing it so wrong.
I‘d love if I could just hit enter but the garbage it shits out unsupervised is just soo bad.
Oh it’s way worser than that. Its erasing our skill
oh no a tech worker is whining about something again. Quick everyone rush to their defense. They must remain perfectly comfortable and happy inside their air conditioned luxury office.
Its work and you’re paid well for it. Suck it up or put your skills to use at a different company.
Okay, Mr. Spacely.
Agents are brain gang banging him.
I was going to say i could automate pressing enter if they give me a job
Sorry, you need a degree and twenty years of experience for this entry-level position.
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.
- Accept 10 jobs
- Make a script that presses enter on repeat
- Deploy script
- Collect 10 salaries
I like where your head is at but I’m an Enter pressing purist. Scripts fail and don’t give you the the confidence to know your true enter pressing quantity.
If the company wants enter pressing slip then scripts are the way to go. If they want to know with 100% accuracy no enter presses were skipped then I’m their guy.
Claude tested my script, all I had to do was press enter
/s in case it wasn’t obvious
Oo! Them! Hire this one!!
Their resume says “Enter Pressing Specialist” so they have the edge
Will you accept a $20,000 a year salary without dental and vision?
Depends on how many times I need to hit enter during my 8 hour shift. If it’s something like 200 times then yes. If you need something more like 7,200 enters pressed in an 8 hour shift then that would break down to 15 enters per minute which requires a little more dedication. I that event I would like to ask for $23,000 a year.
I would also like for the company to pay for any repairs or replacement of my Enter button in the event something stops working.
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.
I want to get off Mr. Bones’ Wild Ride.
Time to lean into the slop extra hard. Use AI to create massive PRs, use AI to approve the PRs. Automate sending slack alerts when a feature ships. Be loud, really show some massive “Productivity”.
A guy I don’t really like at work does all sorts of AI induced PRs. I think he thinks it makes him look good. It probably does, to management.
I got reprimanded for asking if a guy’s extremely weird code was something he wrote himself. He went crying to my boss about how I’m mean on PRs. Fuck you, William. I hope your house catches fire and you pass out while asking Claude for help.
Hey William, I’m having trouble understanding this code, it looks a little weird, can you walk me through it in detail, and explain how you came to writing it like this?
Our place measures PR counts so a ton of tiny ass PRs is actually the move.
I’m sorry for your shitty workplace.
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.
Look I’m all for the AI hate but this is just stupid. I’m aware this might not be the most popular opinion here but be warned
Honestly if I were to change jobs atm asking about their AI policy and usage would be one of the first questions that I’d do and if they don’t use it well and haven’t figured out how to integrate it in their company (as a tool, not necessarily as a product) then I’d end the meeting then and there.
I’d quit my current company if they prohibited AI tools. Fortunately they don’t force us to use them, nor but we’re all encouraged to find actually uses for it (which in Software Engineering are a ton). If one of my colleagues wouldn’t use AI in any way I no only would consider them less productive, I’d consider them a worse engineer because it shows they can’t adapt.
AI in general and Claude Code as an example is an AMAZING tool. You just gotta use it properly. I still own the code I ship even if I understand it in less detail than before (that’s the trade off by being able to ship many more features than I could in the past).
I’ve been in this company for a few years now and just in the past months there are so many projects I have done that there was never an opportunity to do so ever since I joined because it would be days/weeks of work and now it’s a couple of hours while I work on other shit.
And people/companies that spend hundreds of thousands of dollars in AI every month are idiots who are just throwing shit at a wall and seeing what sticks. My company pays me a 100$ month subscription and many colleagues have even cheaper ones. Thats like 1% of my salary and it for sure increases my productivity many orders of magnitude of that.
The reality is that these tools are not going away. Thinking that will happen is not realistic.
They’re part of the deal now. People who refuse to use them will simply become obsolete. It starts in technology, but it will quickly move around.
Thinking you can just avoid it isn’t practical. It is no different from cars displacing horses and computers displacing typewriters.
Think of how absurd it would sound if you came across someone who refuses to use a computer and only a typewriter.
Nah, fuck AI. I will pivot careers. Anyone that claims to be a developer but generates all of their code is just a modern day script kiddie. Idgaf about efficiencies because the ethical implications of AI are far worse than the extra money I can make for a company.
I will never be an AI code reviewer, because that’s all prompting is. Like I said, I’ll pivot careers out of dev work before I do that. Pick up a trade and work until I’m 80 if I have to, but that’s still better than being one of Claude’s bitches.
Outside of the ethics of AI, the idea of sitting in front of a screen and being a “prompt engineer” takes everything I enjoy out of coding. If it was that or death, I’d choose death.
I have not found AI code to be so helpful. I actually use it a lot less and more strategically than back when it first became viable. It can save a lot of time in the right situation though.
The guy is working at a shitty sweat shop and blame AI for his misery instead of moving his ass to another job.
Let’s ask Claude to write an article about it.
workers spend 12-hour days pressing enter
If only that could be automated somehow.
I feel like you are being sarcastic, but this actually is a solved problem :
An elegant solution. I wonder if it is more efficient than a 1TW data centre.
Seriously, though, we use AI in the worst way possible. I like writing code, I hate checking someone else’s code. Why aren’t AIs doing the checking and engineers doing the coding?
Forget “human in the loop” - let’s shoot for “reviewed by AI”. Deep down, we know the humans are barely paying attention when they check Claude’s homework.
Forget “human in the loop” - let’s shoot for “reviewed by AI”
yeah uh, nah, thanks. I would not trust it any more than I trust the current shit show.
The drinking bird only works if it’s dipping it’s velvert covered head into water, the lower water temp creates a temo difference moving the liquid in the glass tube within the bird
I can attest this does work well. Having LLMs review your plans for how to do something and point out what you missed works well too. I also have my local LLM review creative writing without writing anything, give feedback about my Blender renders and other artistic things, and be a sounding board for ideas in general. Be warned that Qwen has no mercy and will shit all over your passion projects.
You absolutely can do that tbh.
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.
And that’s not even talking about code review.
No time for that, we’ve got to hit the sprint end date!
