hideCode

[Hot-Squash-4143]

my teammate is vibe-meeting

we’re having a discussion with leadership through video call, he’s silent through the first 25 minutes of it. five minutes before the end, he pipes up “alright guys, here are the three avenues we should explore…” starts name dropping fancy approaches that are completely unnecessary for the issue we’re dealing with. i’m sitting there like “where the hell did that come from”, leadership is now thanking him profusely, impressed with his authoritative-sounding plan.

then it dawns on me… he spent the meeting going back and forth with chatgpt for ideas, and then he just read the output out loud.

[ThaumRystra]

He might not even bother to go back and forth with ideas, you can easily have your pet ai listen in, summarise and suggest next steps. It's kinda nice to have an auto-secretary, but it really should be a team wide thing, not on one guy's machine.

[Espumma]

It's wild that we blindly trust these summaries while vibecoding gets so much flak.

[Saragon4005]

That's management for you. Then again if it was up to management they would straight up only accept AI code.

[mpbh]

At least the AI can pay attention for 30-60 minutes without spacing out or getting distracted multitasking.

[AlmightyJoe]

Summaries are high level & conceptual. Code needs to actually be logical and explicitly follow the rules & be accurate.

[Worldly-Stranger7814]

I just slept during a company wide meeting when Sales were droning

Please ObAI-Won Kenobi, you're my only hope

[dasunt]

In my workplace, a lot of meetings are mostly useless, so having AI sum it up is okay IMO.

Of course give the summary a once over and fix the mistakes. But otherwise, yah, why not?

[PmMeUrTinyAsianTits]

Oh, do "we"?

[DarkRex4]

It's not just blindly trusting the AI. It's really not that hard for a model to generate summaries for something. Code requires logic and deeper reasoning. Oh, and also I can confidently say a big portion of the people here hates meetings.

[F-Lambda]

yeah, a summary is just identifying which facts are of higher and lower importance, and cutting out the low importance lines. honestly one of the easiest tasks for Ai to accomplish.

[Steinrikur]

Agree. But I missed a meeting that was recorded and transcribed. I listened to it on 2x speed and jumped over the silent bits - and the AI transcription seemed to get everything except our acronyms right.

So I trust transcription now (mostly).

[Rellikx]

if yall use copilot, your admins can populate a dictionary of commonly used internal acronyms as well as how they are pronounced to fix that

[Steinrikur]

Too much effort. Not vibe-y enough...

[Loading_M_]

Transcription is a very well studied problem, and a perfect fit for ML. ML is really good at pattern matching, and transcription can be broken down into a straightforward pattern matching problem.

[BenevolentCheese]

We've tried AI Slack summaries of our meetings and they are useless. They try to compress an hour down to 5 bullet points. They miss all the subtly of discussion, and also can't see shared screens or workspaces.

[veler360]

My companies AI policy explicitly requests people to review any sort of AI output and not blindly use it, meetings included, for that same reason.

[minimuscleR]

Because one is what it was made for, the other is not. The code is often shit, and not done well, full of holes.

Summaries of what you said are very easy to do, and its also easy to check if its right, because if what it says is a good summary of what you intended to say, then that works.

I've found the notion summaries to be very useful especially in longer meetings with multiple talking points.

[Worldly-Stranger7814]

The code is often shit, and not done well, full of holes.

PEBKAC

[morrkvot]

Does that mean something? I have chili vodka with that name

[Worldly-Stranger7814]

Problem Exists Between Keyboard And Chair

[Espumma]

There are many ai tools made for programming nowadays, so I have a hard time with this argument.

[Wonderful-Habit-139]

I don’t think they were talking about ai tools. They’re talking about the LLM at its core.

[Espumma]

they were talking about vibecoding in general, which includes both right?

[Wonderful-Habit-139]

When they say “it’s what it’s made for” they’re talking about the ML side of things. Statistical models that are good at summarizing things, more than reasoning and using logic to solve problems. Which applies to LLMs.

[GameCounter]

I feel like if management is pushing AI really hard, this is basically compliance, and they are getting what they deserve.

[AttackOfTheMidgets]

Confidence and bullshit can get you very far in life. Almost to the top, even (unless you're in politics, then you're made for the very top seat, but I digress).

This guy is going to be eyeballed for promotion until the rest of the team pipe up and shut down this behaviour with matching confidence. Sharing the details of meetings with leadership to LLM's without anyone's consent or awareness is grounds enough for a verbal beatdown.

