<![CDATA[Engineering Choices You Have to Defend]]>556e85d1-3f20-5565-8898-55e132f3267aWed, 05 Aug 2026 12:45:07 +0000Captivate.fmNicola Onassishttps://artwork.captivate.fm/54628a6b-8ad5-4a68-aea8-4c4eaaaf2ad5/blue-white-black-modern-tonight-s-podcast-cover.pngEngineering Choices You Have to DefendNicola OnassisNicola OnassisReal-world engineering decisions in AI, compliance, and production systemshttps://engineering-choices-you-have-to-defend-podcast.captivate.fmfalseserialnopodcastHow Bill Boulden Defends Engineering Speed Without Sacrificing QualityHow Bill Boulden Defends Engineering Speed Without Sacrificing QualityEpisode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Bill Boulden, a fractional CTO and longtime startup engineering leader, to discuss why adding more processes after mistakes can sometimes create bigger problems than the original failure.

After working as an early engineering leader across more than two dozen startups, Bill has seen founders respond to bugs, downtime, and customer complaints by adding approval meetings, checklists, and deployment gates. He explains why engineering teams should instead focus on an acceptable defect rate and use automated systems to improve quality without sacrificing development speed.

Bill shares practical approaches including CI/CD, unit testing, observability, automated regression testing, canary deployments, and instant rollbacks. He also explains why good processes should reduce human involvement rather than create additional layers of oversight.

The conversation explores how AI is changing software engineering, with Bill emphasizing that while AI can make writing code easier, engineers remain responsible for understanding and approving what reaches production. He argues that judgment, critical thinking, and accountability are becoming even more important as AI-assisted development becomes standard.

For startup founders and engineering leaders, this episode offers practical lessons on balancing speed, quality, automation, accountability, and innovation without allowing unnecessary processes to slow down the entire team.

Key Takeaways:

  • Engineering teams should not automatically add process after every mistake.
  • Teams need to establish an acceptable defect rate instead of pursuing perfection.
  • Automated systems can improve quality without slowing development.
  • Good processes should reduce human involvement rather than add approval layers.
  • AI makes coding faster, but engineers remain accountable for production code.
  • Engineering judgment and critical thinking are increasingly important in AI-assisted development.
  • Excessive processes can discourage innovation and initiative.
  • Leaders should balance engineering quality with business needs and development speed.
  • CI/CD, testing, observability, and automated deployments can reduce production risk.
  • The best engineering systems make quality the default without sacrificing velocity.

Connect with Bill Boulden:


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, and scalable software engineering.

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Bill Boulden, a fractional CTO and longtime startup engineering leader, to discuss why adding more processes after mistakes can sometimes create bigger problems than the original failure.

After working as an early engineering leader across more than two dozen startups, Bill has seen founders respond to bugs, downtime, and customer complaints by adding approval meetings, checklists, and deployment gates. He explains why engineering teams should instead focus on an acceptable defect rate and use automated systems to improve quality without sacrificing development speed.

Bill shares practical approaches including CI/CD, unit testing, observability, automated regression testing, canary deployments, and instant rollbacks. He also explains why good processes should reduce human involvement rather than create additional layers of oversight.

The conversation explores how AI is changing software engineering, with Bill emphasizing that while AI can make writing code easier, engineers remain responsible for understanding and approving what reaches production. He argues that judgment, critical thinking, and accountability are becoming even more important as AI-assisted development becomes standard.

For startup founders and engineering leaders, this episode offers practical lessons on balancing speed, quality, automation, accountability, and innovation without allowing unnecessary processes to slow down the entire team.

Key Takeaways:

  • Engineering teams should not automatically add process after every mistake.
  • Teams need to establish an acceptable defect rate instead of pursuing perfection.
  • Automated systems can improve quality without slowing development.
  • Good processes should reduce human involvement rather than add approval layers.
  • AI makes coding faster, but engineers remain accountable for production code.
  • Engineering judgment and critical thinking are increasingly important in AI-assisted development.
  • Excessive processes can discourage innovation and initiative.
  • Leaders should balance engineering quality with business needs and development speed.
  • CI/CD, testing, observability, and automated deployments can reduce production risk.
  • The best engineering systems make quality the default without sacrificing velocity.

Connect with Bill Boulden:


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, and scalable software engineering.

]]>7bd39334-1f1d-44a7-877c-741cdc054a5bWed, 05 Aug 2026 06:00:00 -040024:59falsefullHow Mona Chitnis Defended Building Custom AI Models When Foundation Models Weren't EnoughHow Mona Chitnis Defended Building Custom AI Models When Foundation Models Weren't EnoughEpisode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Mona Chitnis, engineering leader at Boon and former engineering manager at Apple, to discuss one of the most important AI engineering decisions facing modern software teams: knowing when foundation models are no longer enough for production use.

Working on AI systems for the commercial construction industry, Mona quickly realized that general-purpose foundation models struggled to accurately understand complex construction plans and domain-specific workflows. Rather than immediately building custom models, her team first invested in developing a comprehensive evaluation framework to identify performance gaps, measure business outcomes, and determine whether fine-tuning proprietary models would deliver meaningful improvements.

One of Mona's most significant engineering decisions was choosing to build a hybrid AI architecture instead of relying entirely on off-the-shelf foundation models. By combining proprietary computer vision models with large language models, her team created a system capable of understanding construction documents, extracting measurements, and helping customers generate more accurate project estimates. She explains why data quality, customer collaboration, and continuous evaluation ultimately proved more valuable than simply adopting larger or newer AI models.

The conversation also explores Mona's experience leading privacy-preserving machine learning initiatives at Apple, where federated learning enabled AI models to improve without collecting sensitive user data. She discusses why enterprise AI success depends on representative datasets, thoughtful evaluation frameworks, and engineering systems designed around real customer outcomes rather than benchmark performance alone.

For engineering leaders building AI products in specialized or regulated industries, this episode offers practical lessons on evaluation strategy, production AI architecture, data quality, privacy-preserving machine learning, and building AI systems that deliver measurable business value.

Key Takeaways:

  • Evaluation frameworks should be established before deciding to build custom AI models.
  • Foundation models often require domain-specific fine-tuning to solve specialized business problems.
  • Business outcomes matter more than benchmark scores when evaluating AI systems.
  • High-quality, representative datasets are critical to successful production AI.
  • Hybrid AI architectures can outperform relying on a single foundation model.
  • Customer collaboration plays a key role in improving enterprise AI performance.
  • Privacy-preserving machine learning enables AI improvements while protecting sensitive user data.
  • AI benchmarks should complement—not replace—real-world product evaluation.
  • Engineering leaders must balance technical performance with customer value and business objectives.
  • Successful AI products are built through disciplined engineering, continuous evaluation, and strong data strategies.

Connect with Mona Chitnis:

LinkedIn: linkedin.com/in/monachitnis

Company: Boon

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, and scalable software engineering.

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Mona Chitnis, engineering leader at Boon and former engineering manager at Apple, to discuss one of the most important AI engineering decisions facing modern software teams: knowing when foundation models are no longer enough for production use.

Working on AI systems for the commercial construction industry, Mona quickly realized that general-purpose foundation models struggled to accurately understand complex construction plans and domain-specific workflows. Rather than immediately building custom models, her team first invested in developing a comprehensive evaluation framework to identify performance gaps, measure business outcomes, and determine whether fine-tuning proprietary models would deliver meaningful improvements.

One of Mona's most significant engineering decisions was choosing to build a hybrid AI architecture instead of relying entirely on off-the-shelf foundation models. By combining proprietary computer vision models with large language models, her team created a system capable of understanding construction documents, extracting measurements, and helping customers generate more accurate project estimates. She explains why data quality, customer collaboration, and continuous evaluation ultimately proved more valuable than simply adopting larger or newer AI models.

The conversation also explores Mona's experience leading privacy-preserving machine learning initiatives at Apple, where federated learning enabled AI models to improve without collecting sensitive user data. She discusses why enterprise AI success depends on representative datasets, thoughtful evaluation frameworks, and engineering systems designed around real customer outcomes rather than benchmark performance alone.

For engineering leaders building AI products in specialized or regulated industries, this episode offers practical lessons on evaluation strategy, production AI architecture, data quality, privacy-preserving machine learning, and building AI systems that deliver measurable business value.

Key Takeaways:

  • Evaluation frameworks should be established before deciding to build custom AI models.
  • Foundation models often require domain-specific fine-tuning to solve specialized business problems.
  • Business outcomes matter more than benchmark scores when evaluating AI systems.
  • High-quality, representative datasets are critical to successful production AI.
  • Hybrid AI architectures can outperform relying on a single foundation model.
  • Customer collaboration plays a key role in improving enterprise AI performance.
  • Privacy-preserving machine learning enables AI improvements while protecting sensitive user data.
  • AI benchmarks should complement—not replace—real-world product evaluation.
  • Engineering leaders must balance technical performance with customer value and business objectives.
  • Successful AI products are built through disciplined engineering, continuous evaluation, and strong data strategies.

Connect with Mona Chitnis:

LinkedIn: linkedin.com/in/monachitnis

Company: Boon

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, and scalable software engineering.

]]>13904719-893f-4a90-bc86-962869b20151Fri, 31 Jul 2026 06:00:00 -040017:14falsefullHow Hal Eisen Led a High-Stakes PCI Migration Under an Impossible DeadlineHow Hal Eisen Led a High-Stakes PCI Migration Under an Impossible DeadlineEpisode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Hal Eisen, engineering leader and technology executive, to discuss one of the most challenging infrastructure decisions of his career: leading a company-wide PCI compliance initiative under an aggressive six-month deadline after the business had already committed to a major enterprise customer.

