Two developers discuss burnout in software work. Speaker A warns against "vibe coding"—quick prototypes that look good in demos but create maintenance nightmares. They cite an 18-month GoHighLevel project as an example and stress the importance of delegation to avoid burning out.
Chapters
A lot of my job is making sure you have like a really lean process because you're going to burn yourself out is what happens, right? So you have a system that's kind of okay, sort of good. You're okay with it. Clients are coming in, but, um, you know, you wish it was better. Now you're vibe coding. Now all your time is going to go into this, right? And trust me, like vibe coding is great to get an idea out and to get people to develop it. But it is not meant for you to have a final product only because you're going to have to troubleshoot that. You're going to have to, you know, then go and like fix things on whim. Customers complain, you got to fix it in real time, right? And all this has a time expenditure too, just like the 18 months you spent on GoHighLevel, right?
Yeah. And so you're being able to delegate. ¡Hola!