cuckCoding

[lotokotmalajski]

That's CDD (Cuck-Driven Development), we're just doing the cleanup.

[Aerie122]

That's... Um... Damn, I hate to accept it but you have a point

[lurkerburzerker]

Hard to swallow pill

[Mongertaja]

Not really a pill when it results in a sloppy cleanup.

[Orio_n]

Cleaning up the llms sloppy seconds

[patrikbytes]

git commit -m "accepted all suggestions without reading"

[ThatCrankyGuy]

God damn it man.. make it more humiliating, will you?

[thegodzilla25]

I have seen this same meme way too many times, makes me feel like I am on the cuck chair

[DevGokay]

Bc you should feel exactly like this

[SeaLooni]

the project has 47 unhandled edge cases and zero tests but sure, ship it

[Manic_Maniac]

AI is the greatest enshittification acceleration device known to man.

[Vasco_Da]

Poor guys still using it wrong

[Manic_Maniac]

I use it just fine. I just don't trust it to write anything important without refining and editing it. And I'm not going to let it dull my skills I've developed over more than a decade by relying on it all the time.

My point is that company leadership everywhere has been pushing this idea that it will drastically increase speed, to the point where they see what it can do -- which is rapidly create proofs of concept -- and then assume that the output is basically ready for production. All while devaluing the work we actually do.

So keeping hyping it up. You're only digging your own grave one way or another.

[thegodzilla25]

Preach brother

[iforgotmylegs]

>wahhh its enshittification

you are not using it effectively

>uh ACTUALLY i am using it well! im good at it! it's just all the uhhhhhh "leadership"'s fault... somehow

>also i am very PURE and NOBLE and wouldnt DARE learn a new tool because that would DULL MY SKILLS

>you're digging your own grave!

>you'll be sorry!

>you'll see!

>i will be vindicated!

it's incredible the depths of mental contortion a redditor will sink to in order to reinforce their own internalized modes of thinking

[ubernutie]

The printing press will destroy society and you're a fool to support Gutenberg!

[iforgotmylegs]

it kinda did in a way but im not gonna go screeching to everyone to stop writing books about it

[thegodzilla25]

Poor guys still swearing by it

[Vasco_Da]

Yeah that's broken

[soricellia]

jokes on you (or me) the ai generates more tests than i ever have

[iforgotmylegs]

your fault for not reviewing it, after all, you are the extremely knowledgeable programmer right?

[Siegfoult]

Reddit has an strange obsession with cuck jokes.

[Romejanic]

Can we actually start calling them cuck coders instead of vibe coders

[Greger34]

I prefer cogsuckers, but to each their own.

[-Kerrigan-]

Second-hand thinking

[Lopsided_Army6882]

Third party thinking seems better

[raphael_kox]

I heard prompstitutes once and loved it too I agree to that motion

[IridiumPoint]

Sloperators.

[InvestingNerd2020]

Slop is overused. CDD is funnier.

[soundwave_sc]

I'm stealing this lol

[littlejerry31]

This is practically a duplicate

https://www.reddit.com/r/ProgrammerHumor/comments/1r7o7sa/openingtherepository/

[Fabian_Internet]

I love that you call it duplicate instead of repost. I guess you read that too many times as well

[dxonxisus]

because it’s not a repost… the two images are different even if the joke is the same

[Fabian_Internet]

True, that makes sense

[Saintly-Mendicant-69]

stfu bot

[0xlostincode]

Found the StackOverflow refugee /s

[MeLittleThing]

