How Chris Dunkel Balanced No-Code Speed, Compliance, and Enterprise Scale Before AI Changed Software Development

Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Chris Dunkel, engineering and technology leader, to discuss one of the toughest engineering decisions many teams faced before AI-assisted development became mainstream: whether to build a complex enterprise platform using traditional software development or adopt a no-code approach.

Facing an aggressive one-year deadline, a three-person engineering team, and mounting business pressure, Chris's organization needed to deliver a brand-new SaaS platform for colleges and universities that could eventually serve millions of students. Traditional development timelines simply weren't an option, forcing the team to evaluate Bubble as their primary no-code platform while supplementing it with custom microservices where needed.

Chris shares how the team carefully evaluated performance, scalability, regulatory compliance, accessibility, and vendor lock-in before committing to the platform. While Bubble dramatically accelerated UI development and enabled rapid customer feedback during beta testing, the project also exposed limitations around backend workflows, database migrations, accessibility implementation, and compliance responsibilities that became increasingly important as the product matured.

The conversation also explores how the software development landscape has shifted since 2022. With today's AI-powered coding assistants, Chris explains why he would now choose an AI-first development strategy over no-code for experienced engineering teams, while acknowledging that no-code platforms still provide valuable guardrails for non-developers and rapid MVP creation.

For engineering leaders navigating build-versus-buy decisions, enterprise compliance, and evolving AI tooling, this episode offers practical insights into choosing technology based on real-world constraints—not hindsight.

Key Takeaways:

• No-code platforms can dramatically accelerate enterprise product delivery when timelines and engineering resources are limited.
• Rapid UI development enables faster customer feedback and iterative product improvements.
• Enterprise software evaluations must consider performance, scalability, regulatory compliance, accessibility, and vendor lock-in.
• No-code platforms simplify frontend development but may introduce significant backend development challenges.
• Compliance requirements such as PCI can evolve during development, requiring close collaboration with platform vendors.
• Accessibility often requires additional customization and third-party solutions beyond native platform capabilities.
• AI-assisted software development has reduced many of the advantages that originally made no-code attractive for experienced engineering teams.
• No-code remains valuable for non-technical builders and rapid MVP development with built-in guardrails.
• Engineering leaders should thoroughly evaluate operational limitations such as database migrations, workflow constraints, and long-term maintainability before adopting a no-code platform.
• The best engineering decisions are driven by current business constraints rather than ideal technical architectures.

Connect with Chris Dunkel:

• LinkedIn: https://www.linkedin.com/in/chrisdunkel

Listen Now & Subscribe:

Apple Podcasts, Spotify, Amazon Music, YouTube, iHeartRadio, Captivate, or wherever you get your podcasts.

Engineering Choices You Have to Defend explores the real technical decisions behind AI systems, enterprise architecture, compliance, and scalable software engineering.