With no prior experience leading a PCI compliance project, Hal began by learning the standards from the ground up before systematically mapping every system, identifying security risks, and designing an architecture capable of protecting sensitive payment data. Rather than immediately writing code, he invested heavily in understanding the regulatory landscape, consulting compliance experts, and building a shared framework that allowed engineering teams across the organization to understand the migration strategy.

One of the project's most controversial decisions was choosing a "big bang" migration instead of the incremental approach most engineering teams naturally preferred. Although incremental migrations typically reduce risk, Hal realized that the complexity of tightly coupled legacy systems and the aggressive business deadline made that approach impossible. Through extensive planning, detailed migration playbooks, sandbox testing, and multiple rehearsal runs, his team successfully transitioned the platform while minimizing operational disruption.

The conversation also explores how AI is changing software engineering. Hal shares how recreating a document redaction service with ChatGPT in under thirty minutes fundamentally changed his perspective on AI-assisted development. He explains why senior engineers consistently achieve better results with AI, why engineering judgment remains irreplaceable, and why Agile principles continue to matter even as AI dramatically accelerates software development.

For engineering leaders managing compliance initiatives, large-scale infrastructure migrations, and AI-enabled development teams, this episode offers practical lessons on balancing risk, planning, technical leadership, and long-term engineering success.

Key Takeaways:

  • Successful compliance initiatives begin with deeply understanding the regulatory requirements before implementing technical solutions.
  • Visual architecture models and shared language help align engineering teams during complex infrastructure migrations.
  • Big bang migrations can be the right decision when business constraints make incremental approaches impractical.
  • Thorough planning, rehearsals, and migration playbooks significantly reduce operational risk during major system cutovers.
  • Strong communication and stakeholder alignment are just as important as technical implementation.
  • AI dramatically accelerates software development but still requires experienced engineering judgment.
  • Senior engineers achieve better AI outcomes because they understand architectural trade-offs and code quality.
  • Engineering leaders remain accountable for AI-generated software and the business decisions behind it.
  • Agile principles continue to deliver value even as AI transforms software development workflows.
  • Engineering success depends on optimizing for business outcomes, not simply writing code faster.

Connect with Hal J Eisen:


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, and scalable software engineering.

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Hal Eisen, engineering leader and technology executive, to discuss one of the most challenging infrastructure decisions of his career: leading a company-wide PCI compliance initiative under an aggressive six-month deadline after the business had already committed to a major enterprise customer.

With no prior experience leading a PCI compliance project, Hal began by learning the standards from the ground up before systematically mapping every system, identifying security risks, and designing an architecture capable of protecting sensitive payment data. Rather than immediately writing code, he invested heavily in understanding the regulatory landscape, consulting compliance experts, and building a shared framework that allowed engineering teams across the organization to understand the migration strategy.

One of the project's most controversial decisions was choosing a "big bang" migration instead of the incremental approach most engineering teams naturally preferred. Although incremental migrations typically reduce risk, Hal realized that the complexity of tightly coupled legacy systems and the aggressive business deadline made that approach impossible. Through extensive planning, detailed migration playbooks, sandbox testing, and multiple rehearsal runs, his team successfully transitioned the platform while minimizing operational disruption.

The conversation also explores how AI is changing software engineering. Hal shares how recreating a document redaction service with ChatGPT in under thirty minutes fundamentally changed his perspective on AI-assisted development. He explains why senior engineers consistently achieve better results with AI, why engineering judgment remains irreplaceable, and why Agile principles continue to matter even as AI dramatically accelerates software development.

For engineering leaders managing compliance initiatives, large-scale infrastructure migrations, and AI-enabled development teams, this episode offers practical lessons on balancing risk, planning, technical leadership, and long-term engineering success.

Key Takeaways:

  • Successful compliance initiatives begin with deeply understanding the regulatory requirements before implementing technical solutions.
  • Visual architecture models and shared language help align engineering teams during complex infrastructure migrations.
  • Big bang migrations can be the right decision when business constraints make incremental approaches impractical.
  • Thorough planning, rehearsals, and migration playbooks significantly reduce operational risk during major system cutovers.
  • Strong communication and stakeholder alignment are just as important as technical implementation.
  • AI dramatically accelerates software development but still requires experienced engineering judgment.
  • Senior engineers achieve better AI outcomes because they understand architectural trade-offs and code quality.
  • Engineering leaders remain accountable for AI-generated software and the business decisions behind it.
  • Agile principles continue to deliver value even as AI transforms software development workflows.
  • Engineering success depends on optimizing for business outcomes, not simply writing code faster.

Connect with Hal J Eisen:


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, and scalable software engineering.

]]>9d8a2bd6-0f0c-4b3e-acad-633d3e412dc0Wed, 22 Jul 2026 06:00:00 -040017:06falsefullHow Stephen Seidel Transformed Manual Debt Collection Operations with AI, Low-Code Automation, and Better Data WorkflowsHow Stephen Seidel Transformed Manual Debt Collection Operations with AI, Low-Code Automation, and Better Data WorkflowsEpisode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Stephen Seidel, technology executive and operational transformation leader, to discuss why modern software platforms fail without standardized data and scalable operational processes.

After joining an organization that had recently migrated to a modern SaaS debt collection platform, Stephen discovered that the technology itself wasn't the problem. Despite investing in a powerful platform, inconsistent data, fragmented document storage, manual workflows, and decades-old operational habits prevented the organization from taking advantage of automation. Millions of documents were trapped across disconnected systems, making portfolio onboarding slow, expensive, and nearly impossible to scale.

Rather than building custom software from scratch, Stephen made the strategic decision to redesign the organization's entire data ingestion process using low-code automation and AI-powered document processing. By introducing automated OCR, intelligent document classification, standardized naming conventions, and integrated workflows, his team transformed a process that previously required weeks of manual effort into one that could be completed in less than 24 hours while dramatically improving operational visibility.

The conversation explores why operational transformation is often more challenging than technology implementation. Stephen explains how executive buy-in, process standardization, and thoughtful vendor selection became just as important as the technology itself. He also discusses why organizations should evaluate build-versus-buy decisions based on their own operational realities rather than following industry trends.

For engineering leaders modernizing legacy operations, this episode offers practical lessons on balancing low-code platforms, AI automation, operational change management, and long-term scalability while making engineering decisions that deliver measurable business value.

Key Takeaways:

  • Modern software platforms cannot deliver value without consistent, standardized data.
  • Operational processes are often just as important as technology when scaling enterprise systems.
  • Low-code platforms can accelerate digital transformation when engineering resources are limited.
  • AI-powered OCR and document processing dramatically reduce manual data ingestion and improve accuracy.
  • Standardized document naming and structured data enable downstream automation and reporting.
  • Build-versus-buy decisions should consider long-term maintenance, staffing, infrastructure costs, and operational risk.
  • Executive sponsorship is critical for driving successful organizational change.
  • Automating manual workflows can significantly reduce processing time while accelerating business ROI.
  • Vendor partnerships can reduce technical debt and allow engineering teams to focus on business outcomes.
  • Sustainable growth requires organizations to rethink legacy processes rather than simply modernizing existing technology.

Connect with Stephen Seidel:


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, and scalable software engineering.

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Stephen Seidel, technology executive and operational transformation leader, to discuss why modern software platforms fail without standardized data and scalable operational processes.

After joining an organization that had recently migrated to a modern SaaS debt collection platform, Stephen discovered that the technology itself wasn't the problem. Despite investing in a powerful platform, inconsistent data, fragmented document storage, manual workflows, and decades-old operational habits prevented the organization from taking advantage of automation. Millions of documents were trapped across disconnected systems, making portfolio onboarding slow, expensive, and nearly impossible to scale.

Rather than building custom software from scratch, Stephen made the strategic decision to redesign the organization's entire data ingestion process using low-code automation and AI-powered document processing. By introducing automated OCR, intelligent document classification, standardized naming conventions, and integrated workflows, his team transformed a process that previously required weeks of manual effort into one that could be completed in less than 24 hours while dramatically improving operational visibility.

The conversation explores why operational transformation is often more challenging than technology implementation. Stephen explains how executive buy-in, process standardization, and thoughtful vendor selection became just as important as the technology itself. He also discusses why organizations should evaluate build-versus-buy decisions based on their own operational realities rather than following industry trends.

For engineering leaders modernizing legacy operations, this episode offers practical lessons on balancing low-code platforms, AI automation, operational change management, and long-term scalability while making engineering decisions that deliver measurable business value.

Key Takeaways:

  • Modern software platforms cannot deliver value without consistent, standardized data.
  • Operational processes are often just as important as technology when scaling enterprise systems.
  • Low-code platforms can accelerate digital transformation when engineering resources are limited.
  • AI-powered OCR and document processing dramatically reduce manual data ingestion and improve accuracy.
  • Standardized document naming and structured data enable downstream automation and reporting.
  • Build-versus-buy decisions should consider long-term maintenance, staffing, infrastructure costs, and operational risk.
  • Executive sponsorship is critical for driving successful organizational change.
  • Automating manual workflows can significantly reduce processing time while accelerating business ROI.
  • Vendor partnerships can reduce technical debt and allow engineering teams to focus on business outcomes.
  • Sustainable growth requires organizations to rethink legacy processes rather than simply modernizing existing technology.

Connect with Stephen Seidel:


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, and scalable software engineering.

]]>3b8cc684-a7bd-4270-824a-798fb7569271Mon, 20 Jul 2026 06:00:00 -040017:38falsefullHow Derek Gallo Defended "Good Enough" Quality to Scale AI Video ProductionHow Derek Gallo Defended "Good Enough" Quality to Scale AI Video ProductionEpisode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Derek Gallo, a technology leader working at the intersection of product delivery, operations, and AI-enabled content production, to discuss why scaling AI isn't always about generating more content, it's about designing smarter review systems.