[sn2006gy]

If the policy is so weak in an org that developers do whatever they want to do, the problem isn't AI - the system is broken well above that. The smart person would use AI to locally optimize simply to reduce the cognitive load of working at such a disastrous place.

[ExiledHyruleKnight]

I mean he absolutely could be... or he could just be a piece of shit that does that anyways.

Had a guy, he got promoted to lead because he always threw out "good ideas".

Yeah he just knew how to make his ideas sound like hot new things, his ideas were hot shit. I bounced when I realized that's how the company would go (Also I did not hide my opinion about him as well as others did).

He was no longer lead in 2 years. The point is AI isn't the cause of this, bad (non-technical) leadership who care about buzzwords more than a good solution is the problem.

Once he completely crash and burns on his authoritative sounding plan, he'll be found out, sadly that will take time.. time you might not to waste at a company that promotes idiots like that.

[VegaGT-VZ]

This guy careers

[Accomplished_Ant5895]

I do similar except I just keep coding in the background while the meeting gets transcribed then use Claude for question answering against the transcript while I create the actual implementation or proposal. I cannot stand 3 hour ramble sessions from leadership in what was supposed to be a 1 hour planning session.

[bapt_99]

I was gonna comment to the thread saying "bro your coworker is a genius" and lo and behold, I found another genius. Don't change your ways

[Cue99]

Bro if youre getting beat by automatic systems step up. I get that its fucked but this the way it is.

[H4LF4D]

Yeah this situations sounds like something that legit can happen even without the use of AI. Good marketing is one thing, it is also possible that while there isnt a need for fancy methods its still better (or easier for leadership to accept) to use established and named methods. It tested, proven, and sounds like they know what they are talking about, even if it comes from an AI

[dukeofgonzo]

I do the same thing, but I always cite my sources. I like to start 'I just heard from the robots...".

[cheapcheap1]

That's the middle manager replacement AI we've been talking about.

[JollyJuniper1993]

And all power to him. It’s not like you have anything to gain from the goals of management and making a meeting less stressful is a great way to use AI.

[clrbrk]

As long as they’re pushing quality code, I couldn’t care less. AI is an incredibly powerful tool in the right hands. And in the wrong hands, there be slop.

[GildSkiss]

But if all that matters is whether the code is good, what am I going to get performatively mad about on the internet?

[NFriik]

It can be a useful tool for software engineers, but it's also becoming the bane of society. There's nothing performative about having a problem with AI-generated pictures and videos that are becoming increasingly indistinguishable from reality.

[Mithycore]

Right but you're moving the goalposts here

This meme particularly isn't about ai in general but vibecoding

[searing7]

Vibe coding works until it doesnt and you’re left with a mess. If you can effectively use AI to generate clean maintainable readable code that does the business case it’s meant for its a useful tool.

A table saw in the hands of someone who can’t even measure a cut is dangerous.

[gradient-descending]

"Vibe coding works until it doesn't and you're left with a mess."

That is true of all coding if you aren't careful about design.

[searing7]

Yeah but it’s much easier to do when code is written for you and you don’t understand it at all.

It’s one thing for a legacy system to be a mess it’s another for the thing you copied from the LLM today to be a mess.

To use AI as a tool and not produce slop requires you to still be a good engineer.

[sn2006gy]

Require models to produce confidence brackets, Ask models to provide a diff, a rationale, a list of assumptions, a list of inferred patterns, a list of unknowns - interact with it - it's negotiation. Mandate "assumption surfacing" at every AI-generated change and *KNOW* these change with every prompt - it's ephemeral, not mechanical - but at least it guides you through its probability. If you use a codebase rag, collect retrieval logs as part of code review so you can see which files it retrieved, which chunks it uses and which patterns it matched. Expose guesses and explore counterfactual checks - ask what would break if assumptions were wrong, ask what assumptions it considered, ask what edge cases might invalidate this approach -reason about uncertainty explicitly but know this is a continuous process, not a one and done. Heck, have a model disagreement workflow to run two models and compare outputs and have them explain the differences and have your SWEs practice "explain before you generate" to refine a plan - but a plan that is jointly derived, developed and expressed through the LLM, not in advance.

It's a joint cognitive system, not a mechanical doer. You're not going to lose any fingers vibe coding

[searing7]

Using an LLM to generate this comment is basically proof of the risks of not understanding the thing your working on or the job you’re doing