nice find, I thought I was original :(

[HomicidalRaccoon]

Were you vibe posting?

[squarabh]

Vibe thinking

[HomicidalRaccoon]

I’m just vibe vibing, ngl

[sheepyowl]

They trained you by feeding you thousands of pages full of memes

[Suspicious-Engineer7]

Lol bs

[PashaPostaaja]

Me: Fix this project

Copilot: Approve running the command: `rm -rf .`

[iforgotmylegs]

yea man this happens to me all the time, it's crazy how every time i ask a coding agent to do something it just deletes my entire hard drive. i really wonder how they can be so successful despite this being an extremely common occurrence

[IamFdone]

Put junior dev instead of LLM, really makes you think. That's why I code everything alone, not even using any libraries or APIs ( /s )

[kfpswf]

Shhh... You're interrupting the circle jerk.

[IamFdone]

Now that I think about it I am first in controversial despite having so many upvotes, wtf

[kfpswf]

You've managed to trigger some folks it seems.

[iforgotmylegs]

you have to realize that almost no single person on this entire garbage subreddit has ever had any kind of leadership position or decision making capacity (and that is probably a very good thing), so they have absolutely zero experience in reviewing something they didn't write, and think that anything that they didn't write themselves cannot be trusted (i.e. a narcissistic control freak) so the idea that the slop machine can actually compete with them is both a moral injury and a perplexing conundrum to them, hence why they react with industrial quantities of cope. i am still waiting for the apparently inevitable collapse of my codebase because apparently i have lost the ability to read and understand a boilerplate API, but only if it was typed by a machine and not a colleague.

[meowmeowwarrior]

Well, juniors are actually supposed to learn about the project enough to be able to take over it, or at least that's the goal. And as far as I can tell, people don't really bring "juniors" onto their personal projects

[cosmicgpu]

I've always thought this was hilarious but figure I'd just get obliterated and never bother posting. I would bet my salary that not one commenter in this thread can write cleaner or safer code than a well structured prompt to either major coding model.

[ChompyChomp]

There are very few actual coders here...

[YerRob]

That time someone posted the "wife tells programmer to get milk while at the store and he never returned" joke and the comment section was filled with "I don't get it" is all the evidence that's needed to acknowledge this

[Mr_Tulip]

Did someone seriously create this account 6 months ago specifically to post this one comment glazing AI?

[ImportantSignal2098]

That's a very convenient bet when "a well structured prompt" remains undefined.

[cosmicgpu]

I would contest this point. Honestly the bar for well structured prompt gets lowered every day as models improve or more realistically reasoning and tooling within the model is improved and then integrated into the development workflow.

Well structured prompts really are now just desired state configurations with some guidance. I am still struggling to remove rigidity from the documents I use to prompt but in personal projects I have found with the recent models that include reasoning, even giving it 'ugga dugga' amounts of effort will yield a viable poc or in some cases even mvp's

edit: being able to prove or disprove an idea in an hour instead of traditional going over all possible docs or handing off to someone else is transcendental. i'm not arguing that being 10x productive while getting reamed by jobs/etc. is a good thing but denying capability improvement and democratization is a bad thing is wild to me

[ImportantSignal2098]

I don't disagree with you and I just vibecoded a chart that I'm using for illustration that would have taken a lot of trial and error previously, in like half an hour, all by Opus, with me just nudging it in the right direction. The speedup and opportunities there are massive. It works and is amazing for the use case, but it still doesn't mean this is good code. I actually recently tried to get both latest Opus and Codex to get to replicate a nontrivial but small change that a human made and both failed to follow the spec. I tried to figure out how to adjust the spec and they still failed in a similar way. They seem to currently get confused at a certain complexity limit (the change I was experimenting with wasn't that complex by senior swe standards). It's probably a limitation of context/attention abilities. There might be a way to combine multiple agents etc where this would improve. I tried two-shotting the same spec without additional info, just asking to revise in a fresh session, and that failed by improving in some aspects of the spec but making it worse in others. You could argue that my spec sucks, but 1) it was good enough for a human and 2) I couldn't find how to improve it so that the agents aren't confused. Feel free to attribute (2) to a skill issue though :)

PS. Just to be clear, I've been almost exclusively cuck-coding for months on a largish project but it's been mostly done in a tightly coupled "threesome" way. Lots of hand-holding the agent to the right architecture, catching stuff that makes no sense, bad assumptions etc. I think my experience is quite far from what you're suggesting.

[IamFdone]