As AI dramatically accelerated the production of educational videos, Derek's team quickly discovered that content generation was no longer the bottleneck. Instead, endless review cycles became the biggest obstacle. Because AI video editing regenerates an entire video rather than modifying individual sections, every revision introduced the risk of creating entirely new issues, trapping the team in an expensive and time-consuming feedback loop.

Rather than pursuing perfect quality, Derek led the team toward a more structured production workflow built around review rubrics, measurable quality standards, and data-driven capacity planning. By distinguishing between critical issues that required immediate correction and minor imperfections that could safely be deferred, the team significantly increased throughput while maintaining the quality standards that mattered most to their audience.

The conversation also explores how traditional software engineering practices including Agile planning, burndown tracking, lead-time analysis, and backlog management can successfully be applied to AI-powered content production. Derek explains why AI should augment, not replace, human reviewers, particularly for legal, copyright, trademark, and strategic content decisions where judgment remains essential.

For engineering leaders building AI-driven production pipelines, this episode offers practical lessons on balancing quality with delivery speed, using metrics to guide engineering decisions, and building scalable review systems that keep humans focused on the decisions that matter most.

Key Takeaways:

  • AI often shifts bottlenecks from content creation to review and quality assurance.
  • Structured review rubrics reduce unnecessary revision cycles while maintaining meaningful quality standards.
  • Distinguishing between critical defects and minor imperfections improves production throughput.
  • Software engineering practices such as Agile planning, burndown charts, and lead-time analysis can improve AI production workflows.
  • Measuring revision cycles helps identify where production pipelines become inefficient.
  • AI-assisted reviews can automate repetitive validation tasks while humans retain responsibility for high-risk decisions.
  • Human oversight remains essential for copyright, trademark, legal, and strategic content reviews.
  • AI functions best as an intelligent assistant rather than a fully autonomous reviewer.
  • Organizations achieve better AI adoption by investing in employee training instead of simply providing AI tools.
  • Perfect quality loses value if it prevents products from ever reaching customers.

Connect with Derek Gallo:


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, scalable software engineering, and the trade-offs engineering leaders make in high-stakes environments.

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Derek Gallo, a technology leader working at the intersection of product delivery, operations, and AI-enabled content production, to discuss why scaling AI isn't always about generating more content, it's about designing smarter review systems.

As AI dramatically accelerated the production of educational videos, Derek's team quickly discovered that content generation was no longer the bottleneck. Instead, endless review cycles became the biggest obstacle. Because AI video editing regenerates an entire video rather than modifying individual sections, every revision introduced the risk of creating entirely new issues, trapping the team in an expensive and time-consuming feedback loop.

Rather than pursuing perfect quality, Derek led the team toward a more structured production workflow built around review rubrics, measurable quality standards, and data-driven capacity planning. By distinguishing between critical issues that required immediate correction and minor imperfections that could safely be deferred, the team significantly increased throughput while maintaining the quality standards that mattered most to their audience.

The conversation also explores how traditional software engineering practices including Agile planning, burndown tracking, lead-time analysis, and backlog management can successfully be applied to AI-powered content production. Derek explains why AI should augment, not replace, human reviewers, particularly for legal, copyright, trademark, and strategic content decisions where judgment remains essential.

For engineering leaders building AI-driven production pipelines, this episode offers practical lessons on balancing quality with delivery speed, using metrics to guide engineering decisions, and building scalable review systems that keep humans focused on the decisions that matter most.

Key Takeaways:

  • AI often shifts bottlenecks from content creation to review and quality assurance.
  • Structured review rubrics reduce unnecessary revision cycles while maintaining meaningful quality standards.
  • Distinguishing between critical defects and minor imperfections improves production throughput.
  • Software engineering practices such as Agile planning, burndown charts, and lead-time analysis can improve AI production workflows.
  • Measuring revision cycles helps identify where production pipelines become inefficient.
  • AI-assisted reviews can automate repetitive validation tasks while humans retain responsibility for high-risk decisions.
  • Human oversight remains essential for copyright, trademark, legal, and strategic content reviews.
  • AI functions best as an intelligent assistant rather than a fully autonomous reviewer.
  • Organizations achieve better AI adoption by investing in employee training instead of simply providing AI tools.
  • Perfect quality loses value if it prevents products from ever reaching customers.

Connect with Derek Gallo:


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, scalable software engineering, and the trade-offs engineering leaders make in high-stakes environments.

]]>bcc4b62c-6192-4697-8d4b-ac58991aca3cFri, 17 Jul 2026 06:00:00 -040018:26falsefullHow Chris Dunkel Balanced No-Code Speed, Compliance, and Enterprise Scale Before AI Changed Software DevelopmentHow Chris Dunkel Balanced No-Code Speed, Compliance, and Enterprise Scale Before AI Changed Software DevelopmentEpisode 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:


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.

]]>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:


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.

]]>99f41738-aeb6-4096-bdf4-2e64e43c130dWed, 15 Jul 2026 06:00:00 -040017:23falsefull“How Ankur Mattoo Built the AI Foundations That Made Enterprise Machine Learning Scalable”“How Ankur Mattoo Built the AI Foundations That Made Enterprise Machine Learning Scalable”Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Ankur Mattoo, technology leader, architect, and AI practitioner, to discuss why the most successful AI initiatives begin years before generative AI ever reaches production.

While helping build the machine learning foundation at Iterable, Ankur faced a challenge common to many fast-growing SaaS companies: enormous amounts of customer data with little consistency. Serving enterprise customers across industries including DoorDash, Spotify, Zillow, and many others, the platform collected highly diverse datasets that were invaluable for marketers—but extremely difficult to transform into scalable machine learning systems.

Rather than rushing to deliver ambitious AI products, Ankur made the strategic decision to invest in foundational infrastructure first. By introducing an incremental product strategy through a feature called Brand Affinity, his team demonstrated immediate business value while quietly building the feature engineering pipelines, machine learning platform, and data foundation that would later support far more advanced AI capabilities.

The conversation explores why strong data architecture, feature stores, and semantic understanding remain essential for successful AI deployments—even in the era of large language models. Ankur explains why organizations that skip foundational investments often struggle to deliver meaningful AI outcomes, while those that balance short-term wins with long-term infrastructure create lasting competitive advantages.

For engineering leaders building AI platforms, this episode offers practical lessons on earning organizational trust, scaling machine learning across complex enterprise environments, and making engineering decisions that continue paying dividends years later.

Key Takeaways:

  • Successful AI products are built on strong data foundations rather than AI models alone
  • Incremental product wins help secure organizational trust for long-term infrastructure investments
  • Diverse customer data requires scalable feature engineering instead of customer-specific machine learning models
  • Feature stores create reusable signals that accelerate future AI capabilities
  • Enterprise AI success depends on semantic understanding and high-quality data pipelines
  • Large language models are only as valuable as the data they can access
  • Engineering leaders should balance short-term product delivery with long-term architectural investments
  • Building AI infrastructure iteratively reduces technical and organizational risk
  • Strong data architecture enables future AI innovation long before it becomes visible to customers
  • Curiosity and continuous learning remain essential as AI technologies continue evolving

Connect with Ankur Mattoo:

LinkedIn: linkedin.com/in/ankurmattoo

Website: capgemini.com

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, and scalable software engineering.

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Ankur Mattoo, technology leader, architect, and AI practitioner, to discuss why the most successful AI initiatives begin years before generative AI ever reaches production.

While helping build the machine learning foundation at Iterable, Ankur faced a challenge common to many fast-growing SaaS companies: enormous amounts of customer data with little consistency. Serving enterprise customers across industries including DoorDash, Spotify, Zillow, and many others, the platform collected highly diverse datasets that were invaluable for marketers—but extremely difficult to transform into scalable machine learning systems.

Rather than rushing to deliver ambitious AI products, Ankur made the strategic decision to invest in foundational infrastructure first. By introducing an incremental product strategy through a feature called Brand Affinity, his team demonstrated immediate business value while quietly building the feature engineering pipelines, machine learning platform, and data foundation that would later support far more advanced AI capabilities.

The conversation explores why strong data architecture, feature stores, and semantic understanding remain essential for successful AI deployments—even in the era of large language models. Ankur explains why organizations that skip foundational investments often struggle to deliver meaningful AI outcomes, while those that balance short-term wins with long-term infrastructure create lasting competitive advantages.

For engineering leaders building AI platforms, this episode offers practical lessons on earning organizational trust, scaling machine learning across complex enterprise environments, and making engineering decisions that continue paying dividends years later.

Key Takeaways:

  • Successful AI products are built on strong data foundations rather than AI models alone
  • Incremental product wins help secure organizational trust for long-term infrastructure investments
  • Diverse customer data requires scalable feature engineering instead of customer-specific machine learning models
  • Feature stores create reusable signals that accelerate future AI capabilities
  • Enterprise AI success depends on semantic understanding and high-quality data pipelines
  • Large language models are only as valuable as the data they can access
  • Engineering leaders should balance short-term product delivery with long-term architectural investments
  • Building AI infrastructure iteratively reduces technical and organizational risk
  • Strong data architecture enables future AI innovation long before it becomes visible to customers
  • Curiosity and continuous learning remain essential as AI technologies continue evolving

Connect with Ankur Mattoo:

LinkedIn: linkedin.com/in/ankurmattoo

Website: capgemini.com

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, and scalable software engineering.

]]>4bc459bb-601d-4861-a8ad-50a9b13c637aWed, 01 Jul 2026 05:00:00 -040017:30falsefull“How Gautamdev (Gautam) Chowdary Built Healthcare AI That Prioritizes Interoperability, Reliability, and Trust at Scale”“How Gautamdev (Gautam) Chowdary Built Healthcare AI That Prioritizes Interoperability, Reliability, and Trust at Scale”Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Gautamdev (Gautam) Chowdary, Co-Founder and CTO of Zynix AI, to discuss one of healthcare AI's most difficult engineering challenges: building intelligent systems that work reliably across fragmented healthcare environments.

