Andrew
Region: US
Monday 06 July 2026 19:35:02 GMT
32749
810
130
46
Music
Download
Comments
pandabomber.gg :
Vibe coding standalone apps is easy, connecting it to existing legacy systems is not
2026-07-06 20:25:12
194
Adam :
Because you’re planning to make a v2
2026-07-11 21:08:41
0
Elideus :
Because a UI is not software.
2026-07-07 01:46:43
10
Luke Rhodes :
Vibe coded apps and mocks don’t yet
2026-07-11 02:14:54
0
Alex :
If you want to ship your vibe code, then it’s up to you to 1) fix it when it breaks 2) refactor it when it’s time to scale 3) take responsibility for any security issues. But no, you’re going to come to the engineering team for that, and it will take us twice as long to untangle your crap than it would have to build it in the first place.
2026-07-08 15:40:52
3
Ketsi :
Lol PMs are useless in general
2026-07-07 20:46:49
19
SeriusZen :
Programming has never been the bottleneck in software. It’s the engineering and team coordination that takes time. That’s why companies are seeing so little return on AI.
2026-07-07 09:19:33
36
Jacob Herlin :
because the vibe coded prototype uses made up data, and the real project needs an actual backend that's 90% of the work
2026-07-07 13:01:29
60
GetElevatedM8 :
The bloat you’re talking about is based off of years of knowing how things need to live in production or it’s terrible to maintain. Having code that works today is less than half of running a system.
2026-07-07 15:54:08
12
mike85432 :
vibe coded apps are garbage
2026-07-06 22:43:37
28
bsweyand :
Security, observability, scalability, well architected, stack considerations, ci/cd. A PM doesn’t know any of this. So tired of these posts man 😭. It’s just engagement bait (and I’m falling for it ig)
2026-07-08 01:33:10
8
Mattias Andersson :
My take on this is that when developers are planning a task, we think about the different situations that might come up ahead of time, and the task grows. we also like to reuse different kinds of components. we like to create smart systems that might be used in the future. I think we need to rethink how to program now that we have AI. we don't need to have reusability in the same way. an AI can make changes really fast that it's just not worth it to over complicate things. we just need to make sure that the code the AI creates is safe.
2026-07-06 21:45:17
6
Andrew Berg :
Looks good enough, why aren’t I getting 2M dollars?
2026-07-06 23:38:16
18
Уинстон / Winston :
security, sustainability, refactor-ability, reducing redundancies, tech debt. AI can make a bad software look kinda good and have 1 function but for a scalable secure application? you need a dev to guide that. AI will just make 10 unsecured GET requests not reusing any code and call it an API
2026-07-07 01:01:22
19
oskar 🌇 :
because vibe coding is just about as useful as “no code” was a few years ago. it’s all hype
2026-07-07 13:43:47
5
afp7200p :
are you that PM?
2026-07-06 19:57:26
12
josephgerardot401 :
yeah if its finished let them maintain it. if you want me to maintain it you're gonna build it the way i tell you. there is bloat but there are also reasons things take a long time
2026-07-07 03:19:44
8
User4908632995480 :
Everyone disagreeing doesn’t understand that shipping the MVP faster is more important than anything , yes legacy systems aren’t going to benefit as much but new systems will be better
2026-07-07 11:10:28
0
Catnip & Chives :
Vibe coded quickly does not mean the architecture can scale, is secure, or minimizes technical debt. Slow and steady, plus a lot of QA, often always wins the race.
2026-07-08 01:42:06
2
kai :
Can they debug or know if the code correct?
2026-07-08 13:41:15
2
PenguinKing :
You answered your own question, it’s a prototype that was vibe coded. It has to be built so that it actually works, can pass legal checks, security checks, needs to be compatible with the rest of the system, etc.
2026-07-10 19:46:18
1
MarkD :
The vibe code is the prototype, you need to find the problems with the prototype and the requirements, communicate them around around, fix them and setup the CI/CD chain for the product and test the thing. 4 weeks is not a bad timeline for that.
2026-07-07 14:03:37
1
USAAF13 :
Getting a concept is easy.. but at the moment im also building a massive project,, first part “looked” to go fast… now we are at least 3 months further and still not finished
2026-07-07 11:51:35
0
Lloyd Gross :
I’m a manager for a software engineering team and we’re really trying to drop the bar so those folks can deploy their own vibe coded apps. They’re all terribly written and don’t REALLY work. I’d rather us focus on outcomes and what the business cares about.
2026-07-07 02:54:01
0
To see more videos from user @andrhlt, please go to the Tikwm
homepage.
