In this episode, John Rymer and Rob Koplowitz sit down with Dave Marcus to discuss his hands-on evaluation of the fast-moving world of vibe coding, low-code, and process automation platforms.
Dave explains why he chose a CRM-style application as his test case: it had a realistic data model, a third-party integration with Microsoft SharePoint, and a workflow component that would reveal how these tools handle real business complexity rather than simplistic demo apps.
A major theme of the conversation is the difference between prompt-driven development and visual tooling. Dave found that while prompting could generate surprisingly functional applications, the experience often became frustrating when he needed to adjust layout, test changes, or understand dependencies. Visual tooling, when available, often helped—but some platforms treated it as secondary or immature compared to prompting.
The discussion also digs into a critical enterprise concern: maintainability. John and Rob push Dave on what happens when applications need to evolve over time due to changing business, regulatory, security, and workflow requirements. Dave emphasizes that model-based systems still matter because they make dependencies, workflows, and governance visible in ways code-heavy systems often do not.
Another key takeaway is workflow orchestration. Dave argues that workflow is not just a diagram—it is part of the application’s operational logic and must be understandable to domain experts, not just developers. He notes that some pure vibe coding tools bury workflow in code, while some process-centric platforms add complexity that may be more than needed for simpler applications.
In the end, Dave’s conclusion is nuanced: there is no single winner. Different platforms are better suited to different use cases, and the market is evolving too quickly for simplistic “replace everything” narratives to hold up.
Key takeaways
- A realistic evaluation needs a real application, not a toy demo.
- Prompting can produce functional apps, but visual refinement and testing remain important.
- Workflow and dependency visibility are essential for enterprise maintainability.
- No single platform category is best for every scenario.
- The market is evolving quickly, so these tools must be reassessed continuously.