Rather than optimizing for a single electronic medical record (EMR) platform, Gautam and his team made the difficult architectural decision to build an EMR-agnostic platform from day one. Serving healthcare organizations that may operate hundreds or even thousands of EMR instances, Zynix AI, focuses on automating care coordination, scheduling, outreach, documentation, and operational workflows across highly fragmented systems.

The conversation explores why interoperability should be treated as a reliability problem instead of simply an API integration challenge. Gautam explains how healthcare workflows extend far beyond structured APIs, requiring intelligent automation through robotic process automation (RPA), adaptive AI agents, and resilient workflow orchestration capable of handling real-world operational complexity.

A major focus of the discussion is the balance between AI automation and human oversight. Rather than replacing healthcare professionals, Zynix AI, uses confidence thresholds, governance, and human checkpoints to ensure sensitive clinical and operational decisions remain accountable while AI eliminates repetitive administrative work.

For engineering leaders building AI systems in regulated industries, this episode offers valuable lessons on designing deployable architectures, building trust into AI systems, and creating operationally resilient platforms that succeed in production—not just in demonstrations.

Key Takeaways:

  • Interoperability should be treated as an operational reliability problem, not simply an API integration project
  • Building EMR-agnostic architecture creates long-term scalability across fragmented healthcare environments
  • Healthcare AI must integrate with multiple systems beyond EMRs, including telephony, fax, scheduling, and manual workflows
  • AI-powered RPA creates more resilient automation by adapting to changing interfaces and operational variability
  • Human oversight remains essential for clinical ambiguity, regulatory accountability, and low-confidence AI decisions
  • Infrastructure flexibility is critical for healthcare organizations with varying compliance and deployment requirements
  • Deployable architecture often matters more than model sophistication in healthcare AI
  • Trust, governance, and operational reliability drive adoption more than raw AI performance
  • Engineering teams should optimize for production reliability rather than polished demonstrations
  • Successful healthcare AI platforms are built to survive operational complexity at scale

Connect with Gautamdev (Gautam) Chowdary:

LinkedIn: https://www.linkedin.com/in/cgautamdevc/

Website: ZYNIX.ai

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, and scalable software engineering.

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Gautamdev (Gautam) Chowdary, Co-Founder and CTO of Zynix AI, to discuss one of healthcare AI's most difficult engineering challenges: building intelligent systems that work reliably across fragmented healthcare environments.

Rather than optimizing for a single electronic medical record (EMR) platform, Gautam and his team made the difficult architectural decision to build an EMR-agnostic platform from day one. Serving healthcare organizations that may operate hundreds or even thousands of EMR instances, Zynix AI, focuses on automating care coordination, scheduling, outreach, documentation, and operational workflows across highly fragmented systems.

The conversation explores why interoperability should be treated as a reliability problem instead of simply an API integration challenge. Gautam explains how healthcare workflows extend far beyond structured APIs, requiring intelligent automation through robotic process automation (RPA), adaptive AI agents, and resilient workflow orchestration capable of handling real-world operational complexity.

A major focus of the discussion is the balance between AI automation and human oversight. Rather than replacing healthcare professionals, Zynix AI, uses confidence thresholds, governance, and human checkpoints to ensure sensitive clinical and operational decisions remain accountable while AI eliminates repetitive administrative work.

For engineering leaders building AI systems in regulated industries, this episode offers valuable lessons on designing deployable architectures, building trust into AI systems, and creating operationally resilient platforms that succeed in production—not just in demonstrations.

Key Takeaways:

  • Interoperability should be treated as an operational reliability problem, not simply an API integration project
  • Building EMR-agnostic architecture creates long-term scalability across fragmented healthcare environments
  • Healthcare AI must integrate with multiple systems beyond EMRs, including telephony, fax, scheduling, and manual workflows
  • AI-powered RPA creates more resilient automation by adapting to changing interfaces and operational variability
  • Human oversight remains essential for clinical ambiguity, regulatory accountability, and low-confidence AI decisions
  • Infrastructure flexibility is critical for healthcare organizations with varying compliance and deployment requirements
  • Deployable architecture often matters more than model sophistication in healthcare AI
  • Trust, governance, and operational reliability drive adoption more than raw AI performance
  • Engineering teams should optimize for production reliability rather than polished demonstrations
  • Successful healthcare AI platforms are built to survive operational complexity at scale

Connect with Gautamdev (Gautam) Chowdary:

LinkedIn: https://www.linkedin.com/in/cgautamdevc/

Website: ZYNIX.ai

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, and scalable software engineering.

]]>f5c9de12-0c6d-4fe5-baf6-165545cedcf0Tue, 30 Jun 2026 05:00:00 -040014:24falsefull“How Eban Bisong Transformed Engineers into AI Orchestrators to Eliminate Delivery Bottlenecks”“How Eban Bisong Transformed Engineers into AI Orchestrators to Eliminate Delivery Bottlenecks”Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Eban Bisong to discuss how AI-native workflows are reshaping software engineering teams and changing what it means to be an engineer.

While leading engineering at Part DNA, Eban faced a challenge familiar to many growing organizations: a small team supporting multiple clients, constant context switching, increasing delivery demands, and pressure to maintain quality while moving faster. Traditional approaches were no longer enough.

Rather than simply introducing AI coding tools, Eban led a broader organizational transformation that redefined how work moved through the company. By integrating AI agents into engineering, support, documentation, ticket creation, code review, testing, and knowledge management workflows, the team dramatically reduced operational bottlenecks and increased delivery capacity without increasing headcount.

A key part of the transformation was the introduction of an AI teammate named R2-D2, powered by OpenClaw. Initially deployed as a refactoring and code-quality agent, R2-D2 evolved into a company-wide knowledge assistant capable of supporting engineering, customer support, documentation, and operational workflows. The result was a system where AI handled repetitive execution tasks while humans focused on judgment, architecture, customer conversations, and product strategy.

The conversation explores how engineering roles are evolving from writing code to orchestrating systems that generate code, why specification quality is becoming more important than technical implementation, and how organizations can build AI-native processes that improve both speed and quality.

For engineering leaders, this episode offers a practical framework for moving beyond AI experimentation and building organizations where humans and agents work together to create scalable, high-performing engineering systems.

Key Takeaways:

• AI adoption requires a mindset shift, not just new tools

• Engineers are increasingly becoming orchestrators rather than code producers

• AI agents can eliminate context-switching bottlenecks across organizations

• Knowledge management and specifications are critical for successful AI workflows

• Support, documentation, and engineering processes can all benefit from AI automation

• Verification systems must scale alongside development velocity

• AI agents should be separated across testing and implementation workflows

• Product thinking and systems thinking are becoming more valuable than framework expertise

• Organizations should optimize for judgment and decision-making, not manual execution

• Successful AI-native teams focus on improving systems rather than fixing isolated problems

Connect with Eban Bisong:


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, and scalable software engineering.

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Eban Bisong to discuss how AI-native workflows are reshaping software engineering teams and changing what it means to be an engineer.

While leading engineering at Part DNA, Eban faced a challenge familiar to many growing organizations: a small team supporting multiple clients, constant context switching, increasing delivery demands, and pressure to maintain quality while moving faster. Traditional approaches were no longer enough.

Rather than simply introducing AI coding tools, Eban led a broader organizational transformation that redefined how work moved through the company. By integrating AI agents into engineering, support, documentation, ticket creation, code review, testing, and knowledge management workflows, the team dramatically reduced operational bottlenecks and increased delivery capacity without increasing headcount.

A key part of the transformation was the introduction of an AI teammate named R2-D2, powered by OpenClaw. Initially deployed as a refactoring and code-quality agent, R2-D2 evolved into a company-wide knowledge assistant capable of supporting engineering, customer support, documentation, and operational workflows. The result was a system where AI handled repetitive execution tasks while humans focused on judgment, architecture, customer conversations, and product strategy.

The conversation explores how engineering roles are evolving from writing code to orchestrating systems that generate code, why specification quality is becoming more important than technical implementation, and how organizations can build AI-native processes that improve both speed and quality.

For engineering leaders, this episode offers a practical framework for moving beyond AI experimentation and building organizations where humans and agents work together to create scalable, high-performing engineering systems.

Key Takeaways:

• AI adoption requires a mindset shift, not just new tools

• Engineers are increasingly becoming orchestrators rather than code producers

• AI agents can eliminate context-switching bottlenecks across organizations

• Knowledge management and specifications are critical for successful AI workflows

• Support, documentation, and engineering processes can all benefit from AI automation

• Verification systems must scale alongside development velocity

• AI agents should be separated across testing and implementation workflows

• Product thinking and systems thinking are becoming more valuable than framework expertise

• Organizations should optimize for judgment and decision-making, not manual execution

• Successful AI-native teams focus on improving systems rather than fixing isolated problems

Connect with Eban Bisong:


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, and scalable software engineering.

]]>d4dddc35-c05f-47f8-9b87-e641a529cd84Fri, 12 Jun 2026 09:00:00 -040015:32falsefull“How Pavel Spesivtsev Argues That Knowledge Infrastructure Matters More Than AI Models”“How Pavel Spesivtsev Argues That Knowledge Infrastructure Matters More Than AI Models”Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Pavel Spesivtsev, CTO, AI strategist, and agentic engineering practitioner, to explore why many AI-driven software initiatives fail long before coding becomes the problem.

After spending the last eighteen months helping organizations implement agentic development workflows, Pavel has observed a surprising pattern: the models themselves are rarely the weakest link. Instead, failures typically emerge from incomplete specifications, missing organizational knowledge, weak governance, and poor context management.

Pavel explains why traditional software development assumptions are being challenged by agentic engineering. While Agile methodologies were designed around human decision-making and implementation, AI agents require far more structured specifications and complete knowledge systems to operate effectively. When requirements contain gaps, agents fill them with assumptions drawn from training data, often leading to unexpected or incorrect outcomes.

