I can certainly understand why one of your libraries was bothering you if you're merging 250,000 lines of AI generated code in a month.

now ask them to maintain the 250k lines, probably fine for rew more commits, but after that? Oh look, they left the company for the next ai-nonsense-startup.

They're going to take your job.

🤓📚🤚🦋 Is this an empathetic message?

I wonder why everyone hates CEOs

Translated:

High-schoolers are even cheaper and easier to exploit than new grads, and if I don't care if they know nothing as long as they can prop up our crappy app just long enough for me to the company, pocket a bunch of cash, get them all fired, and move on to my next "entrepreneurial" venture while preaching to people about being an innovator and a job creator. Maintenance is for whichever sucker ends up holding the shit bag, because I've got mine.

AI coding is just the latest spin on this age-old practice.

Omg his company sells one of those meeting notes bots

I'd bet everything I own that they leak sensitive information from some company within the next couple of months.

This product will 100% have more security holes than a sieve

... I'm starting to think I need to take up freelance pentesting

red flag number 1: measuring progress in lines of code

From my experience, being "good" at vibe coding is more about being unable to detect flaws in AI generated code rather than being able to code well. Add AI to the workflow of someone who actually understands scalability and maintenance and that won't be able to get past a couple functions before they drop the AI.

Also, assuming this kid gets weekends off, he would be writing 12k lines of code each day. I don't think the average programmer could even review that number of lines in a day, so there's likely no actual supervision for what the kid is feeding into the codebase.

I'd estimate within four months the project will be impenetrable, and they'll scrap the whole thing.

250,000 lines of brand new legacy code nobody has ever thought about or understood? Good luck with that.

"The worst possible situation is to have a non-programmer vibe code a large project that they intend to maintain. This would be the equivalent of giving a credit card to a child without first explaining the concept of debt.”" Vibe Code is Legacy Code

The crash out from AI when all this debt starts to catch up is going to be so massive, not just in terms of market losses for the rich, but literal lost ability to think critically among possibly an entire generation of people depending on how long the grifting can keep going.

Typical CEO thinking number of lines of code is the same as productivity. What was the functionality of those 250k lines? Do arithmetic ops between two ints? Compute if an int is even?

Programming is one of those skills and industries that is accessible enough that basically anyone can do it, but you will run into trouble later if you're doing anything serious without learning how to do it well. There are hundreds or thousands of ways to make something work, but if it's an unmaintainable mess or you don't even understand how it works, then we end up with our financial institutions running COBOL in 2025. Good luck when regulations change. Have fun when your operating system becomes unsupported and you have to replace the underlying dependencies. Hope your boss doesn't sue when they have to hire people to rewrite your hackjob.

And these were all already problems before AI code came onto the scene. We had the programming equivalent of script kiddies, people who would blindly copy and paste code from web searches without even reading the date or the comments saying "this is bad and this is why". But this probably makes it even easier to do, and possibly harder to spot. Combine this with how many universities don't even focus on lower-level languages so you get plenty of people who can't understand how to fix any of the trickier errors in their code. And that's not to say everyone has to be able to, but it's a problem when so few are able to. So these programmers are unlikely to know if the code has problems so long as it passes their tests, and unlikely to know how to fix those problems when they become clear.

Automation tools are good ideas for assisting and detecting possible mistakes. They're not good at generating that much code. In fact, that amount of code in that amount of time is suspicious, hinting that it's unlikely to be well-designed, maintainable or efficient.

I am old enough to remember ms frontpage. It could take a 50 line html page and make it 500 lines or more without changing the external appearance. Didn't make it better.

And how do you even explain the requirements of somethingvthat took that much code to implement to an AI. The context window is only so big.

If this is serious, that entire codebase is fucked

And I seriously don't trust ai with anything mildly more different in scope than what is always shown

250k lines of ai generated code means he didn't do anything

Lauri is a recent teenager-turned-CEO himself... and that "intern" is basically responsible for building Lauri's entire codebase. The whole service his "company" offers is what that teen bodged together in a month.

The fallback is gonna be hilarious, the codebase rewrote by AI? With basically no considerations of business need and system capacity?

I can't wait for the humiliating rollback

Waiting for the "our database got deleted, but I still love AI" post any day now.

Can we fast forward to the Hard Lessons part because it's going to be hilarious

lololoo expecting a follow up - everything is broken now need help post

Someone I know genuinely tried this in a test branch for a Blazor application developed at a university, and the AI introduced insanely hidden UI breaking bugs because it touched every single file and renamed variables to plural without correctly refactoring in every dependent file lmao.

AI is a powerful tool, but throwing an entire codebase at it is exactly how you nuke your development lol. Even the latest and greatest models can't handle complexity beyond a few thousand lines even with increased input limits. And if it's anything proprietary or even not well published, you're basically screwed.

The democratization of technology is a double-edged sword.

For every improvement in UX and lowering of a once impassible barrier of entry, we seem to inevitably gain a massive number of “eXpErTs” who can suddenly stand upon the now much lower skill floor.

Shortly thereafter seems to be a destruction of the general reliability of whatever field these “eXpErTs” flood - usually a field which used to be inherently cryptic and had complex prerequisites just to begin operation within, let alone master.

Like… it makes me almost miss when “using a computer” meant you had to understand how to browse a directory in DOS…

Because at least then you literally couldn’t begin to operate in the field unless you could wrap your head around understanding the basics of syntax.

Now you can just have an entire legion of dullards misspell or misspeak 30% of a malformed question to some random free LLM that still has trouble telling you “how many Rs are in the word strawberry,” and have it confidently fart back out a wrong answer that they will then copy-paste into a paper or article which will then be added to the pile of growing misinformation currently stuffing a frighteningly expanding part of our collective knowledge base.

There are two kinds of Linkedin posters - those who are open about being trolls and those who aren't.

I am trying to imagine how bad that library must have been before for this to be better.

"Doogie Howser here hasn't even had a day of med school, but thanks to AI he's writing 5000 drug prescriptions per day!"

"We literally found this homeless man on the street ranting about lizard people, and now thanks to AI he's the the biggest stud at the hedge fund, making hundreds of multi-billion dollar trades every day!"

"Betty here failed out of high school and can't even pronounce 'nuclear' properly, but thanks to AI she wrote the entire atomic power plant safety manual in a day."

"Would you believe that Fred is still in a coma? Yeah, doctors say he's 'in a persistent vegetative state' and 'never going to recover after that i-beam crushed his head', and 'what you people are doing is both cruel and insane'. But, we hooked DeepSeek up to his respirator and heart monitor and connected some black and red wires together and he's back to working as an air traffic controller!"

I'm shocked, shocked þat "CEO @ userjourneys.ai" would suggest AI is better þan human developers.

Shocked.

Are we just going to ignore that the guy posting this looks 14

A vibe coder not even out of high school replaced your entire codebase

👁️👄👁️

It fits that they don't mention testing or QA.

More lines != better code. Also, who tf wrote their libraries?