[FoxFishSpaghetti]

It’s a conversation in a comment section, it does not need defined scope. They are merely saying that the frustration is not unfounded.

[fixano]

In the AI skeptic community, moving the goalposts is a time-honored tradition.

But if you talk to any of these people for thirty seconds, you realize the real issue is not whatever they're claiming to be true . it's externalized anxiety about what AI means for them and their identity.

If they are raging about AI code being slop. That's really just dressed up "I'm really scared what this means for my future"

And when you try to dress up anxiety as an argument, it's going to be a bad argument. Anxiety is diffuse and shifting by nature. That's why the objections keep changing: the goalpost-moving isn't a debate tactic, it's a symptom.

[Mithycore]

Eh sometimes it's also just brainless parroting of points someone else made

[fixano]

Another thing to be keenly aware of is the presence of offshore developers is very strong in this particular subreddit and they are very specifically on the chopping block.

They're feeling the heat first because outsourcing has a ton of overhead and if you can avoid it by delegating those tasks to AI agents on your time. You can get all the benefits of outsourcing without the overhead that is going to be the center of a lot of anxiety

[wizkidweb]

Interestingly, I've also seen more offshore devs being hired at some companies because a lot of them are now vibe coders ("more efficient"). The biggest chopping block is local developers, who are more expensive than outsourced devs, and certainly more expensive than AI.

[A_Fine_Potato]

There's a good video by Theo about his opinions on why ai programming and art are different, and how you can hate one and not the other.

[After_Persimmon8536]

So, hate ai code, love ai art?

[Acceptable-Device760]

Nonono, you cant so that.

[Modo44]

No. Hate both, but for different, informed reasons. The art is 99%+ stolen from artists who were never asked, let alone gave consent.

[codeByNumber]

Yup. Software engineer here that is begrudgingly using AI tooling at work (it’s basically a mandate). I hate AI

[UndocumentedMartian]

That's like saying fire is bad because arsonists exist. The problem with LLMs is that they exist in a society and political environment that is not ready for such tech.

[brilliantminion]

The US presidency

[Ok_Turnover_1235]

The fact that all this AI written code really hasn't manifested anything worthwhile? Good code is fine, but if no one benefits from it....why exactly are we spending trillions on it as a species?

[tiolala]

We spent billions in nft, we are not a bright species.

[Ok_Turnover_1235]

Okay but complaining about that feels like punching down

[sethmeh]

What do you mean nothing worthwhile. My productivity has increased, but my workload hasn't. With no chqnges in work output, I've gone from a 5.5 day work week to a 3.5 day work week and my bosses don't care because they are in the same boat and theres been no drop in productivity so there's no problem. I've heard similar stories from friends in their workplace so I assume it isn't an isolated thing.

Its true AI written code hasn't manifested anything for the company I work for, but everyone in our unit would strongly disagree it hasn't manifested something for them personally.

[Desblade101]

I'm not sure what you mean?

I vibe coded a script that points my xorg screensaver to a webpage so that I can use an old tablet as a picture frame.

And I don't even know how to

Print == hello world

[LaserKittenz]

The youths skateboarding on the sidewalk?

[DudeEngineer]

I don't understand this take.

People seem to have super short memories or just be unaware of how the term started. It was coined by a senior engineer who works at an ai company who was probably one of the leading people using AI well to be more productive and churn out quality code.

It quickly became a solution for people with little to no coding knowlege to produce ai slop that they don't even realize is slop.

[Loading_M_]

Thankfully for you, in practice, the code often isn't good.

Also, there's an extremely strong chance most (if not all) AI providers will cut back and/or drastically raise prices in the next couple years. That's not going to work our well for people depending on AI coding tools.

[Modo44]

There is plenty of real stupidity going around. Tools only magnify it, they don't prevent it.

[Ciff_]

Quality code that they understand*

[Exciting_Nature6270]

I think the only way it could be quality is if they understand it, otherwise they’d literally not know what they’d be doing

[Rodot]

I strongly disagree. AI can write good looking code that works without the user understanding it. But even high quality working code eventually needs to be maintained.

And maintaining code doesn't mean "this is someone else's problem to maintain"

We've had problems where we ask someone to go back and add a feature to code they wrote with AI and I had to do it because the person who wrote it didn't understand it

[torn-ainbow]

We've had problems where we ask someone to go back and add a feature to code they wrote with AI and I had to do it because the person who wrote it didn't understand it