The conversation explores Pavel’s concept of “Gap Trap,” a framework designed to identify missing requirements before they enter an agentic workflow. He also discusses why knowledge bases and ontologies are becoming critical infrastructure for AI-powered development, how retrieval systems can introduce hidden hallucination risks, and why context engineering is rapidly becoming one of the most valuable skills in modern software organizations.

Pavel shares his perspective on the evolution of software engineering roles as AI adoption accelerates. As implementation becomes increasingly automated, engineers are spending less time writing code and more time designing systems, orchestrating agents, validating outputs, and building the knowledge frameworks that guide intelligent systems toward reliable outcomes.

For engineering leaders, this episode highlights a major shift in software delivery: as coding becomes increasingly automated, competitive advantage will come from designing better systems, creating higher-quality specifications, and building the knowledge infrastructure that enables AI agents to make reliable decisions.

Key Takeaways:

• Most agentic AI project failures stem from specification and knowledge gaps, not model quality

• Incomplete requirements cause AI agents to make unpredictable assumptions

• Knowledge bases and ontologies are becoming critical infrastructure for AI systems

• Context engineering is emerging as a core engineering discipline

• Retrieval systems can introduce hidden hallucination risks when information is incomplete

• Software engineers are evolving from code authors into system architects and orchestrators

• Agentic workflows require stronger specification practices than traditional Agile processes

• Documentation is increasingly becoming operational infrastructure, not just reference material

• Governance, security, and knowledge management are essential for successful AI adoption

• Organizations should focus on knowledge quality before investing heavily in AI tooling

Connect with Pavel Spesivtsev:


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, and scalable software engineering.

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Pavel Spesivtsev, CTO, AI strategist, and agentic engineering practitioner, to explore why many AI-driven software initiatives fail long before coding becomes the problem.

After spending the last eighteen months helping organizations implement agentic development workflows, Pavel has observed a surprising pattern: the models themselves are rarely the weakest link. Instead, failures typically emerge from incomplete specifications, missing organizational knowledge, weak governance, and poor context management.

Pavel explains why traditional software development assumptions are being challenged by agentic engineering. While Agile methodologies were designed around human decision-making and implementation, AI agents require far more structured specifications and complete knowledge systems to operate effectively. When requirements contain gaps, agents fill them with assumptions drawn from training data, often leading to unexpected or incorrect outcomes.

The conversation explores Pavel’s concept of “Gap Trap,” a framework designed to identify missing requirements before they enter an agentic workflow. He also discusses why knowledge bases and ontologies are becoming critical infrastructure for AI-powered development, how retrieval systems can introduce hidden hallucination risks, and why context engineering is rapidly becoming one of the most valuable skills in modern software organizations.

Pavel shares his perspective on the evolution of software engineering roles as AI adoption accelerates. As implementation becomes increasingly automated, engineers are spending less time writing code and more time designing systems, orchestrating agents, validating outputs, and building the knowledge frameworks that guide intelligent systems toward reliable outcomes.

For engineering leaders, this episode highlights a major shift in software delivery: as coding becomes increasingly automated, competitive advantage will come from designing better systems, creating higher-quality specifications, and building the knowledge infrastructure that enables AI agents to make reliable decisions.

Key Takeaways:

• Most agentic AI project failures stem from specification and knowledge gaps, not model quality

• Incomplete requirements cause AI agents to make unpredictable assumptions

• Knowledge bases and ontologies are becoming critical infrastructure for AI systems

• Context engineering is emerging as a core engineering discipline

• Retrieval systems can introduce hidden hallucination risks when information is incomplete

• Software engineers are evolving from code authors into system architects and orchestrators

• Agentic workflows require stronger specification practices than traditional Agile processes

• Documentation is increasingly becoming operational infrastructure, not just reference material

• Governance, security, and knowledge management are essential for successful AI adoption

• Organizations should focus on knowledge quality before investing heavily in AI tooling

Connect with Pavel Spesivtsev:


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, and scalable software engineering.

]]>a7a3b7be-4382-4d4a-973a-1739d5993dfeThu, 11 Jun 2026 09:00:00 -040019:34falsefull"How Paul Baker Stopped Feature Development to Save Engineering Velocity""How Paul Baker Stopped Feature Development to Save Engineering Velocity"Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Paul Baker to discuss one of the most difficult decisions an engineering leader can make: stopping feature development in order to rebuild the engineering foundation.

While working at Capshare, Paul inherited a growing product with strong market traction but a fragile engineering system plagued by regressions, manual testing, multi-day deployments, and the absence of automated quality controls. Faced with mounting production issues and increasing customer risk, Paul proposed an unconventional solution: pause all new feature development for an entire quarter and focus exclusively on improving software quality, testing, and deployment infrastructure.

Paul shares how the team implemented automated testing, continuous integration, and systematic refactoring strategies to transform a legacy codebase into a maintainable platform capable of supporting future growth. He explains why engineering foundations are often the true drivers of delivery velocity and how technical debt can quietly undermine even successful products.

The conversation also explores the evolving role of AI in software development, including the use of LLMs to accelerate legacy system modernization, generate large-scale test suites, and support engineering workflows. Paul offers practical insights into the limitations of agentic coding systems, the importance of prompt accuracy, and why human oversight remains essential as AI-assisted development becomes more common.

For engineering leaders, this episode provides a powerful reminder that sustainable innovation depends on confidence in deployment, disciplined engineering practices, and investing in the foundations that make rapid delivery possible.

Key Takeaways:

• Engineering velocity depends on strong testing and deployment foundations

• Pausing feature development can sometimes accelerate long-term delivery

• Automated testing reduces production regressions and deployment risk

• Legacy systems can be modernized through incremental refactoring strategies

• Continuous integration creates confidence in software changes

• Golden master testing can help stabilize complex legacy applications

• AI can dramatically accelerate test generation and modernization efforts

• Agentic coding systems still require human guidance and oversight

• Deployment anxiety often reveals gaps in engineering infrastructure

• Successful engineering organizations continuously invest in foundational quality

Connect with Paul Baker:


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, and scalable software engineering.

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Paul Baker to discuss one of the most difficult decisions an engineering leader can make: stopping feature development in order to rebuild the engineering foundation.

While working at Capshare, Paul inherited a growing product with strong market traction but a fragile engineering system plagued by regressions, manual testing, multi-day deployments, and the absence of automated quality controls. Faced with mounting production issues and increasing customer risk, Paul proposed an unconventional solution: pause all new feature development for an entire quarter and focus exclusively on improving software quality, testing, and deployment infrastructure.

Paul shares how the team implemented automated testing, continuous integration, and systematic refactoring strategies to transform a legacy codebase into a maintainable platform capable of supporting future growth. He explains why engineering foundations are often the true drivers of delivery velocity and how technical debt can quietly undermine even successful products.

The conversation also explores the evolving role of AI in software development, including the use of LLMs to accelerate legacy system modernization, generate large-scale test suites, and support engineering workflows. Paul offers practical insights into the limitations of agentic coding systems, the importance of prompt accuracy, and why human oversight remains essential as AI-assisted development becomes more common.

For engineering leaders, this episode provides a powerful reminder that sustainable innovation depends on confidence in deployment, disciplined engineering practices, and investing in the foundations that make rapid delivery possible.

Key Takeaways:

• Engineering velocity depends on strong testing and deployment foundations

• Pausing feature development can sometimes accelerate long-term delivery

• Automated testing reduces production regressions and deployment risk

• Legacy systems can be modernized through incremental refactoring strategies

• Continuous integration creates confidence in software changes

• Golden master testing can help stabilize complex legacy applications

• AI can dramatically accelerate test generation and modernization efforts

• Agentic coding systems still require human guidance and oversight

• Deployment anxiety often reveals gaps in engineering infrastructure

• Successful engineering organizations continuously invest in foundational quality

Connect with Paul Baker:


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, and scalable software engineering.

]]>8bf262da-c029-4806-8bf9-2285929467ddWed, 10 Jun 2026 09:00:00 -040023:54falsefull“How Alexander Smirnoff Built Practical Enterprise AI Systems by Combining GenAI with Traditional NLP”“How Alexander Smirnoff Built Practical Enterprise AI Systems by Combining GenAI with Traditional NLP”Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Alex Smirnoff to explore how enterprise AI systems can deliver real business value without replacing the proven infrastructure that already works.

At Luminoso, Alex has spent years building large-scale NLP and text analytics systems that help enterprises analyze customer reviews, semantic search data, and large document collections. When generative AI rapidly entered the market, the company faced pressure from customers and stakeholders to “AI everything” overnight.

Instead of rebuilding the platform around large language models, Luminoso chose a hybrid architecture that combined traditional NLP algorithms, semantic search, classification systems, and retrieval pipelines with modern GenAI reasoning capabilities. Alex explains why many older NLP tools still outperform LLMs for specific tasks like classification and keyword extraction, and how GenAI works best as an intelligent reasoning layer on top of existing systems.

The conversation also explores hallucinations in enterprise environments, RAG pipeline design, grounding responses in source data, and the growing gap between flashy AI demos and production-ready enterprise systems.

For engineering leaders, this episode highlights an important lesson: practical AI systems are rarely built by replacing everything — they succeed by combining proven infrastructure with new reasoning capabilities in thoughtful, cost-effective ways.

Key Takeaways:

  • Traditional NLP tools still outperform LLMs for many specialized tasks
  • GenAI works best as a reasoning layer on top of existing systems
  • Hybrid AI architectures reduce cost and improve scalability
  • Enterprise AI systems must ground responses in customer data
  • RAG pipelines require careful tuning and retrieval quality management
  • Hallucination control is critical in business environments
  • There is a major gap between AI demos and production systems
  • Replacing entire platforms with GenAI often creates unnecessary complexity
  • Engineering teams should focus on business use cases, not AI hype
  • Successful AI adoption requires experienced implementation and planning

