Lazar Jovanovic
Lazar Jovanovic is a full-time professional vibe coder at Lovable. His job is to build both internal tools and customer-facing products purely using AI, while not having a coding background.
Episode
The rise of the professional vibe coder (a new AI-era job) | Lazar Jovanovic (Professional Vibe Coder)
Summary
Lazar Jovanovic, the first official "professional vibe coder" at Lovable, describes his full-time job of building products without writing a line of code, and the specific frameworks he developed to get high-quality output from AI tools. The conversation covers his "parallel build" method (start 4-5 projects simultaneously), the importance of PRD documentation to manage LLM context windows, and why non-technical background is actually an advantage — you don't know what's supposed to be impossible.
Key Takeaways
Start every project by building 4-5 parallel versions with different prompts before committing to a direction — this prevents locking into a bad architecture early and saves more tokens than it costs.
Spend 80% of your time planning and only 20% executing: write PRDs (master plan, implementation plan, design guidelines, user journey) before prompting the agent to build.
The ceiling on AI output is not model intelligence — it's what the model sees before it acts. Always reference the specific file where a bug lives rather than describing the problem vaguely.
Non-technical people have a structural advantage: they try things technical people know "shouldn't work" and often succeed. Approach AI tools with "positive delusion."
Optimize for judgment, taste, and good copy/fonts — those mechanics will be automated within months, but good taste and decision-making will remain the scarce resource.
Notable Quotes
“And then it's my personal mission that resonates with me because if there wasn't Lovable, I would've never built anything, potentially in my life and I don't think that, that would've been a fun life to live. So I guarantee people, I've tested this framework with many people and everybody's telling me the same thing, "Eye-opener."”
“Somebody else can do the writing. You, as somebody who directs and builds this product, you need to know, again, what's going to be useful, what's going to be tasteful, what's going to be something that actually moves the needle. I will say one thing though, just because I put so much emphasis on, "Oh, you need to acquire taste. Oh," that doesn't mean you shouldn't build. You get better at this by building actually.”
“So my advice for people is, yes, vibe your way for fun and vibe your way while you're prototyping because that's the exploration part. I love that part. But when exploration is done, please, please, please use referencing, documentation. Use all the agent files that you can because that token allocation is so scarce. It's going to get expanded over time. Things are going to get cheaper, faster, but right now it's still so valuable and precious, you really need to make sure that they are allocated in the right direction.”