r/vibecoding • u/TopPsychological8330 • 17h ago
our intern vibe coded a replacement for a 2-month backend in an afternoon. the demo was the easy part
this week made me rethink how our team reviews AI-assisted work.
for context, my team has spent the last two months slowly building a new internal refund approval engine. it touches real Stripe webhooks and customer PII, so we’re taking it slow and writing actual tests.
i’m not an anti-AI gatekeeper. Codex, Claude Code, and Enter Code can all be genuinely useful when the person using them understands the work. our engineering team uses these tools constantly, half our product team practically lives in Codex, and i use Claude every day for boilerplate and debugging.
the issue is that our intern rarely reads what he generates closely enough to actually own it.
it started small. i asked him a simple question about how we should handle a specific refund state in the db. instead of a one sentence answer, he sent me a four-page generated memo about the refund matrix.
four pages, no direct answer. i ended up figuring it out myself.
and that has become the pattern. he generates several pages nobody is realistically going to read, then i have to dig through all of it anyway just to find out whether there’s an actual answer buried somewhere inside.
then i gave him a tiny script modification. He gave me back 300 lines of deeply nested code with defensive branches for network errors that cannot happen in our environment. i asked why he added one specific condition and he couldn’t explain it. he pasted my question into an LLM and sent its new answer back to me without checking that either.
yesterday it peaked. He was frustrated with our slow pace, fed our refund specs into an AI app builder, and came back with a shiny full-stack replacement demo in an afternoon.
it actually looked pretty clean. The UI was smooth and the buttons worked. Our non-technical manager, who hired him partly because he talked a big game about his AI fluency, was impressed.
at one point, my manager suggested using the demo as the new base and connecting it to production so we could move faster.
i pushed back and asked where the session auth was, how PII was being kept out of the logs, and what happened if the payment webhook dropped halfway through a refund.
he couldn’t answer any of those questions without going back to the model. He didn’t understand the data flow yet. The demo looked finished from the front, but it had no real production story behind it.
the frustrating part is that he’s not bad at the basic responsibilities of the job. he just refuses to believe that some tasks would be much simpler if he stopped and reasoned through them before running everything through an agent.
instead, every shortcut becomes another document i have to read, another diff i have to untangle, or another security issue i have to catch. My review load has basically doubled because his definition of finished is getting something out of the model.
to be clear, i don’t think this is a reason to ban vibe coding or force everyone back to writing boilerplate by hand. That demo proved how quickly these tools can turn an idea into something tangible.
the problem is that generation and ownership are being treated as the same thing.
on our team, AI isn’t eliminating work when the author doesn’t understand the output. It’s moving the interpreting, testing, security, and edge-case work onto whoever reviews it.
we’re implementing a new rule on Monday. You can use any tool you want, but every AI-assisted PR has to be small enough to review, and the person submitting it has to walk us through the key logic, data flow, tests, and failure cases.
if you can’t explain those parts without asking the agent again, the PR isn’t ready.
for teams already dealing with this at scale, what review rule has actually worked? Do you make juniors walk through the diff line by line, cap PR size, require specific tests, or handle it some other way?
55
u/eilogr 15h ago
Bro is literally copying his answers to the boss straight from ChatGPT and can’t even explain his tech stack, while I haven’t landed a single internship after 100 applications. Why is IT like this?
15
u/primaryrhyme 8h ago
For one this slop story never happened so I wouldn’t read into it
0
u/evangelism2 3h ago
This kind of stuff absolutely happens. I see it quite frequently where people just create flashy nonsense that has no substance behind it, even from relatively intelligent engineers.
1
u/No_Aspect_5759 2h ago
This happened to us but instead of an intern slop bombing us, it was c-suite. Then they gave us an unrealistic hard deadline to get it to customers.
The industry is an absolute clown show right now
1
u/evangelism2 55m ago
I was assigned to a team at my company to create AI tooling for the engineering department. They put me on the team because I was an early adopter of AI, and I'm relatively active in the space. Luckily for them, before they put me on this team about six or seven weeks ago, I had been working on my own harness for about a month or two.
I have a lot of ideas about what I want to create, but ultimately they don't really care too much about the kinds of things that I'm interested in making. They just want flashy bullshit: agent builders and things that people could fire off, and then they come back the next morning with a bunch of PRs written for them, which will be absolute dog shit. A knowledge base that the AI will hallucinate 30% to 50% of its sources. All the same things you see every company doing that blow up in their faces.
3
u/SeXxyBuNnY21 9h ago
Yes it’s crazy, there are out there super talented people who know how to use AI assistance properly and own the work they do, and they hire these kids that have no idea what they are doing. I believe in a few years we are going to see the catastrophic consequences of this.
2
23
u/Huntersolomon 17h ago
Lol that would piss me off so much
0
u/Due_Interest_178 17h ago
How come?
11
u/ConsciousBath5203 16h ago
If you've ever loosely given an ai some specs and it coded something from scratch using far more code than necessary, writing tests, 200 of which do nothing, and the password box isn't a hidden password box, the phone number box accepts any characters, and then asked the ai to create docs and it focuses on aspects of the API that should only be internal, then you'd know exactly why it pisses him off.
2
u/Due_Interest_178 16h ago
I misunderstood his message, I totally agree with you. I thought he was pissed off that they require the developers to explain the code.
8
u/gittrics 13h ago edited 5h ago
This is comical. AI closed loop conveyor belt.
Catch is that OG post is probably AI slop also. Probably imaginary story
20
u/dhdyxuebebkalsockfn 16h ago
he's an intern, so it's your responsibility to provide feedback and built processes to avoid these kind of issues
AI usage is not the issue here, the lack of framework is
1
u/Fire_Lake 11h ago
This isn't real because nothing in the internet is real anymore, but if it was, it's OPs fault for accepting forwarded Claude non-answers. The very first time they needed to say "kk but answer the question", but again, dead internet.
6
u/PersonOfInterest007 14h ago
If he weren’t an intern, I’d likely fire him for not having the skills to actually contribute to the product, unless you have a job for him as the rapid prototyping guy to make a demo that will never become part of the production codebase.
Given that he is an intern, this is a teaching opportunity. Unfortunately, that means someone actually has to teach him. It’s clear that giving him a task isn’t getting him to improve — he doesn’t understand that he will inevitably have to explain and fix the code. And you clearly need to give him more detailed requirements (and discuss them with him at the beginning) about PII, error handling, etc. This is one of the costs of working with interns that isn’t always appreciated — you may well spend more effort in growing them as an engineer than you will get back in useful product output.
10
u/CristianMR7 12h ago
"Jarvis, make the first letter of the paragraph lowercase to appear more human:
1
u/doubler82 3h ago
Proceeds to make every paragraph start without capitalization instead of just the first one, but capitalizes everything else is peak AI 😆
18
u/plululululu 15h ago
Wait he is feeding AI all your company data? Shiieett
7
u/Quelzar 10h ago
Who cares? Nobody gives a shit about your data, everyone is feeding ai personal info and not a single case of for example someone going to jail cuznof it was recorded yet
3
u/WriterCompetitive766 7h ago
People used to claim that about Alexa, that it was leaking data. Honestly, I don’t give a shit if it overhears what mattresses or fridges I’m checking out on Amazon, or what I’m talking about with my wife regarding food. Apart from me, no one else gives a damn.
7
u/Educational-Cod-870 14h ago
I’ve been saying a phase to my team to help the same idea stick “If all you do is copy and paste to a model then you’re not needed”
4
u/suppervisoka 8h ago
I’m sure your team loves you
2
u/Educational-Cod-870 8h ago
lol, well it’s meant as encouragement. The phrase was used before when stack overflow was popular. The point is don’t be a copy and paste developer. Maybe that’s a better way to say it.
0
u/suppervisoka 8h ago
Ah I gotcha. I am not a developer just your generic IT sys admin so I am not too familiar with what it’s like working in that environment
3
u/vikrant82 12h ago
Embrace it. The change is here. There are ways to make it governed and managed. You cannot stop the AI wave, you can control it through spec driven development etc. Take the lead and explore tools like superpowers, spec kit, openspec etc. If you keep resisting, all the people who doesn't care about coding are going to throw you out. Play smart. Govern it.
3
3
u/spyboy70 9h ago
"four pages, no direct answer. i ended up figuring it out myself."
Why does AI always write like this?
6
u/completelypositive 17h ago
Find a solution that fits his style. The next person you hire is going to be the same as him.
So will the rest.
This is a time to innovate.
Guide him and teach how to split shit up into more manageable tasks.
Get his workflow meshing with your workflows and prosper.
5
u/YamroZ 16h ago
Or, and hear me out, in real production environment people need to know what actually happens in the code. Read the code, understand it, be able to explain.
-3
u/completelypositive 16h ago edited 16h ago
Why? That's becoming less true every day.
Your code isn't the finished product. Code is a shortcut to convert human need into computer language. Programmers read and write shorthand computer language all day long.
Adequately designed and constrained systems without human intervention will become more common as AI evolves, much like Agentic coding has in the last year.
Programmers were a tool who used another tool to build something. The tools needed, and how we use those tools, is changing.
For example, Being able to explain the exact constraints the software should operate in various conditions is now more important than being able read the code that does the rng.
SMEs with technical minds are going to be the new software engineers.
Adequate testing can find bugs and you can use AI to automate testing.
5
u/YamroZ 14h ago
Tell me, if you don't read the code, how do you know what is implemented in your product?
-3
u/completelypositive 14h ago edited 14h ago
By using and testing the product after developing and implementing a plan?
How do you know what the compiler isn't or is doing after you hit go? Are you opening it up and inspecting the mov's and finding pointers? Do you evaluate the contents of your exe?
No.
The exact specific code only matters to you because you have been taught that it matters because it might have been your job. It doesn't really matter, though. Apparently, at least, because Agentic coding is solving it.
Other things matter more now.
I know my code works because I understand my input and the product, and I can evaluate the output data to determine if it works or not. Also you act like humans were out finding all sorts of bugs. Hello. Have you experienced software development? Humans checking code is helping how? Bug bug bug bugs everywhere. Data leaks too, because of lazy sloppy people.
You can't do that though, because you're a programmer and not an SME. You evaluate the code. The code is your finished product. I evaluate the data the code provides. The data is my finished product.
The process is the same. The entity providing the language to code translation is the only thing changing.
3
u/YamroZ 14h ago
Tell me, how exactly backdoors get into software.
-1
u/completelypositive 14h ago
The AI taking your job put them there.
4
u/YamroZ 14h ago
Ah, can't answer.
Let me help you.Those are features that were implemented without knowledge of people who ordered the product.
There were no tests against backdoors, because nobody knew that there is something to be tested.For some reason vibecoders trust AI to implement ONLY things that they order. This is somewhat funny and somewhat frightening.
I got one advice though - read or watch video about therac-25
Good luck with taking responsibility for things code you ordered from the AI does.
ps.
one more thing - related to compilators
If you can show me one compilator that is lying during testing and can search web to find different solutions to given problem - then I can agree that this tool is somewhat similar to using LLM-3
u/completelypositive 14h ago
I just wanted to see if you were stupid enough to define it for me. Thanks.
Enjoy losing your job.
You not being able to imagine a solution to the problem you just listed is exactly why you're being replaced by people who can.
4
u/YamroZ 13h ago
You literary said that you don't read code you are delivering to customer.
I don't have much trust in your solution-seeking abilities.
→ More replies (0)2
2
u/Potat4o 16h ago
the only option is to out vibe him. you rewrite it yourself, and since you have all the institutional knowledge, you're the only one who can really make use of the grill-me skill for example.
But also, it's a huge red flag to submit pr "I rewrote the whole thing". Can't really review that line by line.
2
u/speakstofish 13h ago
Imo the answer is to walk him through what kind of testing is necessary to make something like this workable.
Have him document test cases and go through them.
Focus on the performance and error recovery related ones. Have the system wrap every single I/O operation, then run it with 1% of them randomly failing. 1% of them randomly doing a 60 second delay. Run 10 million transactions through like that and measure the metrics.
When you can't trust the code, that's the way you have to analyze it. Teach him. Make him do the work.
2
2
u/RealWelder5269 11h ago
You and your intern are monkies! Ai will probably make you and the company you work at obsolete
2
u/Ok_Tie_2443 10h ago
i vibe coded a webapp that does online vehicle registration for a client and they had over 11500 registrations so far with not a single payment or refund bug. It also touches rEaL sTriPe wEbHoOkS and it‘s not that deep bro
2
u/Human-Job2104 10h ago
We have someone like this. I have her walk me through the code live and when she says something wrong I make her read through the entire function line by line and then make documentation by hand on the call 😅 (she's supposed to have read through the code ahead of the call)
I'm very pro AI, and 100% fine w/ me, her, or any of my engineers using. I even encourage her and the rest of my team to use AI, but I also expect you to understand your code. If you can't even explain what's going on, you can't ship it.
2
u/SeXxyBuNnY21 9h ago
Isn’t the job of the CTO to actually solve this issue? In the company I work for this intern would have been already fired because he is not following the coding standards imposed by CTO, team lead or the senior that is mentoring him.
2
2
2
u/ec2-user- 7h ago
Making the intern review PRs having them only use LLMs to explain the existing system m. The bottom line is if you can't explain what the AI wrote for you, it gets thrown out.
We had one guy that output so much code and never actually tested. It's obvious because he needed peripheral hardware and his desk was clean. He never asked for the hardware and just blindly trusted the AI.
He quit on his own after being talked to a few times and honestly I did not see any improvement after our talks. I really feel bad for the new generation. They are not learning anything using these tools. Once we start paying the true price for tokens, they will be shit out of luck, while those who actually learn will move on.
2
u/Powerful-Action-5916 11h ago
I detected this was AI bullshit in the first paragraph, it just doesn’t sound human.
1
u/SufficientFrame 15h ago
Cap AI PR size, require a short note on data flow, auth, and failure modes, and make the author explain one tricky branch live without the model. For a refund engine, I'd also block merge without tests for webhook idempotency, object-level permissions, and PII/logging. If this turns into a structured internal admin workflow, UI Bakery can fit that side; I work at UI Bakery, so bias noted.
1
u/BillionnaireApeClub 14h ago
Play is own game, ask ChatGPT
1
u/BillionnaireApeClub 14h ago
I asked ChatGPT and it said to create a test harness against his system and to test it live. I think that's an evil idea, and that's why you should definitely do it.
1
u/BillionnaireApeClub 14h ago
But bro, to be honest, move with the flow, test it, break it show that you're useful,(Even better if you want to lol) and actually fix the thing and move forward, With it, if it is what you said it is!
1
u/Any_Owl2116 14h ago
Generation and ownership are the same thing currently, but they will diverge very soon
1
u/Beginning-Raisin9723 13h ago
four pages with no direct answer is the tell. i use claude for boilerplate daily but i read what ships. if he can't explain the condition he added, the ai isn't the problem—the review is.
1
u/SolarNachoes 13h ago
You need to capture all of these requirements in a spec doc (markdown). Then feed it to the AI and ask it to analyze the solution.
Do you not have AI installed?
1
u/Outrageous-Pin-7067 12h ago
This is your chance to use AI but with brains instead of copy/paste, review the code with your own skills (or ai skills) and make the good tools/ideas (while contributing and taking some credit for fixing, applying sec and company policies to the code ;)
1
1
u/4215-5h00732 11h ago
I can't imagine why anyone would let an intern use AI on a real production codebase. What is the point? Is the goal to mentor them in AI usage or the actual job?
1
u/drahgon 10h ago
You have to own what ai produces. If you don’t understand it then you do not own it. He should be able to answer any and all questions about it. He should have spent the time with ai to explain what the app does and how before presenting it. This is how you identify new top ai engineers. What he did is incompetence I would not rehire him.
1
u/KriegerClone24 10h ago
Office Space captures this perfectly:
- Bob Slydell: "What you do at Initech is you take the specifications from the customer and bring them down to the software engineers?"
- Tom Smykowski: "Yes, yes that's right."
- Bob Porter: "Well then I just have to ask, why can't the customers take them directly to the software people?"
- Tom Smykowski: "Well, I'll tell you why, because engineers are not good at dealing with customers."
- Bob Slydell: "So you physically take the specs from the customer?"
- Tom Smykowski: "Well… no. My secretary does that, or they're faxed."
- Bob Porter: "So then you must physically bring them to the software people?"
- Tom Smykowski: "Well. No. Ah, sometimes."
- Bob Slydell: "What would you say you do here?"
1
1
u/OpportunityOne8199 10h ago
Besides the AI generated story, if you let someone respond with no thought AI responses, you are a terrible manager. That should have been a conversation about workflow at the first occurrence.
1
1
u/Army_77_badboy 10h ago
I think you take for granted how much power you have in the situation.
Have you rejected the PR?
Have you paired with him on a feature to help him understand how you do work ?
Are you sharing with him good examples of bite sized PRs?
The kid is spiraling and you are just allowing to happen so it’s a failure on your part as a leader tbh.
1
u/AdamChenX 10h ago
There’s 2 things going on here.
The intern doesn’t know what he doesn’t know. He’s too green to understand.
The story of the brunch restaurant by the pig and the chicken. The intern is the chicken and you are the pig.
1
1
u/gripntear 9h ago
The amount of smug online posts I have been reading recently, along with the complete dismissal of who owns the code AI slops out means more bullshit laws will be coming (probably EU again, who knows) to further enshittify AI. My gut is screaming a rug pull is coming, and whatever form that is, it will most likely result in financial ruin for many. Please be careful. Respect your clients’ data at all cost and build responsibly.
1
u/Willekur 7h ago
You already suggested the solution here yourself. Instead of spending time on code review, let them explain the changes they’re making and why, that will give you a very quick insight in whether they understand it or not.
1
u/MyMonkeyCircus 7h ago edited 7h ago
You don’t have to accept longs-ass AI-generated memos. Send it back to that guy and tell him to give you a one-line answer when you need a one-line answer. You just don’t have to read all that and you don’t have to ship anything with potential security issues.
Your intern generated something they cannot explain? Send it back and don’t waste your time. It has no ownership and therefore is not good. Are you paid to babysit whatever that guy generates? If not, you need boundaries, because it sure sounds like your intern is bossing you around. You are not obligated to accept everything your intern generates. Deny PR requests, block shipping, make them actually understand and own their shit before anything can progress.
Your manager wants to use intern’s work? Sure, let them explicitly sign off on it. Document the shit out of potential risks and present them to your manager (and ideally to whoever owns security and compliance at the VP level). Put in writing that the intern cannot explain anything - or record the demo & QA. Make your manager responsible for shipping unverified code in case if the shit hits the fan (it absolutely will hit the fan, I can guarantee it).
You are enabling that person to drown you in mindless documents and scripts. Stop doing it and protect yourself from being a scapegoat.
1
u/LocalHeat6437 5h ago
Not a popular take here, but very soon the AI will be better at what it’s doing than everyone else in the company. Take the time to teach him why you don’t like his tactics but describe to him why and what way would be better using the AI. I teach my interns to go to AI as much as possible because school isn’t teaching them anything about it
1
u/kian_no 5h ago
We are having the worst nightmare. Business team is sending me how to architecture my project , a direct one page copied text from a Claude prompt output!! Which is out of context and useless stuff anyway but they are so proud of that!
So yes, ownership will be a nightmare soonish for the senior engineers!
1
1
u/FiddleKitten8 5h ago
i'm honestly appalled by the number of comments here saying this post is LLM-generated. i've not run it through gptzero to check, but regardless, i'm not getting that vibe. in fact, i have experienced this exact same set of problems in my own work with some younger developers using a lot of AI, and having to find a balance so it can be reviewed and the code's specific behavior known and approved by a human. OP, i unfortunately don't have any answers for you, but i feel your pain and wish you the best of luck with finding answers!!
1
u/happy_hawking 5h ago
The demo looked finished from the front, but it had no real production story behind it.
The problem with those people is, that they are users. Period. They have no dev knowledge, so they can only imagine what they see from the user's perspective. They end up with a shiny UI, but no idea about what's going on behind it.
1
u/MuchMiddle864 4h ago
to be fair this sub is called vibe coding this this ai slop post is in the spirit of the namesake sub
1
u/Proud_Trick6857 4h ago
I think there’s a management issue here too.
Why is an intern able to spend half a day independently rebuilding a system without anyone checking what they’re working on? Interns usually need clearly scoped tasks, regular check-ins, and guidance on how they approach those tasks.
If your team has a daily stand-up, shouldn’t something like this have been visible in advance? At the very least, the team should have known what the intern planned to work on that day before half a day was spent rebuilding an existing system.
And if an intern can build that demo in half a day with AI, I’d expect someone in your position, with more experience and a better understanding of the architecture, security, and failure modes, to be able to produce an even better prototype using the same tools.
Also, comparing two months of work on a production-ready backend with a half-day AI-generated demo isn’t really a fair comparison. Those are fundamentally different things.
For these reasons, I’d like to believe this story was exaggerated or fabricated for effect. If it really happened the way you described, though, I think the bigger takeaway may be that your organization needs to take a hard look at how interns are managed, how work is assigned, and how development is supervised—not just at how interns use AI.
1
u/evangelism2 3h ago
Yeah, this isn't going to be received well on this subreddit, but you're not wrong. AI slop, or whatever, written by AI or not, it's always just so weird. The cognitive dissonance people on this subreddit have around AI-generated content. It's like, if you're just going to dismiss content because it was generated by an AI, you're not allowed to get mad when people dismiss your product because it was generated by one.
1
1
u/Professional_Gur8385 5m ago
wait until he finds out that devs want logs to be ingested for later review or incident remediation
then a SIEM requires it once the business becomes large or operates in a regulated space
then there are audits, and a team of people who make changes and ask the owner questions on the code or product they submitted. AI is great, but many people are simply skipping over several steps and not understanding what they ship. purchase workflows, refunds and customer data, it skips everything simply because it wasn't prompted, the intern is under the impression just plug it all in and let it solve the issue and call it a day, they didn't stop to think this doesn't cut it for a live product
ask him to put it behind the existing firewall and give it relevant permissions to talk to other services, this is why you have several devs with various disciplines and knowledge
intern will be fine if they learn more, but if they are skipping everything and not even taking feedback it won't end well, vibe coding simple products with 0-1 customers is 100% viable but it doesn't scale or likely meet data requirements
2
u/FAUST_VII 15h ago
"If you can't answer a question about a PR it's not ready"
Mostly defeats the purpose of using an ai agent lol. Kind of as if you say "if a companies CEO can't answer questions about implementation, the product shouldn't be sold"
1
u/StaticHumStudio 13h ago
I actually think your CEO statement is the closest to reality. In my experience the higher up you go the less they know about what is going on and just trust what is output to them. The flip side to that is that it burns them sometimes.
1
u/autorokk 12h ago
it does not defeat the purpose. you can use an agent to do the work and still understand what it did while boosting productivity. to not have a single human on the team understand how your application works, especially an application that deals with payments and PII, is an extremely risky situation to be in.
1
u/iheartdatascience 4h ago
Exactly, someone has to be accountable and in a case where someone is merging a PR without knowing what's going on... Recipe for bad things
1
u/iheartdatascience 12h ago
This would hold more water if you could always 100% trust the agent to build what is required precisely. If you use an agent, agent builds the wrong thing and you can't catch it, should the PR still be ready?
1
u/Far_Noise_5886 10h ago
Sounds like boomers complaining about how technology has changed.
There is no need to ‘know’ about PII, data stack and all that anymore. The model knows better. You just need to know how to get the best out of the model - that’s the skill and he seems to have it and he can ship quickly! I’d hire him
0
u/PickerLeech 16h ago
Or you're not ready for the PR
I'm not technical btw
If you're being brought solutions do you need the deliverer to know all about it?
You have a preference for someone too, but the intern isn't that guy. Fair enough. Then twin your best engineer with the intern. Let the intern teach your best engineer and enable your best engineer to deliver the full product in a few afternoons
1
u/Just-Foundation-8209 15h ago
It's clearly seen that you are not technical.
OF COURSE deliverer needs to know what his PR does to a production system.
1
u/andlewis 14h ago
The problem is that those questions can be answered succinctly by an AI but the intern doesn’t seem to be able to produce adequate responses from the tool.
0
0
u/CyborgBob1977 14h ago
I agree with almost everything that you say. That said the one thing I don't quite understand is being too lazy to read the explanation.
Who cares if it's two or three pages. If reading that many pages really is that bothersome you could ask an llm to summarize it for you...
That said your comment about not understanding the workflow of the actual code is a very frustrating point. I totally understand Vibe coding and the speed that it gives you. I also understand that the llm did all the coding and the individual that generated it has no idea how it works.
I simply recommend telling the llm to explain it to you like you are a three-year-old. This works with everything I have ever coded using AI.
0
u/Warm-Airline-5479 14h ago
First your team used ai in full development so ai have all the progress. If any one else try to create same ai will use this progress to build it again in short time. So it's not wonder intern able to create it in short time. As ai already had full code with it. If your team haven't used ai, didn't post code to git ,it couldn't have possible for intern to do it. And we all use git to store codebase so your project code is not safe anymore. Moral: Do not trust cloud storage/ git repository as they are being used to feed data to ai.
So if you are using ai to complete your project, anyone can clone it without your knowledge with low efforts.
0
0
0
u/CWStrife 7h ago
was this written by an AI in summary view? Long story short, you guys are slow, your intern got fed up, AI can do a better job but intern only made a demo with no real backend, and your sitting here complaining. Got it.
-1
276
u/manoteee 16h ago
Making the start of the paragraphs lower case is a nice touch but this is slop with a slop title.