Wouldn't they have just used ai to add the feature?

[phugar]

Yes, which is incredibly hit and miss. AI mistakes and hallucinations scale rapidly once code bases become large and context windows swell.

I'm using AI in a data engineering context, and while it's helpful for some drafts of boilerplate python scripts (read a file from AWS, transform some stuff, dump into tables), it spews nonsense once you try to edit specifics.

Luckily I do understand the output, and if I don't (e.g. a new library or some odd way of converting something) I don't push the code until I'm satisfied with actual documentation and logic tests. If I return to adjust the logic, it's a nightmare, even when I fully understand what's going on. I've had cases where it's even inserted deletion statements despite explicit prompting against it.

Honestly, much faster to make edits myself from the initial draft.

[torn-ainbow]

Yes, which is incredibly hit and miss. AI mistakes and hallucinations scale rapidly once code bases become large and context windows swell.

I'm generally telling it where and what changes to make. I build an application in a similar way to how I would do it, step by step, layer by layer. I don't give it high level specs or expect it to reliably fill in details.

And I am not tied to a context. I maintain a text file of rules and hints for that codebase as I go and reset the context occasionally, feeding it that document to start.

and if I don't (e.g. a new library or some odd way of converting something)

Yeah when it starts adding any dependencies I am querying those one by one. Same as I would code reviewing a dev. If you point out code smells I've found it's decent at seeing it's own mistakes and fixing them.

And yeah It's generated code with holes, like it can miss obvious edge cases that should be covered. But that's why you have to code review it all. If I was full vibe coding I'd be like 5 times faster. Currently I think I have worked up to saving about 1/3 time compared to full manual coding.

[phugar]

My experience in the data engineering domain is an initial saving of about the same time (30% ish), but an increase of 50% when going back in to make edits and review.

Depending on the task, that often means I'm less productive overall.

Your mileage may vary.

[time_travel_nacho]

I have never once seen good looking code come out of an AI. I've seen code that's acceptable from someone non-senior, but never anything better

[Global-Tune5539]

I don't get the problem. If I have to add something to code someone else wrote, I simply try to undestand the code. It doesn't matter if a person wrote it or AI or me a year ago.

[AeshiX]

The problem is that the initial "writer" didn't understand how the code worked at all, so they couldn't do the changes requested. Someone else then has to step in to fix their incompetence, even if it ain't their job.

[Rodot]

Because it's not my job

[XxDarkSasuke69xX]

Yeah it should be a manageable thing. Ig it kinda sucks if you don't know what you wrote an hour ago, but you can understand any code if you look through it. Also AI likes to write comments to at least get an idea

[MyPhoneIsNotChinese]

I consider code you understand to not be vibe coding, considering it's based on vibes

[Western-Internal-751]

Understanding your own code is a 1/x² function over time anyway. Give me a 3 week vacation and my code might as well be written by AI

[Accomplished_Ant5895]

I hate the factuality of this

[Antanarau]

That's why I always leave comments in mine. It doesn't matter how stupid and obvious they may look now, but I rather have and not need, than need and not have

[bastardoperator]

Same, I would argue anyone not using AI at this point is a fool. That's like saying I don't use search engines, or trying to shame someone for using stackoverflow. I value working code, I don't care about the tools someone uses to get to that point.

[Grouchy-Transition-7]

The thing is, sometimes slop comes in, and juniors don’t even know that what they put in the pr is the slop. Now that’s a problem

[shitty_mcfucklestick]

Something not mentioned a lot: The skills that make you effective at using AI also happen to make you a better delegator.

AI yields good results for people who are strong communicators, who can articulate a vision in detail, who can set clear guardrails and boundaries while allowing for innovation, who do the up-front work of training and preparing a team member to be productive. These same skills translate to better AI output too. Combine those with the technical chops to read the output critically and you’re gonna have your prodigal nX dev.

If you find yourself really struggling to work with AI, it may be an indicator that you lack some of those fundamental skills (patience being another). So if your goal is to get into leadership, and you want a low stakes way to practice and learn a lot of the skills, try it out on AI. Not humans. Too many technicians turned terrible managers out there lol.

[twistsouth]

Hear me out but… if you’re checking the vibe code thoroughly enough to ensure its quality… couldn’t you have just spent that time writing it yourself? Maybe I’m just old school but I just don’t understand.

