r/ClaudeCode • Researcher • Apr 02 '26 • Popcorn 1 Bravo 1

Showcase Why vibe coded projects fail

Post image
3.5k Upvotes

654 comments sorted by

386

u/OperaRotas Apr 02 '26

Totally agree, but it's also kind of obvious.

207

u/EngineSubject5144 Apr 02 '26

It’s not obvious unfortunately for the AI pilled people

64

u/WestMatter Apr 02 '26

It'll become obvious to AI pilled people as soon as they try to make something bigger than a local prototype.

31

u/Additional_Storm_298 Apr 02 '26

Feel like the problem with that is you’ll eventually have AI Pilled people running AI Pilled companies funded by AI pilled investors and that’s where the problems come into play. When it starts to get bigger and the reach is broader, the dominos will start to fall harder.

Yada yada yada, bubble goes pop pop pop BOOM

→ More replies (14)

6

u/Madpony Apr 02 '26

"Why would I have to hire software engineers for my app? It's already 99% complete!"

→ More replies (10)

8

u/turbospeedsc Apr 02 '26 • Bravo

You can make great stuff vibecoding, but you do need to know what you are doing, at least have an idea.

Take a course like CS50 before you start and things will come out a lot better, since know you know what to request to the AI.

5

u/kknow Apr 02 '26

CS50 is far from enough to know how to scale and secure complete systems... The post from OP still fully applies.
This is still the thing about if you extend your knowledge you feel dumber and dumber because your horizon gets bigger and you see what is out there and what you don't know yet.
Every experienced dev went through this and it is never ending whenever you touch a new important concept.

→ More replies (1)
→ More replies (3)
→ More replies (11)
→ More replies (9)

41

u/caldazar24 Apr 02 '26

Honestly this missed the most important reason, which is that they haven't provided a real reason for anyone to use their chat app instead of Slack or Discord, or displayed any understanding of why people use those apps instead of one of hundreds other chat apps in the first place.

If they did have a compelling answer to why their chat app really was better, and they were able to convince even ten small-medium startups of 50-500 people each to drop Slack and use their app instead...the Claude Code app *probably* wouldn't *completely* fall over yet with that traffic, so long as they had tested it carefully. And even that little proof would result in venture capitalists lining up at that point to give you enough money to pay several $300K engineers to clean up your vibecoded mess.

It has always been the case, that version 1 of startup codebases were cranked out by mediocre engineers (by big tech standards), that the idea was compelling enough that a few people used it anyway, and then professionals were brought in to make it polished. Now this is just even more true. The idea guys can now just generate infinite prototypes, most people won't use any of them, there is still real engineering work to be done fixing the prototypes that actually take off.

→ More replies (2)

294

u/joheines Vibe Coder Apr 02 '26

99%+ of software projects are not planet-scale distributed systems, but stupid CRUD webapps with a handful of users

77

u/Estrava Apr 02 '26

levels.fyi was powered from a google spreadsheet and they have apparently ~20 full time employees. I think people here don't really understand you don't need perfect infrastructure or world class disruption in that space to have a successful app.

7

u/ComeOnIWantUsername Apr 03 '26

> I think people here don't really understand you don't need perfect infrastructure or world class disruption in that space to have a successful app.

Yes, this is a lot of people don't understand. There are lots of projects trying to get perfect from day 1, spending months to create some custom engine, notifications system or anything, only to be beaten by someone who glued few services during a weekend.