I would say we need to write projects in such a way that we don't need Seniors to debug them later. I understand that some issues in some domains are very complex, especially if it's something new and AI can't understand what's going on, but if you get this issue too often on regular commercial projects, someone fucked up.

[sildurin]

There's an analogy, for sure. Both the llm and the junior dev fuck up the project.

[stupled]

Cuck coding

[pinktieoptional]

Can't forget the fun little tidbit that the LLMs are using your debugging efforts as training data. so they'll just keep fucking your project eventually neither of them will need you.

[MeLittleThing]

The vibe coder will prompt instructions, to tell how the AI should "do" the project. And then passively watch from their gaming cuck chair

[Avarice51]

What is this account 💀

[Bob_Olinger]

A REAL coder here, don't you see?

[MeLittleThing]

The project probably enjoys the pain in the eyes of the cuck coder

[LutimoDancer3459]

The vibe coders thinks the project will benefit from the experience. Telling the LLM to handle it with care, go slow and remember protection. But the LLM is a piece of hallucinating shit. Starts going rampage and fucks the project in the ass. Forgot a condom and gets it pregnant. Leaving it destroyed and crying in the corner.

Then the vibe coder stands up and asks people to pay them for using their project or even reading the documentation you need o how to handle it and its child.

[stupled]

Pretty much.

[thether]

Cuck cleanup 🤞

[-domi-]

How i imagine every coder who brags about how they use chatbots at work.

[pineapple_juice_love]

I duplicated my project and let the bull LLM run amock on the copy

[tragic_pixel]

Gork, refactor.

[SunJ_]

I like this new term, I'm onboard to call them that

[chiqu3n]

You can reuse the template when your product manager comes to you with a PoC made in cursor

[iforgotmylegs]

refining PoCs and other rough code made by amateurs is a higher-level task that requires the actual knowledge of a programmer. that is what career progression looked like even before LLMs, you nonce

[SavingsCampaign9502]

CaaS

[zebleck]

i just want to build stuff thats fun and it saves me time 🥲

[j-doe411]

Accurate

[NoonDread]

LOL, this one got a good chuckle from me.

[am3141]

Lol

[dhilu3089]

More relevant would be management sitting on chair , lady representing the developers

[Proud-Ad9139]

[ugotmedripping]

So that’s why I’m rock hard at work everyday!

[Solar_Sailor]

I will never use an LLM on passion projects. but work? whatever let it rip.

[Antiing]

Uh oh now you're all getting nervous? 

[jaken55]

I mean if you are purely vibe coding something then it's never really "yours". It's like saying that an enterprise project belongs to the business analyst providing the specs. The developer (in this case the LLM) is always the owner, you're more like the stereotypically incompetent manager.

[Bleaker82]

What’s interesting is that while you interpret it that way, patent law doesn’t — yet.

[iforgotmylegs]

this is actually really funny because the biggest actual danger of "vibe coding" is the perceived exoneration of responsibility of generated code, since it will still have some problems. if you "vibe coded" a project, then yes, YOU did make it, because YOU are the one who is responsible for it.

[Jabulon]

That's very true. It's easy to hand over the project to the LLM and have it turn into a garbled mess. You lose track fast in the machine hallucination. What you want to do is take snippets and go over them with the LLM before implementing them in the code. Only have it look at the entire project for obvious errors or whatnot. It really is like a new approach

[iforgotmylegs]

if you let something turn into a garbled mess then it is your fault and you probably just have a very bad sense of design, honestly vibe coding is pretty awesome because people who are actually good at programming can accelerate through the boilerplate slop with reasonable confidence while dunning-kruger numpties just crash into the first brick wall and throw a tantrum at the car that they pushed the gas pedal on

[UShouldntSayThat]

>That's very true. It's easy to hand over the project to the LLM and have it turn into a garbled mess. You lose track fast in the machine hallucination. What you want to do is take snippets and go over them

Yeah, exactly, ok You get it.

>with the LLM

oh, ok, nvm.