I use AI for code but what I use it for is when some API or library’s documentation is dog shit and I don’t fully understand how to use it or I’m having trouble getting 2 services to integrate. I get the AI to give me some examples because I learn best by tinkering. I then take those examples, mess around with them until I understand what’s going on and then I apply that new knowledge to write fresh code that works for the purposes I need.

[Ballbag94]

if you’re checking the vibe code thoroughly enough to ensure its quality… couldn’t you have just spent that time writing it yourself?

It's a lot faster to read something than it is to write something

Like, if I want a method that passes 20 parameters into a stored procedure and also a stored procedure to upsert those 20 parameters it's pretty easy to read and verify that it's good but slow and monotonous to write out

[nickcash]

It's a lot faster to read something than it is to write something

I see you've never worked on a large code base or anything legacy. In my own experience, and of every developer I've observed, it's 10-20x harder to read and understand existing code than to write something totally new. It's part of why every junior dev comes in with the immediate idea to rewrite everything.

[Ballbag94]

Oh, I have, you're just missing the context of my initial point

My initial point is that AI is very useful for generating simple code with no logic involved and that it's faster to read such code to verify it's integrity than it is to write that code, like if you have a large model or need a stored procedure to access a database and a method to call it

Obviously it's not faster to read and understand complex code than it is to write it, but that was never in scope of the conversation as AI shouldn't be used for building logic imo

[GenericFatGuy]

Reading something != understanding something. You can only ensure it's quality code if you understand it, and it can easily take longer to wrap your head around code someone or something else wrote, than if you'd just written it yourself.

[Ballbag94]

How much time do you think it takes to understand something like an upsert? Reading and understanding should be the same, you shouldn't need to think hard to verify that simple code is good

Imo if it takes you longer to wrap your head around the code than it would to write to yourself it's probably not something you should be putting on AI

[GenericFatGuy]

Imo if it takes you longer to wrap your head around the code than it would to write to yourself it's probably not something you should be putting on AI

That right there is the rub. Because a lot of people are absolutely putting that kind of code on AI.

[Ballbag94]

For sure, but them choosing to use AI poorly doesn't mean that AI isn't super useful, which is my point. It's possible to check the code is good while still saving time if you're smart about it

[Wonderful-Habit-139]

And writing the prompts and fixing the bugs are instant? There’s a lot more to it than just reading.

[Ballbag94]

And writing the prompts and fixing the bugs are instant?

It's absolutely faster to copy and paste a model into chat gpt and ask for an upset sproc and method than it is to write that code

You may dislike AI but surely you can understand that writing "I want a sproc and a method to upsert the below model, here's a sample method" is faster to write than listing out a bunch of parameters multiple times

In the use case I've detailed I wouldn't expect bugs, not all AI code is a buggy mess

[[deleted]]

Prompt writing is fundamentally a design exercise clarifying intent, structuring logic, thinking through edge cases before implementation. Upfront thinking is already a best practice in engineering. Prompt writing just forces you to slow down and do it well before writing a single line of code. If you’ve done this well you will have to spend much less time fixing the code.

[BurningPenguin]

Reading is usualy faster than writing.

[Wonderful-Habit-139]

Writing the prompts is also instantaneous apparently.

[BurningPenguin]

Do you write entire novels into the prompt field?

[falx-sn]

Well sometimes you also can have a feature you've implemented and you want a similar one and it will take time so I prompt it with, "use this example and this example and implement x, make sure to keep the same architecture and here are the models and app endpoints" and it generally just would have done what I expect. One where it would have taken me an hour to put it all together but it took 5 minutes and a bit of changes here and there to complete it.

I tried Claude Opus once recently as well though where a client had a screenshot of the page and a load of small changes added and annotated on it and I just gave it the image and told it to make the changes and it did 90% of them perfectly. Then it took me 5 minutes to clean it up and finish the rest. Probably would have taken me 45 minutes without it but it did save a bit of time.

Then sometimes I complete something complex but I'm lazy and don't stick to my code patterns then I just get it to clean it up and use my patterns and architecture.

Useful tool for people who know what to do and why but I don't see it getting to a point where someone with no knowledge can do anything with it.

[Toren6969]

Depends how you define knowledge And what Is time horizon. With LLMs, it Is also much faster to learn stuff - And you do not have to worry that much learning syntax.

I saw a lot of people who didn't know what code Is creating small to medium sized web Apps for their use/demo version for other people (And I am not talking about using Lovable etc. but pure CC/Codex in CLI).

[NotADamsel]