Connect with Alex Smirnoff:


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, and scalable software engineering.

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Alex Smirnoff to explore how enterprise AI systems can deliver real business value without replacing the proven infrastructure that already works.

At Luminoso, Alex has spent years building large-scale NLP and text analytics systems that help enterprises analyze customer reviews, semantic search data, and large document collections. When generative AI rapidly entered the market, the company faced pressure from customers and stakeholders to “AI everything” overnight.

Instead of rebuilding the platform around large language models, Luminoso chose a hybrid architecture that combined traditional NLP algorithms, semantic search, classification systems, and retrieval pipelines with modern GenAI reasoning capabilities. Alex explains why many older NLP tools still outperform LLMs for specific tasks like classification and keyword extraction, and how GenAI works best as an intelligent reasoning layer on top of existing systems.

The conversation also explores hallucinations in enterprise environments, RAG pipeline design, grounding responses in source data, and the growing gap between flashy AI demos and production-ready enterprise systems.

For engineering leaders, this episode highlights an important lesson: practical AI systems are rarely built by replacing everything — they succeed by combining proven infrastructure with new reasoning capabilities in thoughtful, cost-effective ways.

Key Takeaways:

  • Traditional NLP tools still outperform LLMs for many specialized tasks
  • GenAI works best as a reasoning layer on top of existing systems
  • Hybrid AI architectures reduce cost and improve scalability
  • Enterprise AI systems must ground responses in customer data
  • RAG pipelines require careful tuning and retrieval quality management
  • Hallucination control is critical in business environments
  • There is a major gap between AI demos and production systems
  • Replacing entire platforms with GenAI often creates unnecessary complexity
  • Engineering teams should focus on business use cases, not AI hype
  • Successful AI adoption requires experienced implementation and planning

Connect with Alex Smirnoff:


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, and scalable software engineering.

]]>12cd213c-dd6d-4ecb-9e1d-6f8f7e865ed3Wed, 27 May 2026 09:00:00 -040026:27falsefull“How David Phipps Built AI-Powered Retail Systems by Prioritizing UX Over Feature Factories”“How David Phipps Built AI-Powered Retail Systems by Prioritizing UX Over Feature Factories”Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with David Phipps to explore how engineering teams can scale AI-powered retail systems without sacrificing usability, reliability, or operational simplicity.

Before joining Generation Tux, David helped build AI-driven digital signage and audience analytics systems that combined computer vision, edge computing, and point-of-sale integrations to measure customer engagement and advertising performance in physical retail environments.

David shares how the company faced a critical decision after years of accumulating feature requests that made the platform increasingly difficult to use. Instead of continuing to add more features, the team committed to a complete UX and platform overhaul focused on simplicity, scalability, and fleet management.

The conversation explores why usability became a competitive advantage, how Linux and Docker improved reliability at scale, and why AI-assisted development increases the importance of planning, architecture, and stakeholder alignment.

For engineering leaders, this episode highlights an important lesson: the most valuable engineering decisions are often the ones that reduce complexity instead of adding to it.

Key Takeaways:

  • UX and simplicity can outperform feature-heavy competitors
  • AI systems operating at the edge require reliability and low operational overhead
  • Feature factories often create long-term scalability problems
  • Managing large fleets requires strong architecture and automation
  • Stakeholder alignment is critical during platform redesigns
  • AI-assisted development increases the importance of planning and oversight
  • Simplifying workflows often creates more value than adding new features

Connect with David Phipps:


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, platform architecture, scalability, and engineering leadership.

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with David Phipps to explore how engineering teams can scale AI-powered retail systems without sacrificing usability, reliability, or operational simplicity.

Before joining Generation Tux, David helped build AI-driven digital signage and audience analytics systems that combined computer vision, edge computing, and point-of-sale integrations to measure customer engagement and advertising performance in physical retail environments.

David shares how the company faced a critical decision after years of accumulating feature requests that made the platform increasingly difficult to use. Instead of continuing to add more features, the team committed to a complete UX and platform overhaul focused on simplicity, scalability, and fleet management.

The conversation explores why usability became a competitive advantage, how Linux and Docker improved reliability at scale, and why AI-assisted development increases the importance of planning, architecture, and stakeholder alignment.

For engineering leaders, this episode highlights an important lesson: the most valuable engineering decisions are often the ones that reduce complexity instead of adding to it.

Key Takeaways:

  • UX and simplicity can outperform feature-heavy competitors
  • AI systems operating at the edge require reliability and low operational overhead
  • Feature factories often create long-term scalability problems
  • Managing large fleets requires strong architecture and automation
  • Stakeholder alignment is critical during platform redesigns
  • AI-assisted development increases the importance of planning and oversight
  • Simplifying workflows often creates more value than adding new features

Connect with David Phipps:


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, platform architecture, scalability, and engineering leadership.

]]>70a2b2cf-1115-48e2-952a-e19771231169Tue, 26 May 2026 09:00:00 -040024:32falsefull"How Matt Lievertz Built Privacy-First AI Coaching Systems by Treating Compliance as a Core Product Strategy""How Matt Lievertz Built Privacy-First AI Coaching Systems by Treating Compliance as a Core Product Strategy"Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Matt Lievertz, VP of Engineering at Cloverleaf, to explore how engineering teams can build AI-powered products that balance personalization, privacy, and enterprise trust.

Cloverleaf combines behavioral assessments, workplace communication data, and AI-driven insights to help teams improve collaboration and performance. But handling personality data, coaching interactions, and workplace integrations introduced major technical and ethical challenges around privacy, compliance, and system design.

Matt shares how a difficult enterprise compliance conversation in 2022 became a turning point for the company. Instead of treating privacy as a legal checkbox, Cloverleaf chose to build privacy protections directly into the architecture of the platform. That decision later positioned the company ahead of emerging regulations like GDPR, CCPA, and the EU AI Act.

The conversation also explores how AI systems increase the complexity of privacy engineering, why minimizing personally identifiable information is becoming critical for enterprise AI adoption, and how simplifying platform architecture unlocked both scalability and partner growth.

For engineering leaders, this episode highlights an important lesson: privacy and trust are no longer compliance features — they are foundational product decisions that directly impact scalability, enterprise adoption, and long-term platform resilience.

Key Takeaways:

  • Privacy becomes significantly more complex in AI-powered products
  • Enterprise trust requires going beyond minimum compliance standards
  • Building privacy into platform architecture reduces future regulatory risk
  • AI systems increase pressure around PII handling and data minimization
  • Treating compliance separately from engineering creates long-term risk
  • Simplifying platform architecture reduces regression risk and operational complexity
  • Unified systems scale more effectively than fragmented configuration models
  • Privacy-first design can become a competitive advantage in enterprise sales
  • Strong platform foundations reduce future engineering fire drills
  • AI trust depends on structure, filters, tokenization, and human oversight

Connect with Matt Lievertz:


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 regulated software, compliance, and AI integration, helping leaders build secure, auditable, and user-friendly systems."

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Matt Lievertz, VP of Engineering at Cloverleaf, to explore how engineering teams can build AI-powered products that balance personalization, privacy, and enterprise trust.

Cloverleaf combines behavioral assessments, workplace communication data, and AI-driven insights to help teams improve collaboration and performance. But handling personality data, coaching interactions, and workplace integrations introduced major technical and ethical challenges around privacy, compliance, and system design.

Matt shares how a difficult enterprise compliance conversation in 2022 became a turning point for the company. Instead of treating privacy as a legal checkbox, Cloverleaf chose to build privacy protections directly into the architecture of the platform. That decision later positioned the company ahead of emerging regulations like GDPR, CCPA, and the EU AI Act.

The conversation also explores how AI systems increase the complexity of privacy engineering, why minimizing personally identifiable information is becoming critical for enterprise AI adoption, and how simplifying platform architecture unlocked both scalability and partner growth.

For engineering leaders, this episode highlights an important lesson: privacy and trust are no longer compliance features — they are foundational product decisions that directly impact scalability, enterprise adoption, and long-term platform resilience.

Key Takeaways:

  • Privacy becomes significantly more complex in AI-powered products
  • Enterprise trust requires going beyond minimum compliance standards
  • Building privacy into platform architecture reduces future regulatory risk
  • AI systems increase pressure around PII handling and data minimization
  • Treating compliance separately from engineering creates long-term risk
  • Simplifying platform architecture reduces regression risk and operational complexity
  • Unified systems scale more effectively than fragmented configuration models
  • Privacy-first design can become a competitive advantage in enterprise sales
  • Strong platform foundations reduce future engineering fire drills
  • AI trust depends on structure, filters, tokenization, and human oversight

Connect with Matt Lievertz:


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 regulated software, compliance, and AI integration, helping leaders build secure, auditable, and user-friendly systems."

]]>857bc393-edc9-4d1f-8e59-eee154616a36Fri, 15 May 2026 09:00:00 -040024:40falsefull"How Lavanya Elangovan Reduced Technical Debt by Embedding Security, Compliance, and Infrastructure Upgrades into Healthcare Engineering Workflows""How Lavanya Elangovan Reduced Technical Debt by Embedding Security, Compliance, and Infrastructure Upgrades into Healthcare Engineering Workflows"Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Lavanya Elangovan to discuss the hidden engineering decisions required to maintain secure, compliant, and scalable healthcare platforms.

Lavanya shares how a planned MongoDB upgrade quickly evolved into a full-stack modernization effort involving Ruby on Rails, infrastructure dependencies, and more than 40 libraries. Driven by both security certification requirements and product scalability goals, the project exposed the risks of accumulated technical debt in regulated environments.

The conversation explores how her team approached the migration through phased rollouts, automated testing, security validation, and incremental infrastructure improvements built directly into the product roadmap. Lavanya also explains why AI-assisted development increases the importance of engineering rigor, human oversight, and deployment discipline.