There is a great talk about it, unfortunately in Polish, but YT dubbing (even though it's shitty) is there: https://www.youtube.com/watch?v=dYzfArtf7qU

7

u/No_Point_1254 Apr 05 '26

This touches the key point I think.

Good developers can understand complex systems.

Great developers understand that most of the time, you don't need complex systems.

You need it to be exactly complex enough to be adaptable if requirements change and at the same time so simple that barely any IQ is needed to actually maintain them.

→ More replies (1)
→ More replies (2)

8

u/tzaeru Apr 02 '26 edited Apr 02 '26

Most chat/VoIP/screen sharing services people actually do use tho, do require some sort of system distribution.

Nowadays when the need is not just the sharing of text, but the sharing of images, doing voice calls, the passing of notifications, avatar updates, emoji lists, etc, you do hit processing and bandwidth limitations on a monolithic system quite early.

If you want to literally be a replacement for Slack or Discord, then the whole project hinges on being able to get that one surge in users that it then continues riding until it breaches a critical threshold in users. Discord reached its first million users in less than a year. If you somehow reach 50 000 users and then your servers start dying and notifications don't work because stuff crashes under the load and the bandwidths go to zero for video streams and VoIP, your app is essentially dead. You have hours to get it to work again, maybe days, but certainly not weeks, or you risk the early users turning away because they don't deem your app stable enough.

8

u/MillenialBoomer89 Apr 02 '26

99% of projects maybe. But 99% of actual usage is on 1% of those CRUD apps where what OP mentions actually matters. See I can make up stats too

→ More replies (3)

43

u/FatefulDonkey Apr 02 '26

That's also why 99.99% of projects fail to make any money.

72

u/OverSoft Apr 02 '26

LOL, the simple CRUD based applications with a handful of users are often the best earning applications in the B2B market.

→ More replies (18)

12

u/Left_Somewhere_4188 Apr 02 '26

Nonsense. I used to make money creating shitty e-commerce sites in about a week. I always had WAY MORE offers than I had time to do them. This is something that is completely obsolete now. Simple projects make money, that's how the the vast majority of software developers have made money outside of companies, simple projects.

Not to mention in-house projects...

Or for example, a friend owns a drilling company, they have software needs that aren't met by software on the market, previously they'd pay someone who understands software and geology and pay them a truckload of money, now it's an easy vibe codeable project.

8

u/akera099 Apr 02 '26

There's money to be made with vibe coding, but I'm pretty confident that the vast majority of usage will come closer to what people used Microsoft Access for : user debuggable apps to serve as simple internal tools. 

→ More replies (2)

6

u/ENTclothingRussell Apr 03 '26

Correlation isn't causation. Projects fail to make money because they don't solve a real problem, can't acquire customers, or run out of runway. Not because they're CRUDs.

Some of the most profitable software ever written is a boring CRUD with good distribution.

→ More replies (2)
→ More replies (31)

4

u/AdmiralSWE Apr 02 '26

Uhhh almost all software projects at almost all F500 are large scale bespoke applications

13

u/who_am_i_to_say_so Apr 02 '26

I’ve got news: nobody cares about your architecture either. It’s marketing that is the key.

Shoot I have some crud apps where 1000 users would make me $500k a year in revenue. I’m not even aiming that high- getting 1000 users is a battle in itself. Marketing is hard.

→ More replies (20)

2

u/Tech-Grandpa Apr 02 '26

Give examples of this 99%,also, where did that number come from?

→ More replies (23)

40

u/AJGrayTay 🔆 Max 20 Apr 02 '26

I've been vibe-coding my project for ten months - I'm not a dev, I'm a security architect.

Once you realize that vibecoding isn't a single one-and-done prompt, but an iterative planning process where you need to carefully define what you need from an architectural and product perspective, and constantly check assumptions and blind spots, you can build what you want. Just don't think it'll happen in a weekend. The agents are good, but they can't read your mind just yet.

5

u/octotendrilpuppet Apr 03 '26

And recursively ask your agents to keep inching up the software product to world-class security standards if need be. There is NO barrier in principle to making what you want in the software dev world now - dev normies be like "it's cute you made a proto, but you don't understand how hard it is to scale" ...bruh, I had to first make the product exist (something you suckers wouldn't touch without a 100k upfront capex). If I have the drive to make something happen, I can also muster up the drive to make it world-class.

→ More replies (2)

3

u/poj4y Apr 05 '26

Yeah this. I’m a UX Engineer so I do some coding at work but wanted to give Claude and vibe coding a try with a relatively simple project. It’s been about a week and I still got plenty left to do. I’m being very intentional with each feature at we create it to make sure my end project is satisfactory.

→ More replies (7)

132

u/_laoc00n_ Apr 02 '26 edited Apr 02 '26 • Bravo

The poster is misunderstanding why the ability to create apps that generally replicate the functionality of expensive SaaS products is potentially a SaaS killer. If you’re building a Slack or Discord replacement app for your organization, you don’t have to worry about scaling to 50k users for almost any company. A few dozen or a few hundred, which is relatively trivial. You aren’t building Slack for everyone, you’re building it for you. If 50% of orgs can do this who currently own Slack licenses, then Slack is at risk of losing half their customers.

Edit: Most of the replies are still missing the point. You are continuing to think if things in terms of the current paradigm. No one needs to clone Slack, they need to have a way to share files with each other internally, send messages, and create groups where multiple members can chat. They don’t need a canvas or a voice capability or workflows necessarily. If you are fully utilizing Slack and all of its features, that’s probably too big a lift for most companies. But most companies aren’t really doing that, they are using it in the most basic way possible and the rest is bloat for them. You’re also overestimating the time required to manage something like the kind of tool I’m talking about. It’s not necessarily set it and forget it but it’s not something that would require a full time engineer to maintain, they’d barely ever be working. There are people doing harder and more interesting things than they’ve done before because the barriers for doing so are lowering. There’s an unsurprising amount of gate keeping being done by those who have had these roles for years because there’s an inflated sense of intelligence and skill that they don’t want to admit has been partially trivialized. Better engineers will build better tools. But for most tools, just being good enough is enough and they can be created by a much larger pool of people.

20

u/[deleted] Apr 02 '26

No one needs to clone Slack, they need to have a way to share files with each other internally, send messages, and create groups where multiple members can chat.

Exactly this. I work for a small town utility. Enterprise work order management apps are $75k to purchase and $10k+ annually for licensing. I used claude code to build a stripped-down replica for my 10 maintenance guys, managed to deploy it to the web so they can use it on their phones, and built it to serve precisely the needs of my department. It's been working flawlessly for 6 weeks, and all it cost me was a $20 anthropic subscription and about 10 days of my time working on it for a few hours a day (which was fun!). I didn't "kill" one of the companies that makes these apps, but i sure as hell wasn't going to pay $75k for one, but now i have something that works great for my workers. All-or-nothing thinkers like OP are misunderstanding the value and purpose of vibe coded apps.

6

u/ChemicalBankBurned Apr 02 '26

Cool. Mind sharing the endpoints? Or have they been ddosed to death already?

7

u/[deleted] Apr 02 '26 edited Apr 02 '26

no, it hasn't yet.

ETA: the app sits behind cloud run and requires our org's google logins to access it. Worst case scenario some malicious bot finds my URL and gets spun away because of the google login, but if it's super persistent, cloud run auto scales. If something really bad happens I have a budget action that shuts it down after a certain dollar amount, but it's an internal app and none of that is a.) likely, or b.) all that consequential.

→ More replies (7)

4

u/eboran123 Apr 02 '26

I'm sorry but this just sounds like you were oversold something. If you could vibecode it, then there was probably an open source or much cheaper version already out there somewhere.

→ More replies (1)
→ More replies (2)

30

u/p1zza_dog Apr 02 '26

yeah, but are those licenses more expensive than an engineer's salary to maintain and debug them? is that really what a business wants to spend its money on rather than core business problems?

13

u/Left_Somewhere_4188 Apr 02 '26

Yeah I highly fucking doubt it. Besides it won't just be one engineer, there will probably have to be a product manager, and compliance involved as well, there's bunch of non-software related issues that Slack solves for you, and it does not cost that much... And when inevitable bugs creep up...

Replacing a service that is complex enough to have thousands of employees behind it, doesn't sound like a good idea for 99.9999% of the tech companies in the world.

3

u/GrapefruitFriendly70 Apr 02 '26

My last employer took the opposite approach. The development team focused on work that substantially improved profitability, replacing internal services with off-the-shelf solutions whenever possible.

→ More replies (2)

20

u/Vnxei Apr 02 '26

This sounds a lot like the new "my nephew could make the website for us over the weekend", tbh. Sometimes that works, but more often, you'll end up wishing you'd paid a professional for a version that works. 

Saving money on SaaS licenses sounds great until you realize how much stupid minutiae you're dealing with rather than your actual job. 

10

u/bamboozled_bubbles Apr 02 '26

Nailed it! Software stocks trade at a >20x multiples because of EXPECTED growth in users, margin, revenue. Nobody is expecting an enterprise level organization to rip and replace a legacy SaaS for vibe-coded slop. The real danger is if the average SMB business is willing to test out a vibe-coded app that only needs to support their 50-100 employees, rather than paying a SaaS for those 50-100 licenses - that completely changes the deal flow for SaaS. Worst case scenario, SaaS companies see their SMB business disappear overnight. Best case scenario, SaaS companies lose margin on SMB business because their competitive moat is narrowed.

→ More replies (6)

14

u/AncientAspargus Apr 02 '26

you're missing the point here. It's not like scalability is the only aspect a vibe-coded app is lacking.
Run your internal Slack clone for a while, and you'll notice this feature missing, that message not arriving, here's a bug, there's something that works differently from this other thing, here's an API endpoint to return all user passwords the agent added for debugging but forgot to remove… It's a never-ending stream of work. Not to forget the security and dependency updates you ought to take care of, the databases to set up and secure, and a ton of other things you didn't think about.

→ More replies (16)

4

u/AgeMysterious123 Apr 02 '26

You see the light. :)

We’re not there yet, but that’s where we’re heading. I was looking for a tool last night for personal use. I found one, closed source, they wanted $45 for a forever license. Totally reasonable. I told Claude I wanted to replicate it, the feature tweaks I wanted, and a few other things I didn’t need. I now have a version running locally that works for me. Does it have bugs? Not yet, but they’ll be easily squashed if they pop up.

I talked with an Account Manager at a compliance firm yesterday who did something very similar for her daily task scheduling tools. She is not a developer. She said there’s a few issues, but better than what she had before. She was happy with it.

Does this type of software kill all SaaS? Of course not. Can it easily replace something like JIRA for a company of 12 people? Absolutely.

The industry is not moving to “I vibe coded the next multi-billion dollar startup”, but it is moving to hyper localized tools that were previously handled by startups.

→ More replies (1)

3

u/markvii_dev Apr 02 '26 edited Apr 02 '26

Yes bro an enterprise company that sells financial services wants to create and maintain its own communications application - why stop there? Surely the company wants to create and maintain all of its external vendor dependencies. It's easy right?, uptime of 98% is good enough for all internal services.

Excellent business strategy cotton, let's see how it plays out.

Edit: fucking lmao I just seen the breakdown of the Claude code source code. And this guy thinks an actual SAAS with 10x the entropy would be viable. Brother...that skill ceiling is rough.

7

u/DangerousSetOfBewbs Apr 02 '26

Bingo. Slack is literally losing their moat every release or upgrade of claude etc

2

u/Tech-Grandpa Apr 02 '26

Just about every app on the market already had a foss version of it, yet businesses still pay for licenses and support.  Why?

2

u/ThreeDMK Apr 02 '26

You somewhat had me until you mentioned gatekeeping. I honestly don't believe any of my industry experience has been trivialized at all. The only thing that has changed with the introduction to these types of tools is that I can now execute faster than I did before. If anything, it gives me more people to interact with because the bar has been pretty high getting into this type of development.

I would honestly say it's the inverse, as the OP shows. People who have never built applications are now empowered to create tools without understanding the impact these tools have on their companies. This inflated sense of ego will cause even more problems. Especially when people try to warn them about possible issues and they are ignored because apparently our experience or knowledge doesn't matter.

Take a slack clone for instance. Do you think a junior dev building a tool is going to consider security, pen testing, securing endpoints, before tossing their tool up on AWS without properly locking it down? Using home grown tools like this to replace core pieces of communications infrastructure is a recipe for disaster. This is how data breaches happen.

I have zero worry about this being a SaaS killer from the perspective of people building their own tools. What this will do though is see the introduction of more robust communication tools built by development teams that leverage this technology to compete against them. It may also make Slack itself better a stool since the engineers behind the project now have the ability to iterate and test at scales they never could before.

2

u/round-earth-theory Apr 02 '26

Scale becomes an issue faster than you think it would. We recently gave up on our chat app backend because the scale issue was becoming a growing nightmare and no one wanted to make this their full time job. We went to a backend provider and just paid for it. Still get the benefits of our custom solution without too much cost but it's use based so we could end up needing to change gears again in the future if things keep going.

2

u/diavolomaestro Apr 02 '26

I think the applicable business case is: “what SaaS products are we paying a lot for without getting tons of value?” That could include: you need a niche feature that bumps you into a new tier (and can’t negotiate a discount), you need heavy customization to get the data in or out of your system (ideally you haven’t already done this - let’s say you’re scaling up), or you need to build lots of workflows within the software, or you have to pay per seat for every employee even though 99% of employees just use one tiny feature.

I guess the last one is: the software basically is your business. In this case you’re a medium size company that has built its entire operations in and around a product built by another company. Think an accounting firm using a client management software, or a freight broker using a transportation management system. Every company faces build/buy decisions and I think these new tools push more companies toward the “build” route earlier

2

u/Slight_Strength_1717 Apr 03 '26

There are literally good open-source, self-hosted options for basically any SaaS already. You don't need to roll your own, that's insane. But even given that, the majority of companies still choose Saas because the complexity of self-hosted isn't worth it.

→ More replies (11)

42

u/robhaswell Apr 02 '26

I was handed a project from a junior developer (hand coded I should add) that included a docker-compose.yml file with all markup to make it run for local dev. This needed deploying to our internal K8S cluster. Because this is an internal tool, I decided to experiment with giving Claude limited access to our GitOps installation (verifying each command it wanted to run) and asked it to deploy the app.

It did an amazingly good job, better than I would have done, properly following all devops best practices that I tend to omit for internal stuff. Very impressive.

So yeah I'm in the "this post is correct but potentially not for long" camp.

19

u/gothamtommy Apr 02 '26

The key there is you knew what was needed. That could be "update this yaml to work on prod" or "this is not working for prod" but the result may be the same.

I think the difference is knowing architecture and being able to tell an AI tool like CC how you want to scale. For instance, I can tell CC I want to add auth to my app, and it may create its own auth system or use basic http auth while I may know to use something like Cognito and ask it to integrate with that for scale.

11

u/Spinal1128 Apr 02 '26

I can tell CC I want to add auth to my app, and it may create its own auth system or use basic http auth while I may know to use something like Cognito and ask it to integrate with that for scale.

Actually directly have experience with this. Except we needed to use internal tooling that handles auth and (obviously) claude didn't know that and kept trying to use basic auth even when told what the deal was.

The more "generic" the thing you need the better AI is at doing it, as the "customization" goes up, the more you have to intervene and guide it. Hence why there is so much "it got me 80% there!" Because 80% of most projects is pretty generic or follows conventions that are already there to use as examples.

I don't think that should be a very controversial take tbh.

→ More replies (1)
→ More replies (19)
→ More replies (6)

29

u/siberianmi Apr 02 '26

It's not wrong, but also wrong at the same time.

If a Vibe coded $100 worth of tokens slack works fine for your 10 person team, you'll never have to address any of those scaling issues.

8

u/LowFruit25 Apr 02 '26

But why tho?

You have your own product or service to build but now every company is gonna do 10x the work just to save 200 bucks a month on all SaaS?

Don’t run a company if you’re scrupulous about that kind of money.

4

u/TracePoland Apr 02 '26

It’s the fallacy that your time is free (or that Claude is free). The obvious outcome of this being undertaken every time is that as people use it, bug reports and feature requests flood in and now you have 1 person full time working on it, which is guess what - like $150k+/year. 99% of SaaS licences your small enterprise buys will be nowhere near that sum.

→ More replies (10)

6

u/cherya 🔆 Max 100 Apr 02 '26

But why the fuck you need an own slack for team of 10?

→ More replies (17)
→ More replies (3)

8

u/joban222 Apr 02 '26

Now I can just paste this screenshot into Claude code to improve my chat app. Thanks OP.

→ More replies (2)

12

u/Inside-Yak-8815 Apr 02 '26

He sounds so butthurt that AI will be laying him off soon.

1

u/Complete-Sea6655 Researcher Apr 02 '26

Source of the tweet was ijustvibecodedthis.com btw

5

u/PrimaryAbility9 Apr 02 '26

yes, building the functIonal prototype is only first part of the game. BUT i don't want this to ever discourage the people/vibecoders who are newly entering into software. in the same way that vibecoders learned how to build prototypes, vibecoders can also learn what it means to deploy and manage things in production. it's all part of the learning journey.

and besides, ai is so good now (and it's still due for another exponential jump!). ask or knock and you shall receive.

4

u/blaster151 Apr 02 '26

Funny, I enjoyed this and agree. Are we gatekeeping a little too much though? Technically if you approach your LLM conversationally and even if you don't know what questions to ask, you'll get far if you’re willing to ask, "What are the questions I should be asking?" There's no reason that a top-tier model can't walk you through a slow, dawning understanding of what it means to scale and to become production hardened while doing almost all of that work for you.

4

u/agrophobe Apr 02 '26 edited Apr 03 '26

My brothers in crime. Please don't fall for this. Just see how much factorio this is.
bro does a thing. It fails, he learn about all the things, or maybe half, the pic talks about. He adapt, he rebuild.

I'm myself coming from painting, but I'm legit digging astrophysical simulation and MHD. Do you think I get it? I never did math since I was 16 yrs. But will I get it? Yes I will.

My 2 cents? A lot of people here have been living life in a silo, only working on one aspect of a skill.

But as an artist, I'm trained to suck multiple things at a time.

No, not in that way.

3

u/Agile-Expression-161 Apr 03 '26

my brother what makes you think developers aren't trained to suck multiple things at a time 🤣🤣🤣

I have sucked both at backend, frontend, and behind Wendys

→ More replies (1)

11

u/hammackj Apr 02 '26

I run my own stacks locally and I’ve replaced Trello / private github / QuickBooks and some other junk saving me 1000+ a year in expenses. I’ve been coding for 30 years and being able to say Claude build me my own shit and an hour later I have it working locally(I hate cloud) which is perfect for these dumb SAAS shit tier sub models. Would I raw dog these apps on the internet obviously not but for my own internal use to cut expenses yeah it’s fine. In 1 month of Claude I’ve saved over 1k in yearly SAAS expense.

The quickbooks one is great I have all the features I use and the same export for my CPA.

Claude also helped me move all my YouTube editing and thumbnail creation to open source software to remove another 700 in adobe expenses.

Sure today you are not building a discord replacement but eventually it will.

2

u/ChemicalBankBurned Apr 02 '26

There are already numerous well tested open source alternatives available for almost all SaaS apps. Guess everyone just forgot the saying “don’t reinvent the wheel”

→ More replies (5)
→ More replies (12)

27

u/BarnyardBilly Apr 02 '26

You can almost taste the salt through the screen.

16

u/raholl Apr 02 '26

yea... salt of vibecoder's tears realizing the truth behind the scene :D

6

u/Dangerous_Bus_6699 Apr 02 '26

Lol it's so amusing to me to see professionals rage. I would be welcoming every AI slop in the world. If what they're saying is true, that would make your job even more secure, increase market competition for your knowledge, people would be beginning you to help them scale.... But no one gives a fuck about you anymore. They'll wait until until the next model can do more, rinse and repeat.

→ More replies (6)
→ More replies (4)

3

u/EzioO14 Apr 02 '26

well it would be same for a solo developer starting his first project... you learn along the way

3

u/notmsndotcom Apr 02 '26

Straw man argument. Most vibe coders don’t actually think their 1 month MVP is a slack killer. Their MVP is something that they can go out and start validating, selling, and doubling down.

3

u/MalaxesBaker Apr 02 '26

Most of this is true but the post is also kind of elitist. Not every app needs to scale like Slack to generate business value.

3

u/erbuka Apr 02 '26

Let them leave the dream.

I remember when in mid 2000s professional cameras became cheap enough that normal people could afford them.
All of a sudden, everyone was a "Photographer". Same thing here, people that lack skill and knowledge now pretend to be software engineers, LOL. So by extension, since I can use CAD quite well, I can be be an architect, right?

They say now the focus is not on code, but on architecture, prompt and orchestration... Yes, there's some truth in that, but it is IMPLIED that you have knowledge about software architecture and tech stack.

2

u/cleverhoods Apr 02 '26

"just need to adjust a few things and it's ready to deploy"

This probably the most common lie that we tell ourselves ... vibe coding or not.

2

u/Shoemugscale Apr 02 '26

I just rewired my house!

Suck-it, electricians!

-House burns down from electrical fire..

Everything looks simple on the surface, but, it takes years of experience to properly architect a backend, account for scale and edge cases etc.

This is also why, in the corp world we are seeing the junior roles going away, in favor of the seasoned dev who can now just direct the AI like a junior (or better) to build the system. Its a scarry gap because, those seniors and higher are going to retire sooooo..

2

u/tzaeru Apr 02 '26

Pffh IRC handled tens of thousands of connections per server and hundreds of thousands of total users across the network no problem already back in the early 00s!

But yeah. Much fun:

- File upload. And there will be people who essentially treat the service as their personal photo backup. And there will be bots that try to use the service for general file sharing.

- Copyrights and other legal requirements. If you store data like images, video, archive files, etc, someone will upload something illegal. Not a problem in the small scale. But once someone dumps a terabyte of child porn on your servers, it's also your problem under most jurisdictions.

- Voice chat. Less trivial than one might first think (though decent libraries and protocols exist for it, that you could maybe staple in to your product). Buffering issues, latency issues, quality issues. Takes a fair bit of bandwidth.

- Video streaming. Same as above except it needs 50x more bandwidth.

- And indeed; a lot of edge cases from eventual consistency, data races, order of processing things. Someone deletes something while someone else is accessing it, someone picks a nick that is not currently reserved and the UI shows it as OK, but user creation fails because it got reserved in-between, you have to handle which messages intended for them each user has seen and no, you can't just let the client deal with it. etc, etc.

2

u/hghg432 Apr 02 '26

Try shipping your one shot garbage code into prod and see what happens

2

u/Prestigious_Lab_1033 Apr 02 '26

Building aí software is a big responsibility you talking about lifes not numbers, same principles as building a house.. how much pressure can the foundation handle tons of data without collapsing?

2

u/robonova-1 Apr 02 '26

There is a HUGE different between prototyping something as a POC and putting something in production. If someone doesn't understand this difference they shouldn't be vibe coding anything until they have a grasp of insecure software and pasting links to their GH repos. That's why actual SWEs scoff at vibe coded projects. Not to mention we spent years of education and experience learning things that vibe coders think they can simply reproduce with a few prompts without understanding a single line of what they are generating.

2

u/PhallicPorsche Apr 02 '26

I agree with the premise but slack is also garbage

2

u/ybcurious93 Apr 02 '26

Says the dev who imports random packages without knowing everything within them lol

Isn’t this just another layer of abstraction? The same way for many languages you can just use a function because someone else built everything for it to run ?

Yes it’s not perfect and scale is kinda scary but within 5 years i can see this getting to the point of being able to one shot slightly beyond using locally 

2

u/daniele_dll Apr 02 '26

The title is very misleading!

The issue is not the vibe project per se but the standalone vibe engineer:

  • if you are a slack engineer with 10 plus years (which aren't really "enough" for the stuff being discussed in the screen... I am curious to see a database with eventual consistency written by someone with only 10 years of experience that works... written without the AI of course!) you can still drive AI effectively

  • if you are not but work in an organized company you will be working along people with seniority that know what they are doing (at least more than the junior)

I haven't written one single line of code yet my projects have:

  • meaningful unit tests, integration tests and e2e tests

  • the CI has to fully pass and the static analysis tools must report nothing

  • copilot runs on PRs as additional layer, which might not be great but doesn't hurt

  • the linter has to pass to commit, and there are linting rules on the LoC in single files

  • there are benchmarks which are disguised as tests and they must not get worse more than 5 percent otherwise the PR can't be merged (these run on dedicated runners)

  • I didn't directly do any of these but I directed the AI because most were things I was doing by myself and I am simply enforcing more.

  • All my e2e tests use testcontainers and literally fully deploy the infra standalone as much as possible (most of the modern services offer emulators that run inside docker or are compatible with alternatives that can run locally via containers).

This is my standard and the standard I require for all our repos (the benchmark only for sensitive stuff), some like it some don't, luckily not their choice 😊

Again, it's not a matter of what, it's a matter of whom 😅 The alone vibe coder is instead a very different "beast" and without reining in the roaring pointless confidence it will just crash against reality.

2

u/iKontact Apr 02 '26

Copys & Pastes his response into Claude:

"Claude did you think about all these edge cases? Get to work!"

Lol

2

u/RegularOstrich3541 Apr 02 '26

It might take years to learn a skill to scale , LLM learns that in a sec . LLM can definitely create powerful systems at scale. You have to be an experienced engineer to know what to prompt

2

u/mad01 Apr 02 '26

It takes substantial effort even with AI to build apps even when you’re a developer

2

u/casual_rave Apr 02 '26

Most of these people don't try to build massive-scale apps to be used by millions of customers, so naturally they haven't faced any of the problems mentioned in the post. You make a simple app to be used by 10 people, why care about distributed systems or database replication? Your project requirements will be less in numbers, and simpler in their nature.

2

u/GOTW7 Apr 02 '26

But it is possible to build a entire app without coding and keep having good performance, security etc

2

u/edmillss Apr 03 '26

the real issue is people vibe code stuff that already exists. like why are you having claude write a custom auth system when there are 50 battle tested ones already. i started pointing claude at a tool catalog (indiestack.ai has 8k indexed with an MCP server) and the code quality went up immediately because now its wiring up proven packages instead of hallucinating an auth flow from scratch. vibe coding works fine for the glue, just dont vibe code the foundations

2

u/Tricky-Pilot-2570 Apr 03 '26

The marketplace doesn’t give a damn about your 'eventual consistency' or your $300k ego. While you’re in a dark room solving imaginary problems for 50,000 users you don't even have yet, the guy with the AI prototype is out there actually making a sale.

The hard truth is that most 'perfectly engineered' systems are just expensive monuments to an engineer’s pride. I’d rather have a 'broken' app that puts money in the bank today than a 'perfect' one that stays in development for a decade. If the wheels fall off when you hit 50,000 users, that’s a high-class problem—and one you can solve with the profits you’ve already made.

Until then, you’re just a cost center complaining about the people who actually know how to ship.

2

u/IckrisRun Apr 03 '26

Ex-dev here. Got in the game before PHP went Object oriented.

Non-developers have been hacking successful apps together for well over a decade to secure thousands of users as the first step to getting vc money. All anyone that doesn’t have deep technical knowledge needs to do is leverage a BaaS or SaaS to get up and running. You don’t need 20 years of deep experience. You just need to leverage available services that handle the scaling and security for you. Been this way for a long time in the startup world. The gatekeeping is wild.

2

u/TheExodu5 Apr 03 '26

No one pointing out the fact that the post is obviously created by an ai?

2

u/bluewhackadoo Apr 03 '26

I don’t agree with this entirely. But also, it does feel like the fart app era of mobile.

2

u/arbyther Apr 05 '26

While this tweet is complete true (the mvp isn’t the hard way part), I find it funny that we’ve been saying «Optimize late (or never)» for decades, but suddenly when something is vibe coded, we’re expressing our concern about how a project will handle 50K concurrent users…

2

u/Safe_Presence_9341 Apr 09 '26

I am an artist - I simply do not have the money to pay someone from an industry who on average earns 10x than an artist. So this finally enables me to build artistic software systems the way I imagine them. Even though the process is insanely frustrating and to 60% I have no idea what the code exactly does. Also I hate how much babysitting it is. And the hallucinations where something works - I fix some bug and then the thing that always works is broken and then I am using all my credits on fixing that. But - I go through this pain to build my vision, it is currently the best way forward I see.

→ More replies (1)

2

u/True_Sir_5042 Apr 16 '26

I agree that vibe coded products aren't maintainable.

Honestly though, the majority of software engineers aren't really much better than LLM output. I don't mean that in a way where I'm praising LLMs. They can't be used effectively without domain knowledge.

It's just that...most people writing software are terrible at it, with or without AI assistance.

4

u/hvacsnack Apr 02 '26

This won’t age well

7

u/DangerousSetOfBewbs Apr 02 '26

Not wrong and yet still wrong. The tide is shifting. I remember doing pen testing the manual way before automated scanners could effectively do end to end with reporting. We all laughed because of the bugs and shotty reporting. Now we all use them and they are extremely effective, and occasionally when we get time use the manual way for fun. This is an angry coder at best trying to cling to the idea that their job can’t be fully replaced. Yes they are correct, in this moment they are safe. But in 6 months maybe not

→ More replies (23)

1

u/Se4h Apr 02 '26

Partially agree. Vibe-coded projects fail mostly because they aren't grounded in business and user needs - they solve the author's own problems, which is fine. But in a business context, you need monetization and real user pain points plus technical requirements. Without those constraints, failure is almost inevitable in the monetization layer.

That said, this isn't new. Plenty of such apps existed long before AI. It's just much much easier to build now, so the scale of failures is far more visible.

1

u/Amazonrazer Apr 02 '26

I made a script that scrapes google lens images and bypasses their anti-bot measures without using any cookies and from a datacenter IP.

1

u/Matmatg21 Apr 02 '26

So this post assumes that the future of software is SaaS as we knew it in the past 20 years – one app that serves millions of users.

But what if the future of SaaS is more personal, if it serves max 50 users does it really matter to have the most optimal race conditions, etc?

Personal SaaS didn't make sense before because it would be a bitch to maintain (and slow you down), but now with claude I'd be lying if i said it was hard to maintain simple software. More and more autonomously too btw

→ More replies (1)

1

u/Glockenspielintern Apr 02 '26

Yeah and I can just copy and paste this into claude code though and get the solutions written out for me.

Its about knowing what it is not how to do it, which I'm afraid to say is a more challenging skill to maintain and keep up. Learning syntax from memory is kind of dumb.

1

u/Dmoh34 Apr 02 '26

Then there’s the whole marketing bit and does your product really solve a problem or is it the 1,245,8957th to do list app

1

u/Daadian99 Apr 02 '26

The first 90% takes 10% of the time. The last 10% takes 90% of the time. This has always been true of software.

1

u/THE_RETARD_AGITATOR Apr 02 '26

yes & no, it's not 0.5% but a good exaggeration to give the proper wakeup call.

most companies don't even need the scale of slack. so 90% of the time they are over engineering the fuck out of everything anyway

1

u/Alundra828 Apr 02 '26

This guy cooked hard. And while this is obvious to every developer that's ever developed any bit of production software, this clearly isn't obvious to project managers, or CEO's who are assuming what it can do.

1

u/rc_ym Apr 02 '26

Yeah, the next thing they need to folk on is ops work. Claude is already a passible sysadmin, but I wouldn't let it touch production, not even on my home servers, without heavy sandboxing and a human minder.

1

u/Tryotrix Apr 02 '26

"claude yolo mode pls help. Someone critized us. See: [Paste1] - Please create a plan to fix it and explain to me"

3

u/Tryotrix Apr 02 '26

/btw whats local host?

1

u/Select-Way-1168 Apr 02 '26

Blah blah, "I'm down in these mines, shipping st scale" blah blah, engagement.

1

u/fouriels Apr 02 '26

It's already been said indirectly in the comments, but more directly: 'and what if you didn't want your app to compete with slack/discord'? If you have a small use-case for your app, LLMs might be the right tool for the job in terms of being fast and cheap, even if they write sub-par code.

I'm sure that there are a small number of deluded people who think that vibecoding will enable them to make Whatsapp 2, but otherwise the OP is tilting at windmills.

→ More replies (2)

1

u/Idiberug Apr 02 '26

One trick I learned early on in my software development career is that your frontend styling should be an indicator for the status of your backend. If the backend functionality isn't done yet, don't style your component or else the customer may think it's 90% done already.

1

u/WinProfessional4958 Apr 02 '26

Just ask it to make Kubernetes with ISTIO routing GRPC-Web. Problem solved.

1

u/BeerAndLove Apr 02 '26

Now, I would copy his response, and tell Claude to do all these things. Profit! /s

1

u/Whyme-__- 🔆 Max 20 Apr 02 '26

I only use Ai to debug and learn if there are any better ways to engineer something then what I did.

1

u/Zennivolt Apr 02 '26

As a software/devops guy, I agree with every sentence except one. It's not like pouring a foundation and saying you built a skyscraper. It's more like sketching an art piece of what you want the skyscraper to look like and saying you built a skyscraper.

1

u/Financial-Outside158 Apr 02 '26

Nailed it! I have a younger family member who pinged me recently to ask about how to improve his 1.0 build. After careful review (literally 1 min) I told him, for starters you cant have the entire codebase in a single file. He argued with me, so I let him crash and thus he burned.

1

u/bb0110 Apr 02 '26

Ai right now is incredible for making things for personal use (by personal I mean to be used by you, it could be for business purposes). It is not amazing at making products to scale though. That still needs attention to detail and experience from someone who knows about the space. That doesn’t even touch on the fact that once you make a product to scale there is the whole business portion, which is the tougher aspect of all it.

1

u/wellarmedsheep Apr 02 '26

This entire copypasta is gatekeeping dressed up as wisdom.

I'll the excitement of people building and discovering the same thing over and over to what this sub has become.

1

u/Disastrous_Start_854 Apr 02 '26

I believe that there is vibe coding and then there is a.i assisted development. Vibe coding is like being a conductor but you have no idea what the fuck you’re doing while waving your arms around but because the orchestra is making sound, you consider it to be music. Of course that is a disastrous result. With a.i assisted development, you have the experience and knowledge from several years of experience and you know how to conduct the music beautifully. You are meticulous in every motion and you ensure that every note is perfect which can lead to wondrous results. A.I is only a real tool in the hands of the right user with the proper background or even with vibe coders who are intelligent enough to hire real developers to fix their work and making a authentic, secure, and workable product to scale. That be my 2 cents.

2

u/simplex5d Apr 03 '26

100% accurate.

1

u/fadeawaydunker Apr 02 '26

The analogy is way off, most people who vibe code just do it for personal use, friends, or for their work/business. Not for use by millions of people.

People who even think about vibe coding that way are just arguing with those hype posters online. Who intentionally hyperbole everything for engagement. Baited.

99.9% of people who vibe code have zero intention of making something like slack, discord, or anything similar. They just want to make personal tasks easier or implement their own projects.

1

u/Nexma26 Apr 02 '26

The biggest reason I don't think all this AI stuff is going to replace real experienced workers. Ai can definitely reduce friction, but it doesn't minimize logistics.

1

u/flarpflarpflarpflarp Apr 02 '26

Claude review this post and see if I have these issues w my app.

1

u/Big-Fan9696 Apr 02 '26

Agreed but I mean the point of AI at least the way silicon valley is using it right now is not to replace high level engineers it's to accelerate product development. If you can get to 50k users with vibe-coded really junior level systems. You can get vc funding and hire like real engineers that have more domain knowledge then you. Getting to the stage of 50k users is a accomplishment for anyone lol.

1

u/blutosings Apr 02 '26

That chat app might be a total disaster in terms of security, scalability, usability... and everything else but it could also solve a problem for internal communication in a company intranet between a few people that want to exfiltrate their companies data and violate company security constraints so win-win right?

1

u/[deleted] Apr 02 '26

Although, to be fair, most startups like slack probably also weren't aware of the challenges beforehand. They mostly learned and adapted on the fly. This can also be done with vibecoded products. Imo the problem of vibecoded products is not that they are not prod ready or scalable, it's most often that they are uncreative and generic.

1

u/CriticalDiscipline4 Apr 02 '26

There’s this pushback I’m seeing against vibe coded projects but the key to developing profitable new products and services is to test them out, to experiment, to try new things and fail, and that’s what vibe coding allows immediately without regard to notions of AGI or ASI. It compresses the time to find new markets or ideas.

1

u/hiepxanh Apr 02 '26

It true, the scale issue is big issue

1

u/schooledapp Apr 02 '26

As my friend used to say, gtfol (getting the fuck off localhost) is the hard part

1

u/Jeferson9 Apr 02 '26

Stopped reading at "readability". Almost had me there.

1

u/Timo425 Apr 02 '26

Let me guess without reading first: tech debt, maintenance hell, losing track of what your codebase is doing?
EDIT: ok ok close enough, scaleability and laying out all the infrastructure is the big one.

1

u/UFXProject Apr 02 '26

People use LLM and never audit anything.... that's reason for 50% of fails.... Stress testing never happens that's 20%.. 30% is they have no idea how things work.

1

u/ThreeDMK Apr 02 '26

This is legit. After using Claude for a short time, I decided to come to reddit and see how people are using it. What I see is pretty concerning.

The tool is incredibly powerful in the right hands, but equally dangerous in the hands of someone without experience in these fields they are developing tools in. It gives people a false sense of security. This then feeds into the leadership thinking that AI solves everything. Reality: People are building one off solutions without the real capability of supporting these solutions without Claude.

Even small applications for the office need some levels of redundancy and fault tolerance when things go bad.

1

u/djyeo Apr 02 '26

What if claude code updates and offer these skills in the new update?

1

u/Fstr21 Apr 02 '26

I dunno?... Just maybe let me build?

1

u/timiprotocol Apr 02 '26

people confuse "it runs" with "it works at scale"

1

u/QuietLunch2077 Apr 02 '26

“Yeah, israelgpt please generate me an obvious common information and make it look controversial. Make no mistakes”

1

u/aualdrich Apr 02 '26

Slack doesn’t suffer by one dev vibe coding it. It suffers by 100 small scale but competent devs vibe coding it. It’s just a case of more competition.

1

u/TimeKillsThem Apr 02 '26

Sure - but I would argue (or hope) that vast majority of vibecode only projects are for personal use. This shit is amazing because it truly does become your software/tool, instead of a software/tool you use. Plus, it’s fun as fuck hahaha

1

u/greeny1greeny Apr 02 '26

Apps can be cloned. Marketshare cannot.

1

u/PaperHandsProphet Apr 02 '26

Claude read this post and give me a game plan to implement fixes

Implement those fixes

Have codex verify the fixes and plan

Have Claude codex and Gemini constantly reading logs and alerting when they detect an issue and give a game plan

Summarize this post and respond to twitter OP sarcastically

1

u/PyrrhaNikosIsNotDead Apr 02 '26

I don’t care about scale, I want to learn the security though. 100 users and secure is appealing to me

1

u/jonsnow1308 Apr 02 '26

I think we can do plan better with these llms and then built a scalable system

1

u/rm-rf-npr Apr 02 '26

Can't wait 'till this vibe coding era passes and people realize that "maybe you do need technically skilled people to make products that don't cost millions in privacy violation fines, data leaks and security violations.".

Bring on the lawsuits!

1

u/RubiksCodeNMZ Apr 02 '26

I understand your point, but don’t buy into whole death of SaaS, simply because of responsibility. The part of what license is selling is that it is not your (or your department) responsibility.

1

u/rmethod3 Apr 02 '26

Amen to this.

1

u/fpesre Apr 02 '26

Totally agree

1

u/Long-Presentation667 Apr 02 '26

Claude, what are race conditions

1

u/dylan4824 Apr 02 '26

Just add "consider how this might be scaled to millions of people" to the prompt smh

1

u/Typical_Brilliant432 Apr 02 '26

We had this problem at work… if you don’t know what good looks like AI wont save you

1

u/DarkMatter007 Apr 02 '26

I remember one line from a guy and that’s the problem with all projects.

It costs 10% of the time to get to 90%. Then it costs 90% of the time to finish that last 10%.

Making it work at scale + making it profitable + get users are all part of the same game. Not only a security skill or a supabase skill

1

u/sfjhh32 Apr 02 '26

And the big question is if all requirements can be specified if the agent (or agents) are able to meet those requirements in the near- or long-term for someone to vibecode a slack killer. Clearly the answer now is 'no', but I'm wondering about fundamental limitations in the medium- or even long-term.

1

u/hustler-econ 🔆Building AI Orchestrator Apr 02 '26

Claude knows how to write functions and 'code' but has judgement as a human with business logic in the real world. It can give you bunch of polished sentences but it has no real experience, real pains, real relationships, real jobs of the real world like us people have.

1

u/relativityboy Apr 02 '26

Foundation is over-stating it. More like a Sweeded version.

And for people who want to see what sweded (alt spelling) really looks like - https://www.youtube.com/watch?v=5TBq_gDHsy4

1

u/Vorenthral Apr 02 '26

Can't wait for C suite to find this the hard way

1

u/ShaggyAF Apr 02 '26

Check my app out and tell me it won't scale: http://localhost:3456

1

u/Acrobatic-Cost-3027 Apr 02 '26

As someone who has a scaled product that serves millions of users, this is not the infrastructure that most of these products start with. That said, while AI is not going to solve all of these problems today, I firmly believe it will in the future. Just need the capital.

→ More replies (1)

1

u/Broad_Committee_6753 Apr 02 '26

Fear mongering….can u face these issues? Yes, will u? Who knows….also how many start-ups will hit 1000 daily users never mind ten of thousands ….new CS grads are crying and fear mongering

1

u/Stop_looking_at_it Apr 02 '26

I’ve never seen developers panic like this

1

u/Wozar Apr 02 '26

This first thing AI builds is confidence.

1

u/india2wallst Apr 02 '26

Claude and Codex give non coders a lot of confidence in their ability to write plain English prompts. It's that overconfidence that's paired with distrust in developers

1

u/petitlita Apr 02 '26

you can vibe code terraform too tho

1

u/D_Costa85 Apr 02 '26

I make all kinds of apps for our small business use and personal use and they work great. I would never pretend to know how to make anything for anyone outside our walls that can scale exponentially. That shit is hard.

That being said, AI has made my work life so much easier and less tedious in every way imaginable.

1

u/MacPR Apr 02 '26

Yes, it is true. You can’t vibecode slack, but you can vibecode a version for your org. Then you ditch slack.

1

u/silentsam77 Apr 02 '26

This is what separates the "vibe coders" from the "architects/experienced coders".

1

u/fyn_world Apr 02 '26

Yep. I'm a vibe coder. I created a google chrome extension for my own needs. Worked well etc. I got Codex Cli and loaded the project in it. I told it, hey, I want to make this extension public in Chrome Web Store. And Codex Cli went - hahaha, ahhahah, ahhh, wait, you're serious. - Aaaand I had to learn to make something professional and oh boy it takes a lot of time for how technically small this extension is.

But yeah, impossible to vibe code correctly without a CLI and even then you have to be very willing to learn and test and iterate a lot.

→ More replies (1)

1

u/innahema Apr 03 '26

Well. Slack sucks ass! IDK about neginering of their websockets but UX is awful. Discord / Telegram are 500% better.

And actually messages occasionally don't deliver or get stuck. UI freezes often. And when you lose connection to internet experience is awful.

1

u/ElysCube Apr 03 '26

ah not this again... every day... If you cannot code you won't be able to finish any code related project. Period.

1

u/Gears6 Apr 03 '26

It's not just that, but the most difficulty part is getting users to use your shit. If you have enough users, you can hire people to fix it. You can't hire people to fix shit if you don't have users and hence don't make money.

It's not like there weren't gazillion chat apps prior to discord or slack.

1

u/ImOutOfIceCream Apr 03 '26

This is why I left the tech industry and started a solo consultancy. I have handled all of those situations over 20 years in Big Tech and know exactly what to do. Small business owners deserve access to good software engineering at reasonable rates. Ivory towers and walls of IP should crumble, filling in SaaS moats and turning software into a commodity. Grond! Grond! Grond!

1

u/slow_diver Apr 03 '26

I mean, of course. But as a non-coder, I feel where it's actually killing things is the one-off apps. Functions that used to be paid plugins for my website, subscription apps that I can now replicate, things like that. I'm saving $10/month here and there, or maybe $99-200/year by vibecoding it myself. As long as it's not being distributed or used at scale, it works exactly as needed.

1

u/Alone-Biscotti6145 Apr 03 '26

I've acknowledged this from day one: vibe coding isn't magic. It doesn't ship the entire build; it's pretty much an MVP builder. Once I noticed this, I leaned toward more local-style tools where security and infrastructure aren't as demanding. This way, I know I'm not steering myself in the wrong direction, learning the basics and building from there. It's not a genie in a bottle; it's a partner with broad depth in the majority of subjects. If you use its strengths instead of trying to create magic, you tend to learn a lot more.

1

u/Otherwise_Rise3548 Apr 03 '26

U mean the first 10,000 lines of code...

inside one file?

1

u/_Pixelate_ Apr 03 '26 edited Apr 03 '26

From a long Web Dev person with a Design background, being able to create platforms or sites using Claude Code, is an opportunity to move ideas forward.

I'm not claiming to know more than I do, but being able to create a foundation or a version 1 of a platform without having to hire a Coder team right away is exciting. I don't know enough about coding or building platforms that scale and are secure to know whether Claude Code that build those aspects of the project or not. That being said, it's exciting to see ideas come to fruition in a way I've never experienced before.

That's why I'm joining and learning more about platforms like Github and using Reddit and other forum to ask questions. I joined some of these sites previously, but am now learning more about how they function on a practical workflow.

I imagine that there will be some conflict between vet Coders and Designers who use Claude Code or even businesses that use Claude Code. I went through a similar experience as a Designer when Canva was launched and anyone could make their own logo or graphic designs.

I don't know what the future looks like in terms ensuring Claude Coded platforms are secure and scalable, but hoping to either learn enough or partner with Coders to make that happen on my projects.

And....isn't this a Claude Code community, so why are Coders saying vibe coded projects will fail when Claude Code can vibe code? Is it trying to say go ahead and use Claude Code but you'll see need Coders to make scale and be secure?

1

u/Warm_Lock_2660 Apr 03 '26

Nah not me though built different

1

u/Tricky-Pilot-2570 Apr 03 '26

Engineers are mad that the barrier to entry just collapsed. Yes, scale is hard, but most problems don't require 'Slack-level' engineering. Let people build cool things without the ego check.

1

u/LevelOnGaming Apr 03 '26

The people that get into vibe coding, are the tech literate. They may not be coders per se but they understand some of the systems coders play around with and I think a person like that armed with drive and creativity is more valuable than any other employee right now. Everyone’s gotta be a good AI copilot to make it right now.

1

u/Faangdevmanager Apr 03 '26

You can probably guess what I do from my username. Let me tell you a small secret. We use a lot of AI coding and it’s even part of every SWE’s expectation to use it when it makes sense.

Now there’s a massive difference between vibe coding a whole app and asking AI to write unit tests. But a lot of boring, repetitive, or integration tasks are easily solvable at scale with a solid <agent>.md file. Where we had static generator before to save time, we now have AI generator for things that are deterministic enough. Then have other agents validate the work before they get out through a series of tests.

My SWEs are happier they don’t have to read a 30 page integration guide for a one off project. They are also delighted to not have to write 300 lines of unit tests on 150 lines of feature work.

And yeah, my team owns a product with more than 1.5B MAU :) AI doesn’t architect or design, obviously but has been helpful in design review to clarify some edge cases.

1

u/Fermato Apr 03 '26

Yeah so? Give it a year and all his points are moot

1

u/Horror_Brother67 Apr 03 '26

who here didn't known this? Genuinely curious.

1

u/vamonosgeek Apr 03 '26

Vibe code is usually linked with people that don’t know how to code or even think about system architecture.

Vibe coding gives them the moment they’re dreaming of making something and seeing it work in a localhost.

1

u/rutvaL Apr 03 '26

But vibe coding your own custom requirements that only cater to one user by combining and stitching many different features of many products available into one single vibe coded local-hosted project is the best thing one can ask for as a vibe coder. Why pay for 3 different subscription products where you can just vibecode what you like into one? It reduces the overall cost when looking at longterm subscription to those products.

1

u/ChikkuN07 Apr 03 '26

You are wrong, you just need to know to build properly, It is obvious that one shot applications wont work at scale, it took me 1 month 1000s of iterations to build a perfect application in a way I want it. Use BAAS.

CLAUDE BUILT COWORK VIBE CODING.

1

u/Odd-Investigator8666 Apr 03 '26

The amount of multi million companies that have shit software is massive, you don’t need to know how to work with websocket at scale if you want to make a million bucks with software (or100 million)

1

u/Taurus-Octopus Apr 03 '26

I've been vibe coding at home for single user niche tools I want, and I guese its natural that someone wants to make money off these things.

But I'm really just enjoying that I can make a fantasy baseball alerting system for breakout performance tuned to my weird league scoring system. No desire to "ship" anything.

Ive been using regular copilot to code at work as a non coder. Its been great, but my procese has become rather (necessarily) intensive where I have to make a plan, enumerate all of my assumptions, identify contracts, establish an architecuren(that ends up changing), make a skeleton draft, flesh out a module and test it, flesh out a layer and test it, iterate for each layer, dream about it, cry over it, finish it, then feel a delusional sense of capability, then get told it immediately broke, test it, fix it and live with the anxiety that it will eventually break again, and hopefully not so long that you forgot how you made it.

These are for 4 users maximum, so here's hoping my stdlib python scripts dont bring my massive employer to its knees via a compromised, vibe coded SQLite database.

1

u/bitspace Apr 03 '26

Why reddit posts fail  

Screenshots suck 

1

u/pon12 Apr 03 '26

Like anything else, early validation is a key. It's just easier to build stuff faster now.

I built demotape.dev for easier early stage testing and ux research.

1

u/kloden112 Apr 03 '26

This is literally the Dunning-Kruger effect

1

u/Kemetic_Crypto Apr 03 '26

I think the problem with the above logic is this…. Most users don’t desire to scale to teams of 300k most new devs want to earn a slightly more than their current income lol

The assumption in OP is that I want to compete with that global model most new coders don’t lol

If I wanted to pack a stack to that level I would hire teams let’s be real for a bit here

1

u/rwz Apr 03 '26

Because coding is usually not the most difficult part of a successful project.

1

u/Majestic-Hope3600 Apr 03 '26

That’s true. Good summary. Example from slack says everything

1

u/domocles Apr 03 '26

I think what seems to be missing from this is yeah Dunning-Kruger is a problem for people who have never built anything like Slack. But what happens if one of those 300k a year Devs decides to give it a go? They will know all of the current short-comings of the existing solution and would have a pretty good idea of what it takes to get to the first MVP.

1

u/octotendrilpuppet Apr 03 '26

The "just killed Slack" tweets from localhost are embarrassing and give the whole movement a bad name. A prototype is not a product. No argument there.

But there's a framing problem in this conversation that keeps getting missed: these distributed systems problems are being treated as permanently hard.

Race conditions, eventual consistency, message ordering, presence systems, WebSocket scaling — these were genuinely hard to DISCOVER. Slack's engineers spent years debugging failures that only surface at scale with real users. That discovery process was painful, expensive, and required deep expertise. Full respect.

But once discovered, those solutions became knowledge. CRDTs, Redis pub/sub, database replication patterns, WebSocket gateway architectures, sharding strategies — all documented in papers, blog posts, conference talks, open-source implementations. None of it is secret. None of it is black art. It's engineering knowledge, and it's banked.

Tell Claude Code "architect a chat system for 50K concurrent WebSocket connections with message ordering, eventual consistency, and presence detection across multiple regions" — it doesn't guess. It draws on thousands of documented implementations of exactly these patterns. Redis pub/sub for real-time, PostgreSQL with read replicas for persistence, horizontal WebSocket gateway, CRDT-based conflict resolution. Not magic. Pattern matching against the entire corpus of distributed systems knowledge that humanity has produced.

The gap between prototype and production is real. But it's not static. It's shrinking every month. What took 50 engineers a decade will take 5 engineers with AI tools a fraction of that time. Not because the problems got easier — because the solutions got accessible.

The hard part was never writing the code. The hard part was knowing WHAT to build and HOW to debug it when it breaks at scale. AI is increasingly good at both. Not perfect. Not one-shottable. But the ceiling is rising fast.

I use AI to build production tools every day. Not Slack-killers — real tools for real users solving real problems. The difference between the hype bros and serious builders isn't the tools. It's the tenacity to keep iterating past the prototype and the honesty to know how far there still is to go.

The original post is right about the hype. But don't let the hype create the opposite delusion — that these problems will stay this hard forever. They won't.

1

u/PrideQuick670 Apr 03 '26

I built a framework for vibe coders to apply sound software engineering and architectural principles to the apps they build. For existing projects, it will examine your code base, and ask you some basic question about the app and based on your answers and what it found in your code, it will build a project profile that Claude will use going forward. It covers deployment and will analyze what your currently doing and give you recommendations. Just paste the prompt below into the Claude chat window to give it a try:

Read the BOOTSTRAP.md file from https://github.com/jgnoonan/vibeArchitecture and follow its instructions before we start building. Ask me the intake questions first.

I'm a 40 year developer and IT architect and I've lived through several "anyone can build software" technologies and had to clean up a ton of real messes. This framework is a distillation of my experiences over the years. I hope people find it helpful.

1

u/False-Difference4010 Apr 03 '26

Talking about skyscrapers, would you move-in a skyscraper built and designed by AI?

1

u/nickosh Apr 03 '26

It's just part of the PR of big AI companies. They actually promise this — "you don't need to be a developer, just one prompt and your Slack-killer app will be ready". They are misleading people for a reason, money reason. They need to extend their business and invite people who are not engineers too. Your app will actually look like Slack-killer but it's actually not exactly true. It will still be a working prototype, not a production-grade product. But nobody highlights this in PR materials. "You could build a prototype from one prompt and then need to spend a year of self education and polishing to build a real product without any prior knowledge" - sounds not so marketing friendly. Let's not blame people here. Build real products with AI tools are very real, but you can't skip the hard work part even with these powerful tools. Not yet, at least.

1

u/NewDad907 Apr 03 '26

At least with me, I’m the SME of the subject my project is about, so I know if it’s working or not and what it should/shouldn’t be doing.

And I’m also under no illusion that why I’m creating is basically just a bigass HTML document, not a “real” application. There’s zero database, no call requests.

It’s literally a spreadsheet on steroids with a user interface.

It probably helps that even though I’m not a SWE or Dev, I have been on project teams as a SME/tester and did the whole Jira test scenario stuff for a big .NET build like 12 years ago. Helped refine the UI and make sure certain features worked.

I think it was a compliment, but I got told I’m good at breaking things lol, so they always seemed to want me pushing the limits of what the program could do.

1

u/Munchmatoast Apr 03 '26

This misses the mark completely.

Why are you comparing continent wide scaled infrastructure to a small scale vibe coded customer facing web app?

If you strip the first half and just compare the customer facing web app of slack to your vibe coded web app, then yeah, you can "kill slack" and make a far more superior customer facing UI wrapper.

You don't need $300k per year software devs to rollout software to self contained businesses. Why pay extreme amounts of money for slack when you can just get a personalised web app that does exactly what slack does for your business, but better in almost every way, fully customisable to how you want it to be?

zzz.

1

u/JazZero Apr 03 '26

I don't know if it's vibe coding or not but I have begun using AI to write blocks of code that I assemble into the final product.

Like no one has time to hand write mappings for 2 letter Country Codes to 3 digit ISO Country Codes.

Ai saved me 3 fucking hours of work right there.

I spend more time architecting the code and AI does the key stroke grunt work. Is this considered Vibe Coding?

1

u/checkwithanthony Apr 03 '26

So if i know what all of these things are and have managed them for years but hate writing code.. can i vibe code? Or do I still need an old school typer to develop for me?

1

u/Jomuz86 Apr 03 '26

I coded a bit before and my main job is a statistical programmer so never did apps and I have come leaps and bounds using Claude and other tools but I 100% agree with this, it’s great for making internal tools even things that could probably handle 100 users or so. But when you get to needing to handle and debug a scalable infrastructure. The year and a half nearly two years it’s taken me to get to the point I am teaching myself as I go along I would probably the same time and then some to get something to work at scale on my own.

1

u/jmills2222 Apr 03 '26

You can ask ai these questions it will answer and tell you what you need or do what it can lol

1

u/IcyMaintenance5797 Apr 04 '26

But they'll learn a lot along the way.