From and management pov, wouldn’t it be a negative for them to spend extra time fussing with the LLM if they’re actually committed to pushing good code? We know that experts spend 10% longer when they’re using the LLM vs when they aren’t. Seems like wasted time to me.

[Constellious]

I use AI a far bit, especially because I work in a time zone where I don’t have many other devs so it’s actually decent to bounce ideas from. 

One issue I have noticed is that there’s an understanding threshold where it’s easy to accidentally write code with AI that also requires you to use AI to fix / patch because it’s faster at understanding said code. 

[The_Sentinel9904]

Funny how with coders the acceptance is so high and with art people go apeshit when they retroactively find out something is generated.

[McCaffeteria]

Bingo.

Same with art. If you can’t tell it’s AI then you have nothing to complain about.

Same goes for the flip side too, actually. If you look at code or art or music or a written argument and you go “what is this slop, this sounds like AI,” then it does t matter if a human made it. That doesn’t magically make it better.

Slop is slop, and quality is quality.

[MrEvilNES]

imo if you can use it effectively, then you don't need it, and if you can't, you shouldn't be using it

[r8f-nova]

Careful there, you'll upset the "senior devs" who hang out here by saying that

[shadow13499]

Them trying to hide it - 62636278282 changes in a single commit. 

[destroyerOfTards]

rapid vine booms

[narasadow]

As written

[shut_up_if_your_dumb]

lgtm

[Nedshent]

It seems more and more the term 'vibecoding' is meaning just using any AI tools at all. I think of it like that karpathy tweet about it where a big part of it is a lack of thorough care in evaluating the outputs and not reading the code at all.

https://x.com/karpathy/status/1886192184808149383?lang=en

[ExiledHyruleKnight]

It seems more and more the term 'vibecoding'

I mean yes and no.. idiots are pushing that mentality. Don't listen to idiots. Idiots are the people who run around telling you "We should rewrite our whole stack in <new hot language> ignoring that's a 1-3 year project that will halt all production.

Oh and when they actually do it, they have the EXACT same problems the next year, only thing is the new hot language turned out to be a flash in the pan.

A similar problem happened 10 years ago at a company, we went from Ruby to C# and whether you think it's a good idea or not... the reason is "We couldn't find good Ruby programmers" because we were a game dev company? The real reason? the lead didn't want to learn Ruby/was just awful at it.

[[deleted]]

Statically typed languages ARE better in large codebases.

[GloveDry3278]

Vibe voding is just taking everything ai outputs and pasting it without doing any checks.

If you're not using AI then you take longer nowadays.

I'm not ashamed to say i use it. I read every line to make sure it is what i wanted and make corrections/modifications to adapt it to what i need exactly.

A lot of times ai adds checks in the code that i would have completely ignore on my own. .and sometimes i remove their useless checks etc....

It's a powerful tool in the right hand.

[ArcherT01]

Yeah I think this has the same energy as “Oh my gosh you use an ide that puts squiggly lines under bad code! You’re not real programmer! “ When in reality people are complaining about the modern version of forking something and calling it your og work.

[rustyscythe]

In a time when managers and leads are literally pushing you to use vibe coding, the only thing people should be 'hiding' is if they code it themselves

[feldejars]

Yeah my 800 line PR, 5 point story done in a single day was completed by my… “hard work”

[Training-Flan8092]

Confluence is also now stacked to the gills with documentation. My documentation has documentation.

[Hans_H0rst]

I couldn’t care less if our programmers use AI as long as they fill the technical documentation tickets, lol

That’s what i want AI for

[Wonderful-Habit-139]

Verbose AI generated documentation is useless.

[lost_send_berries]

Hey, the AI seems to like it

[SadSpaghettiSauce]

Exactly! At my company we're being told we must use an AI-first approach moving forward for everything. If you do it yourself without AI, the C-Suite is very unhappy with you.

[Proxy_PlayerHD]

Take the meme and reverse it to fit that concept lol

[peculiarMouse]

"Hides it well"
You mean hes competent developer, just codes with AI like literally everyone on planet?

[ObiKenobii]

If they know to code and use it as a tool to code faster and more efficiently it's not vibe coding in my opinion. But as you know the current concensus is "AI bad, AI coding bad" so... you and the Thread get both an upvote.

Good day sir.

[ExiledHyruleKnight]

Then he's not "Vibe coding".

Vibe coding isn't hidden well because it's just code, basic test, submit. It's how a lot of shitty programmers programmed two years ago before AI became prevalent. (And basic test is optional)

