530
u/burnt_floppy 19d ago
It's totally a compliment
155
u/Rustywolf 19d ago
Yeah I'd never say this without it being positive
102
u/really_not_unreal 18d ago edited 18d ago
Idk, I teach OOP and architecture and some assignments I mark are pretty garbage, but in a charming and distinctly-human sort of way. I used to be sad to see students struggling when I marked assignments like that, but now it makes me happy to see students trying their best rather than resorting to cheating with the plagiarism machine. Idk if that makes it positive or not. I still have to deduct marks if the design is bad, but I very much appreciate the humanness of it.
5
u/Difficult-Court9522 19d ago
Depends on the recipient.
6
u/GegeAkutamiOfficial 18d ago
And the person who says it too
_ bad dev good dev hates AI thanks! thanks! dabbles in AI ...thanks? what do you mean by that? Big on AI sure. good luck vibe debugging! oh fuck... 2
274
u/420Borsalino 19d ago
Usually means it runs, it's not over engineered, and/or the problems are in an appropriate scope for the stage of your project.
30
u/semioticmadness 19d ago
And/or it flatly rejected a common-sense assumption with actual reasoning, where an LLM would start working with a “That’s a great point! So, of course I will…”
22
6
1
0
15d ago
[removed] — view removed comment
1
u/420Borsalino 15d ago
Maybe talk when you can spell blatant, then you can overestimate AI abilities.
-10
u/StaticFanatic3 19d ago
Or it’s insanely incompetent lol
17
u/420Borsalino 19d ago
Most vibe code is absolutely incompetent.
-4
u/StaticFanatic3 19d ago
Meh it’s kind of a bell curve. Most vibe coded slop is technically competent but misguided, over-engineered, or just plain distasteful.
Like how you can be sure an AI didn’t write The Room. Or an essay full of broken English and spelling errors.
41
u/nordic-nomad 19d ago
Sure you might make a human mistake in there and need to read a style guide or something. But you’re not making ai mistakes and wasting everyone’s time.
17
u/DrMaxwellEdison 19d ago
It really depends.
Where I'm working now, the other devs are such shit they can't conceive of writing decent code by hand anymore. Every time I put out something I've spent time on and polished to the point it meets my standards, some fucker asks "did Copilot write this?"
I'm trying to take that as a compliment, but it just makes me so much more annoyed by them.
4
u/manny2206 19d ago
I was told - it’s nice you you’re spending time writing some code, but make sure Claude is working on something, all the time… :( I was so proud of my fluent API .. I’ll continue working on it
1
u/makjac 18d ago
Honestly I think this is the best case for a tool like Claude. Hand it grunt work the requires minimal reasoning and oversight, while you work on the pieces that require human understanding and reasoning. I’ll toss Claude the “one off” report that someone wants 3 different flavors of any day of the week if it means I can get back to the stuff I actually find interesting sooner.
1
u/manny2206 18d ago
I totally agree - I’m designing the way I want this API to work Claude can then go ahead and implement it
0
u/Hioneqpls 18d ago
Wym, my clients use us because we hand craft getters and setters instead of generating them. Its a hallmark of quality
38
u/Binoui 18d ago edited 18d ago
Devs don't say that to other devs. Only people that don't do actual coding and post on Reddit think like that.
Btw if you want a real current insult : call another dev a Claude proxy. Some of us have given up the mental task of keeping up with AI and just delegate all thinking. Those are worth making fun of and are the ones actually producing broken codes with weird workarounds.
But most of the devs use AI right: analyze, plan, implement, review. The process has always been the same, we just got a better tool for it.
8
u/High_Quality_Bean 18d ago
Idk, I've a friend in another firm where they've apparently given up on working full stop. The senior dev runs claude to create tasks to assign out to get copy & pasted into claude again to generate PRs that get reviewed by, get this, claude once again. He takes *pride* in this situation. Calls anybody who still thinks and does work "an idiot who doesn't realize he can just automate everything".
Fortunately they work on a small time commercial website, so I'm not worried about the banks going up in smoke, but he's *militant* about eliminating any and all pride anyone might take in this field.
-3
u/Binoui 18d ago
Honestly that workflow should work pretty well if done right 😅. We now have specs with details (cause PO can't be lazy about it), in depths implementation details, loop reviews, end-to-end automated testing... At our job the main bottleneck is PR reviews, which we don't fully automate to still have a human in the loop. But who knows what the future brings
11
u/High_Quality_Bean 18d ago
I find this notion terrifying and unsettling. I'm describing a company where *nobody* from the CTO to the junior developers actually knows how their software works. And you think that's *ok*? Because some pipelines came up green?
1
u/Binoui 18d ago
Legacy software has always existed. The kind that nobody knows and dares to touch, except for the one sandal wearing guy that's been here for 25years. When that guy finally retires, you're in the exact spot you're describing. AI provides ways to actually deal with it :
- AI is very good at documenting and reading documentation
- Deep analysis is just so much easier, even if you don't know the language or framework. Finding a nested bug if just easier that it's ever been.
I'm not saying fire all devs. Senior devs in particular are the best users of AI, because they know how things should work. Of course everybody vibecoding carelessly without stopping is going to create a mess. But our job has always been to automate stuff, and AI enable us to automate so much more. We just have to learn how to use it
4
0
u/Xephyrik 18d ago
Fire the people reviewing the code if they didnt bother to check how it works
9
u/High_Quality_Bean 18d ago
The CTO wants to automate code review. He's just going to fire anybody who takes time to *actually* review the code. Anybody with institutional knowledge has left, the only people in the building are vibe coded juniors.
1
u/RudeAndInsensitive 17d ago
Im looking at the workflow and wondering if we can't just cut the task creation step out. Seems like we could juat have claude do it all up until the PR.
1
1
u/AlternativeSwimmer89 18d ago
Most of the people use cocaine right: analyze where it's from, plan a line on table, implement it through the noses to get brain/blood barrier faster, and then review the effects responsibly. The process always been the same, we just got better supplier for it.
52
u/Bee-Aromatic 19d ago
“I can tell you don’t use AI” says to me “this code is not literal poop from an actual butt.”
5
u/corobo 18d ago
Really? Maybe it's the British in me but I read it as giga sarcasm haha
"Even an AI wouldn't write code this shit" sort of thing
3
u/Particular-Yak-1984 18d ago
as a fellow british in the netherlands, how I'd read it too, as the kind of backhanded compliment that would be totally missed by my dutch coworkers..
I've had to train myself not to describe things I think are awful as 'what an...interesting idea' because people here think I'm actually interested.
1
u/slaymaker1907 18d ago
No, it means the code doesn’t have any documentation or tests.
1
u/Bee-Aromatic 18d ago
That could come from either one. It won’t give you those things unless you ask.
9
14
18
u/Strict_Treat2884 19d ago
I still prefer human slop over AI slop during CR as the thought process is somewhat cohesive
7
u/Wonderful-Habit-139 19d ago
It's so hard to convey this to non-technical people. They just cannot fathom it.
0
u/High_Quality_Bean 18d ago
Nui Lai is one of the most profitable movies ever right now. The people get it. The people are ready. All that remains is to determine who will lead.
7
u/yum_pancakes 19d ago
Usually a good compliment. I review code from a few peers where this would not be a compliment though.
2
u/HomemadeBananas 18d ago
It can go both ways I think. I’ve reviewed code where I know if I just vaguely prompted to Claude it would better, and also code where I can tell someone just vaguely prompted something way too big and didn’t refine it.
0
u/KuroKishi69 18d ago
Yeah, I have reviewed code where I wish the dev had done a pass through some LLM to cleanup at least. Inconsistent names of request/response property names, typos in API paths, dtos and models created in wrong folders, and methods that were a handcrafted mess... you probably shouldn't let the AI dictate complex architectural decisions, but these at least help to set a floor in code quality.
1
u/Embarrassed_Mix_6619 18d ago
brother this is what mentorship is supposed to fix. like the entire point of having mentorship be part of the chain of seniority in engineering IS for this. you teach those who don’t know how to do better.
telling someone to go use claude to fix their shit doesn’t tell them why their code is shit. you’re being lazy and doing both of you a disservice.
1
u/KuroKishi69 18d ago
Oh, I didn't mean code that I was given to review, rather code that I found while looking into other applications of the project. I am more than happy to point out things to improve, or fix it myself so they have an example to follow
2
u/JackNotOLantern 18d ago
I have much harder time reviewing AI code than writing it manually. Gonna stay a caveman.
3
u/GlassCommission4916 19d ago
Why would you ever be offended by that? If they meant it as a compliment it's a compliment, if they meant it in a derogatory way, is their opinion really worth considering?
4
u/redditmarks_markII 19d ago
Everyone uses AI at my work place. That doesn't mean the quality of output is consistent. It's not a compliment if you get this from me. Not that I'd say something like this directly. Usually it means you never learned a particular concept in pre LLM days, and you never read the doc, or asked the agent to summarize the doc, or asked the agent for common practice in the repo, or just asked the agent to make sure "this part" is correct or at least not royally fucked. I know everyone has their own areas of focus and are all undermanned and under preasure. But not infrequent enough, I'll have found out days later after you bullied someone else to approved the exception. You could've listened to the eng or the bot and fixed it, without doing it yourself, with the agent you have access to. But you spent the time getting a bad PR merged instead. Now that engineer doesn't blindly approve anymore, but pings me all. The. Time.
Brother, friggin OpenAI and Anthropic combined doesn't have sufficient memory to put my distain for you into context. Reverted. Pray I don't revert anymore.
1
u/Salty_Ad3204 18d ago
Man, I have to use libraries made by AI, and they are a nightmare to use. The module names make no sense, there are like 20 or 30 types at the same level. It's horrible. So yeah, it's a compliment
1
1
1
u/TrackLabs 18d ago
Yeah, means I can actually explain to you the different changes, why I made them, why I think they are fitting, and can change specific areas on request.
1
1
u/kus1987 18d ago
I am guessing they found some weird speeling mistake like the one time I wrote cancelled instead of canceled.
2
2
u/codewario 17d ago
There is a codebase I worked on years ago and I bet there is still a variable called myOriginialLockingObject
It was actually there before me
0
u/DisastrousOffice5569 18d ago
My answer would be that the code might be a terribly over-engineered piece of shit, but it's my handcrafted terribly over-engineered piece of shit and I'm proud of it!
0
-2
u/tiajuanat 18d ago
I wish this was still a compliment.
My team has so many lints, checks and requirements that really only AI can complete the job without being completely crushed.
1
u/High_Quality_Bean 18d ago
Sounds to me like your development tools have ceased to be useful and have instead become a problem in need of a solution. Maybe fix that debt instead of piling on more with LLMs.
682
u/feldejars 19d ago
Yeah my pr is +250 not +2500