For engineering leaders, this episode highlights a critical lesson: technical debt is not just a maintenance issue; it directly impacts security, compliance, deployment confidence, and long-term business velocity.

Key Takeaways:

  • Healthcare engineering requires stronger compliance and security practices
  • Infrastructure upgrades often reveal hidden dependency risks
  • Technical debt slows deployment speed and reduces release confidence
  • Incremental modernization is safer than large “big bang” migrations
  • AI-assisted coding still requires strong human oversight and testing
  • Embedding infrastructure work into product roadmaps improves long-term scalability
  • Deployment confidence is a key indicator of platform health

Connect with Lavanya Elangovan:


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 regulated software, compliance, and AI integration, helping leaders build secure, auditable, and user-friendly systems."

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Lavanya Elangovan to discuss the hidden engineering decisions required to maintain secure, compliant, and scalable healthcare platforms.

Lavanya shares how a planned MongoDB upgrade quickly evolved into a full-stack modernization effort involving Ruby on Rails, infrastructure dependencies, and more than 40 libraries. Driven by both security certification requirements and product scalability goals, the project exposed the risks of accumulated technical debt in regulated environments.

The conversation explores how her team approached the migration through phased rollouts, automated testing, security validation, and incremental infrastructure improvements built directly into the product roadmap. Lavanya also explains why AI-assisted development increases the importance of engineering rigor, human oversight, and deployment discipline.

For engineering leaders, this episode highlights a critical lesson: technical debt is not just a maintenance issue; it directly impacts security, compliance, deployment confidence, and long-term business velocity.

Key Takeaways:

  • Healthcare engineering requires stronger compliance and security practices
  • Infrastructure upgrades often reveal hidden dependency risks
  • Technical debt slows deployment speed and reduces release confidence
  • Incremental modernization is safer than large “big bang” migrations
  • AI-assisted coding still requires strong human oversight and testing
  • Embedding infrastructure work into product roadmaps improves long-term scalability
  • Deployment confidence is a key indicator of platform health

Connect with Lavanya Elangovan:


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 regulated software, compliance, and AI integration, helping leaders build secure, auditable, and user-friendly systems."

]]>3e6918fe-274a-4ce5-9edc-6358b7e3b115Thu, 14 May 2026 09:00:00 -040014:47falsefull"How Roy Resh Scaled Retail AI by Moving from Custom Pipelines to Configurable Computer Vision Systems""How Roy Resh Scaled Retail AI by Moving from Custom Pipelines to Configurable Computer Vision Systems"Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Roy Resh, VP of Engineering at Trax Retail, to explore a pivotal architectural decision that reshaped how large-scale computer vision systems are built and scaled in retail environments.

At Trax, Roy and his team built a computer vision platform that analyzes shelf images captured in retail stores, identifying products, pricing, and point-of-sale materials to generate a digital representation of store shelves. This enables brands to measure execution, shelf share, and product availability in near real time. But as the platform scaled across enterprise clients, complexity began to compound rapidly.

What started as a unified recognition pipeline evolved into a heavily customized system, with per-client logic for attributes like expiration dates, display detection, reporting formats, and KPI calculations. Each new customer introduced new requirements, leading to custom code per client, duplicated processing flows, and increasingly long onboarding cycles that stretched from weeks to months.

Roy explains how the system eventually reached a breaking point: onboarding delays of 30–60 days, rising operational overhead, and microservices becoming entangled with client-specific logic. In some cases, the platform even processed the same image multiple times to satisfy different customer requirements, driving up cost and complexity.

The team made a strategic decision to move away from custom implementations and toward a configurable, JSON-driven workflow architecture. Built on event-driven microservices, queues, and coordination barriers, this new system allowed engineering teams to define and version entire processing flows through configuration rather than code.

This shift enabled safer deployments, faster experimentation, and gradual rollouts per client—without affecting the entire platform. It also introduced a standardized KPI layer, reducing the need for bespoke reporting logic across customers.

Roy also discusses the importance of human-in-the-loop validation in production AI systems. In a constantly evolving retail environment, human annotators help generate training data, validate model outputs, and maintain accuracy for high-stakes enterprise use cases where precision is critical.

For engineering leaders, this episode highlights a key lesson: when every customer forces new code paths, you’re not scaling a product—you’re scaling complexity.

Key Takeaways:

  • Over-customization is a clear signal of architectural scaling limits
  • Long onboarding cycles often reveal hidden system fragmentation
  • Configurable workflows reduce dependency on per-client code changes
  • Event-driven, JSON-based orchestration improves flexibility and deployment safety
  • Gradual migration strategies reduce risk in enterprise system rewrites
  • Standardizing KPI logic is as important as standardizing AI pipelines
  • Human-in-the-loop systems remain essential in dynamic real-world AI environments
  • Scalable platforms reduce variability instead of multiplying it

Connect with Roy Resh:


Listen Now & Subscribe:

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

"Engineering Choices You Have to Defend explores the real technical decisions behind regulated software, compliance, and AI integration, helping leaders build secure, auditable, and user-friendly systems."

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Roy Resh, VP of Engineering at Trax Retail, to explore a pivotal architectural decision that reshaped how large-scale computer vision systems are built and scaled in retail environments.

At Trax, Roy and his team built a computer vision platform that analyzes shelf images captured in retail stores, identifying products, pricing, and point-of-sale materials to generate a digital representation of store shelves. This enables brands to measure execution, shelf share, and product availability in near real time. But as the platform scaled across enterprise clients, complexity began to compound rapidly.

What started as a unified recognition pipeline evolved into a heavily customized system, with per-client logic for attributes like expiration dates, display detection, reporting formats, and KPI calculations. Each new customer introduced new requirements, leading to custom code per client, duplicated processing flows, and increasingly long onboarding cycles that stretched from weeks to months.

Roy explains how the system eventually reached a breaking point: onboarding delays of 30–60 days, rising operational overhead, and microservices becoming entangled with client-specific logic. In some cases, the platform even processed the same image multiple times to satisfy different customer requirements, driving up cost and complexity.

The team made a strategic decision to move away from custom implementations and toward a configurable, JSON-driven workflow architecture. Built on event-driven microservices, queues, and coordination barriers, this new system allowed engineering teams to define and version entire processing flows through configuration rather than code.

This shift enabled safer deployments, faster experimentation, and gradual rollouts per client—without affecting the entire platform. It also introduced a standardized KPI layer, reducing the need for bespoke reporting logic across customers.

Roy also discusses the importance of human-in-the-loop validation in production AI systems. In a constantly evolving retail environment, human annotators help generate training data, validate model outputs, and maintain accuracy for high-stakes enterprise use cases where precision is critical.

For engineering leaders, this episode highlights a key lesson: when every customer forces new code paths, you’re not scaling a product—you’re scaling complexity.

Key Takeaways:

  • Over-customization is a clear signal of architectural scaling limits
  • Long onboarding cycles often reveal hidden system fragmentation
  • Configurable workflows reduce dependency on per-client code changes
  • Event-driven, JSON-based orchestration improves flexibility and deployment safety
  • Gradual migration strategies reduce risk in enterprise system rewrites
  • Standardizing KPI logic is as important as standardizing AI pipelines
  • Human-in-the-loop systems remain essential in dynamic real-world AI environments
  • Scalable platforms reduce variability instead of multiplying it

Connect with Roy Resh:


Listen Now & Subscribe:

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

"Engineering Choices You Have to Defend explores the real technical decisions behind regulated software, compliance, and AI integration, helping leaders build secure, auditable, and user-friendly systems."

]]>f75b088d-ea8a-4ec7-a482-0e8ce0cbe9aeWed, 06 May 2026 09:00:00 -040018:15falsefull"How Keith Deming Scaled Computer Vision by Moving AI from Servers to the Edge""How Keith Deming Scaled Computer Vision by Moving AI from Servers to the Edge"Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Keith Deming, an engineering leader with experience at Postmates, Uber, and PRISM Skylabs, to explore a pivotal architectural decision that transformed how computer vision systems scale in the real world.

At PRISM Skylabs, Keith and his team built a platform that turned retail surveillance cameras into powerful analytics tools, tracking foot traffic, customer journeys, and in-store engagement. The system worked exceptionally well… until customers wanted it everywhere. What started as a four-camera deployment quickly became a 200-camera scaling challenge, exposing the limits of server-based infrastructure.

Keith shares how the team faced mounting constraints, hardware costs, power consumption, cooling limitations, and physical space, and realized that simply scaling servers wasn’t viable. Instead, they made a bold shift: moving compute from centralized servers directly onto the cameras themselves.

The conversation dives into how a Raspberry Pi prototype proved edge computing was feasible, why rewriting performance-critical systems from Python to C++ became necessary, and how eliminating video decoding overhead unlocked real-time processing. More importantly, this architectural shift didn’t just solve a technical problem, it removed friction from the buying process, making it easier for customers to adopt and scale the product incrementally.

Keith also reflects on how modern advancements in edge AI and distributed computing are reshaping system design today, and why many teams still underestimate the true cost of centralized infrastructure.

For engineering leaders, this episode highlights a critical lesson: scaling isn’t always about adding more resources—it’s about rethinking where computation happens.

Key Takeaways:

  • Centralized infrastructure can become the biggest bottleneck to scale
  • Edge computing eliminates hardware, power, and space constraints
  • Moving the compute closer to the data reduces latency and processing overhead
  • Prototyping with simple tools (like Raspberry Pi) can unlock major breakthroughs
  • Rewriting for performance (Python → C++) is often necessary at scale
  • Removing infrastructure friction accelerates customer adoption
  • The best architectures reduce reasons for customers to say “no”
  • Distributed and edge-based systems are becoming the future of AI deployment

Connect with Keith Deming:


Listen Now & Subscribe:

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