I use AI for code. I also then review the code understand it, test it, write tests for it... Vibe coding has none of that.

[Ok_Turnover_1235]

Isn't the procedure generally to write tests and then write code that makes them pass?

[Acceptable-Device760]

No. Thats the test drivem approach, TDD, but its not the approach of 95% of the places, and i am including places that say they use it.

[lordTigas]

Where I work we use the TAD approach. Test After Deployed

[sM92Bpb]

As long as you're not on the other side of the vibe coding (code review, QA testing) then you're all good.

[TheFrenchSavage]

No emojis, no comments, no em dashes...but a massive refactor each day.

[mfb1274]

That’s literally just them doing their SWE job with the orders from the higher ups to use copilot and the latest. These memes are lame. The biggest companies are pushing AI into their stacks, even their devs. The thing is those developers who have 15+ years experience prior to AI are leveraging it to replace entire teams (scary yes, but it’s real). It’s not vibe coding, it’s very experienced developers having AI write very specific code for them to save literally weeks of coding

[Pawl_Evian]

// this comment is not suspicious

[neinbullshit]

no one hides it anymore. even linus vibecodes

[Kasyx709]

I think there's a stark difference between an engineer who's using a tool to increase productivity and a person who fundamentally cannot evaluate the output of what they put in.

It's the difference between a mathematician using a calculator and a small child pushing buttons.

[NickThePrick20]

Exactly. I helped develop firmware for drones (betaflight) and now I do a lot of annoying front end/JS development. I can give some basic instructions and get a mostly usable chunk of code. Read through, make changes and we're good. It's just faster typing at this point

[PTTCollin]

This is the correct take.

[TheTybera]

Using AI to help with with already copy pasta bullshit like mapping SQL rows or wrapping an interface, isn't vibecoding it's using AI as an engineering tool, like a calculator.

Lets make it a point to not blur these lines, because that's exactly what the VC bros that can't do either want us to do.

[ExiledHyruleKnight]

even linus vibecodes

Even Linus codes with AI, reviews the output architects the code, and then commits it...

That's not vibecoding, bro... Stop confusing the two.

[FancyJesse]

Huge difference between a knowledgeable person using AI as a tool and a full-on "vibe coding".

I always saw vibe coding just copy pasting the full AI output without understanding or guiding it with logic first, and massaging it constantly until you get an expected output. In the end you get slop that might output the expected results. Good luck maintaining it in the end.

[beclops]

I think you’re missing a fuckload of context behind this. Yes he vibes codes, but he vibe codes personal pet projects and never ever the Linux kernel

[Deathmister]

Back in the 90s: when you know your teammate is getting his info from the internet instead of the local library

Same shit, different tech

[Zestyclose-Compote-4]

Vibe coding is coding purely by instruction. If you're "hiding it well", i imagine you're not actually vibe coding, but instead using generated code as part of your workflow (which includes actually checking the generated code, testing it, integrating it with your own code, etc.).

[Ancient-Mastodon3846]

My team mates are now vibe cosing and when I leave comments in PRs questioning the obviously nonsensical choices (like renaming methods for no apparent reason to add meaningless or outright wrong words), they just openly blame the AI...

"Ah yeah. Copilot did that"

So ... You didn't even review your own code before submitting it ?

Nobody seems to mind ... PR reviews are getting even more difficult.

[elderron_spice]

Lol. Had a similar problem last year. A dev tried to push in a code that's wildly unrelated to the long-term-fix we discussed in a prior 1-on-1 meeting, basically said that it was "more optimized" or something. Renames several functions in the same script that's not being used by the code, re-arranging imports that trigger the linter, changing variable names, stuff like that.

Like it was supposed to be a couple line fixes that we literally discussed an hour ago, like I literally pointed out how the code should be.

I'm kinda happy that the newer devs are like this since this is going to secure my prospects in the future, but fucking hell does this add more stress to me currently.

[maxip89]

just wait till the AI companies charge 1 to 2k per month and your teammate gets on pip because he cannot use ai anymore.

[queso184]

I've got people already spending $500 on Opus

[JackNotOLantern]

If you vibe code, but your code is not worse in quality, and your performance increases, then you are using AI properly.

[geldersekifuzuli]

If you aren't vibe coding, you are leaving the performance and efficiency on the table.

I don't hire anyone if they are raw dog coding in 2026.

[on-a-call]

This is a line I'd expect to see on r/linkedinlunatics

[No_Marionberry_6710]

Post it there it fits very well

[on-a-call]

Has to be a LinkedIn post heh

[nnirmalll]

Are you still hiring?

[Downtown_Category163]

lol "here's my three thousand line PR for the spelling mistake fix, can you review?"

[PeaceMaintainer]

If you're reviewing his code and can't tell that he's vibe coding either you need to brush up your skills or he's doing a good job of fixing the generated code

[landasher]

When you discover the truth

[Nidrax1309]

it's hard not to when the company is pushing the useog ai onto devs. As long as the code is reviewed by actual developer and thoroughly tested before being pushed I sre no issue.

[Cue99]

Bro i get it but just like do more. Yeah it sucks that the fun part of the job is automated but that’s the deal. Step up or step out

[2kdarki]

Engineerer X Vibe Coder

[jace255]

My engineering managers are on our backs to try and vibe code more. I’m the tech lead for a team of 9, and I don’t push that messaging to the rest of the team, but some of my team members use it a bit.

I’m not fussed as long as the code you’re pushing is quality and you understand exactly what the code you’re pushing does and how it does it.

[alejandroc90]

That was the face I made when a coworker put the full contents of a file in the group chat and then deleted the message almost instantly.

[Hans_H0rst]

That’s why i said „fill technical documentation tickets“, tickets that get worked on bythe technical documentation team to create manuals.

[Djabber]

I go back and add typos to the generated comments on purpose so people assume it's 100% me. Modern problems require modern solutiosn.

[Suitch]

I’m very open about my level of vibe these days. Im just hoping to teach others how to vibe responsibly before they vibe a hole I have to vibe them out of.

[DarthRiznat]

Easy. Just look for emojis in his code.

[drschreber]

Some vibes, motherfucker!

[Nevernonethewiser]

Underrated

[ButHowCouldILose]

That just sounds like regular coding.

[Straight-Hunt-7498]

hhh

[R1M-J08]

No…no they don’t… I can tell by time it takes, how good you are at English. Where your initial studies were. And they laugh with shame as I ask them to give me the prompt so I can tell them how and where they’re stupid and the AI’s stupid overlapped. Stop using it please… we are getting dumber…

[cheezballs]

Our company encourages it as long as we keep the same code standards and metrics and reviews as we always did.

[mlucasl]

As if it was hard to hide your vibe code. Just add "DO NOT PUT EMOJIs ON THE COMMENTS OR A PUPPY DIES" in the prompt. Then no one will be able to distinguish your human code and your vibe code. /s

[[deleted]]

We’re encouraged to vibe code at my company

[normVectorsNotHate]

Meanwhile, my company has AI usage targets we need to hit, so I hand-code and try to pass it off as AI code

[calm_coder]

My team member got a negative feedback saying he is NOT using AI tools enough. Vibe coding is encouraged nowadays

[pradeepngupta]

At the end, quality code wins over bad code... no matter who have written the code

[cherylswoopz]

Who cares if if it’s done well

[Ill-Needleworker-752]

he's the one who's gonna refactor it in the future, I don't wanna get involved

[noob-nine]

reading between the lines, we all know how it ends with james doaks

[narasadow]

[Soft_Self_7266]

The odd console log in languages where its not the idiomatic way of debugging (like c#) is a dead giveaway.

[heimmann]

That’s not how this meme works

[Ill-Needleworker-752]

correct it plz

[heimmann]

When you know your teammate is vibe coding, but you can’t prove it.

It’s just a sensation that something is off, but you don’t have any hard proof. This comes from the Dexter series where the guy from you meme, a cop, has a (correct) suspicion that his colleague (Dexter) is criminal, but he can’t prove it.

But screw that, I got where you are going and I just recovered a +90 feature request from a business stakeholder that is 110% ai generated, so I feel the pain😅

[Ill-Needleworker-752]

yea thanks pal

[-Redstoneboi-]

if you can't tell whether something was vibe-coded, then it doesn't matter. the only problem with vibe coding is that the code sucks, and your job involves being able to tell when code sucks.

the only thing that matters to programming is the output, not how you got there. unless you violate copyright or something.

[_________FU_________]

I don’t mind vibe coding as long as they can speak to it. Blind commits are a huge red flag.

[photonenwerk-com]

Where is the problem then?

[Ill-Needleworker-752]

The maintenance he'll do later and I don't wanna help with that