"Engineering Choices You Have to Defend explores the real technical decisions behind regulated software, compliance, and AI integration, helping leaders build secure, auditable, and user-friendly systems."

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Keith Deming, an engineering leader with experience at Postmates, Uber, and PRISM Skylabs, to explore a pivotal architectural decision that transformed how computer vision systems scale in the real world.

At PRISM Skylabs, Keith and his team built a platform that turned retail surveillance cameras into powerful analytics tools, tracking foot traffic, customer journeys, and in-store engagement. The system worked exceptionally well… until customers wanted it everywhere. What started as a four-camera deployment quickly became a 200-camera scaling challenge, exposing the limits of server-based infrastructure.

Keith shares how the team faced mounting constraints, hardware costs, power consumption, cooling limitations, and physical space, and realized that simply scaling servers wasn’t viable. Instead, they made a bold shift: moving compute from centralized servers directly onto the cameras themselves.

The conversation dives into how a Raspberry Pi prototype proved edge computing was feasible, why rewriting performance-critical systems from Python to C++ became necessary, and how eliminating video decoding overhead unlocked real-time processing. More importantly, this architectural shift didn’t just solve a technical problem, it removed friction from the buying process, making it easier for customers to adopt and scale the product incrementally.

Keith also reflects on how modern advancements in edge AI and distributed computing are reshaping system design today, and why many teams still underestimate the true cost of centralized infrastructure.

For engineering leaders, this episode highlights a critical lesson: scaling isn’t always about adding more resources—it’s about rethinking where computation happens.

Key Takeaways:

  • Centralized infrastructure can become the biggest bottleneck to scale
  • Edge computing eliminates hardware, power, and space constraints
  • Moving the compute closer to the data reduces latency and processing overhead
  • Prototyping with simple tools (like Raspberry Pi) can unlock major breakthroughs
  • Rewriting for performance (Python → C++) is often necessary at scale
  • Removing infrastructure friction accelerates customer adoption
  • The best architectures reduce reasons for customers to say “no”
  • Distributed and edge-based systems are becoming the future of AI deployment

Connect with Keith Deming:


Listen Now & Subscribe:

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

"Engineering Choices You Have to Defend explores the real technical decisions behind regulated software, compliance, and AI integration, helping leaders build secure, auditable, and user-friendly systems."

]]>3f46e6ad-a164-4acb-baa9-7b11ce992a26Mon, 20 Apr 2026 09:00:00 -040021:04falsefull"How Sean Graham Reduced Deployment Risk with Small Batch Delivery""How Sean Graham Reduced Deployment Risk with Small Batch Delivery"Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Sean Graham, VP of Engineering at Idelic, to unpack a critical shift in how engineering teams approach delivery in high-stakes environments.

At Idelic, where software directly impacts fleet safety, compliance, and insurance risk, reliability isn’t optional. Sean shares how their team moved away from traditional two-week sprint cycles after realizing that large batch releases were quietly increasing risk. While velocity appeared healthy on the surface, debugging became guesswork, QA was overwhelmed, and every deployment felt like a high-stakes event.

Instead of optimizing Scrum, the team reframed the problem entirely, focusing on reducing batch size and risk. By shifting to a continuous, small-batch delivery model, they dramatically improved traceability, simplified debugging, and restored trust in their system. Lead time dropped from 25 days to just 4, while releases became routine instead of stressful.

The conversation also explores how infrastructure, like per-ticket test environments and fast pipelines, enabled this transformation, and why discipline became the most important skill once sprint boundaries disappeared.

As AI accelerates code generation, Sean emphasizes that structured delivery systems are more critical than ever. Without them, faster output simply compounds risk. Teams that pair AI with disciplined, low-risk delivery models will scale safely, while others risk creating faster chaos.

For engineering leaders, this episode is a powerful reminder: speed isn’t about working harder, it’s about reducing risk and improving feedback loops.

Key Takeaways:

  • Large batch releases increase risk and reduce system reliability
  • Debugging becomes exponentially harder when too many changes ship together
  • Continuous, small-batch delivery improves traceability and confidence
  • Lead time can drop significantly with continuous validation (25 → 4 days)
  • Psychological safety and trust are critical for high-performing teams
  • Strong infrastructure is required to support fast, safe delivery
  • AI increases output—but without discipline, it also increases risk

Connect with Sean Graham:


Listen Now & Subscribe:

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

"Engineering Choices You Have to Defend explores the real technical decisions behind regulated software, compliance, and AI integration, helping leaders build secure, auditable, and user-friendly systems."

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Sean Graham, VP of Engineering at Idelic, to unpack a critical shift in how engineering teams approach delivery in high-stakes environments.

At Idelic, where software directly impacts fleet safety, compliance, and insurance risk, reliability isn’t optional. Sean shares how their team moved away from traditional two-week sprint cycles after realizing that large batch releases were quietly increasing risk. While velocity appeared healthy on the surface, debugging became guesswork, QA was overwhelmed, and every deployment felt like a high-stakes event.

Instead of optimizing Scrum, the team reframed the problem entirely, focusing on reducing batch size and risk. By shifting to a continuous, small-batch delivery model, they dramatically improved traceability, simplified debugging, and restored trust in their system. Lead time dropped from 25 days to just 4, while releases became routine instead of stressful.

The conversation also explores how infrastructure, like per-ticket test environments and fast pipelines, enabled this transformation, and why discipline became the most important skill once sprint boundaries disappeared.

As AI accelerates code generation, Sean emphasizes that structured delivery systems are more critical than ever. Without them, faster output simply compounds risk. Teams that pair AI with disciplined, low-risk delivery models will scale safely, while others risk creating faster chaos.

For engineering leaders, this episode is a powerful reminder: speed isn’t about working harder, it’s about reducing risk and improving feedback loops.

Key Takeaways:

  • Large batch releases increase risk and reduce system reliability
  • Debugging becomes exponentially harder when too many changes ship together
  • Continuous, small-batch delivery improves traceability and confidence
  • Lead time can drop significantly with continuous validation (25 → 4 days)
  • Psychological safety and trust are critical for high-performing teams
  • Strong infrastructure is required to support fast, safe delivery
  • AI increases output—but without discipline, it also increases risk

Connect with Sean Graham:


Listen Now & Subscribe:

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

"Engineering Choices You Have to Defend explores the real technical decisions behind regulated software, compliance, and AI integration, helping leaders build secure, auditable, and user-friendly systems."

]]>7796ed5d-5210-487b-8144-811ab8466b40Wed, 01 Apr 2026 00:35:00 -040011:32falsefull“How Kevin DiGilio Builds Compliance-First Software for Regulated Industries”“How Kevin DiGilio Builds Compliance-First Software for Regulated Industries”Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Kevin DiGilio, President of KMD Technology. Kevin explains how compliance frameworks like ITAR, NIST, and DFARS don’t just guide documentation; they dictate core system architecture.

When regulations evolved, KMD faced a choice: layer compliance on top of existing software or refactor the entire platform. They chose the latter, embedding user classification, role-based permissions, encryption, and access control throughout the stack. Kevin shares the trade-offs between usability and security, explaining how granular permissions and clear data classification maintain operational efficiency while staying fully compliant.

The conversation also explores AI in regulated manufacturing environments. Kevin highlights how AI systems must inherit compliance rules, log every decision, and enforce strict data boundaries. Improper access or hallucinations aren’t minor—they can be catastrophic.

For founders and engineering leaders, Kevin emphasizes that compliance should shape architecture from the start. Delaying integration almost guarantees costly rewrites, while proactive planning ensures systems that are secure, auditable, and operationally smooth.

Key Takeaways:

  1. Compliance must be embedded into core architecture
  2. Role-based permissions balance usability and security
  3. Encryption and access control are essential at every layer
  4. AI must respect regulatory boundaries with full logging and citation tracking
  5. Delaying compliance leads to costly refactors

Connect with Kevin DiGilio:

  1. LinkedIn: https://www.linkedin.com/in/kevindigilio
  2. Company: https://kmdtechnology.com/

Listen Now & Subscribe:

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

"Engineering Choices You Have to Defend explores the real technical decisions behind regulated software, compliance, and AI integration, helping leaders build secure, auditable, and user-friendly systems."

]]>Episode Summary:

In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Kevin DiGilio, President of KMD Technology. Kevin explains how compliance frameworks like ITAR, NIST, and DFARS don’t just guide documentation; they dictate core system architecture.

When regulations evolved, KMD faced a choice: layer compliance on top of existing software or refactor the entire platform. They chose the latter, embedding user classification, role-based permissions, encryption, and access control throughout the stack. Kevin shares the trade-offs between usability and security, explaining how granular permissions and clear data classification maintain operational efficiency while staying fully compliant.

The conversation also explores AI in regulated manufacturing environments. Kevin highlights how AI systems must inherit compliance rules, log every decision, and enforce strict data boundaries. Improper access or hallucinations aren’t minor—they can be catastrophic.

For founders and engineering leaders, Kevin emphasizes that compliance should shape architecture from the start. Delaying integration almost guarantees costly rewrites, while proactive planning ensures systems that are secure, auditable, and operationally smooth.

Key Takeaways:

  1. Compliance must be embedded into core architecture
  2. Role-based permissions balance usability and security
  3. Encryption and access control are essential at every layer
  4. AI must respect regulatory boundaries with full logging and citation tracking
  5. Delaying compliance leads to costly refactors

Connect with Kevin DiGilio:

  1. LinkedIn: https://www.linkedin.com/in/kevindigilio
  2. Company: https://kmdtechnology.com/

Listen Now & Subscribe:

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

"Engineering Choices You Have to Defend explores the real technical decisions behind regulated software, compliance, and AI integration, helping leaders build secure, auditable, and user-friendly systems."

]]>c3c87d09-b196-44b5-a310-758d49fd8e87Tue, 03 Mar 2026 09:00:00 -040012:41falsefull