Engineering Choices You Have to Defend

Nicola Onassis
  • 5.0 (1)
  • Technology
  • Series

Real-world engineering decisions in AI, compliance, and production systems

  1. Mar 3

    “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: Compliance must be embedded into core architectureRole-based permissions balance usability and securityEncryption and access control are essential at every layerAI must respect regulatory boundaries with full logging and citation trackingDelaying compliance leads to costly refactors Connect with Kevin DiGilio: LinkedIn: https://www.linkedin.com/in/kevindigilioCompany: 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."

  2. Apr 1

    "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 reliabilityDebugging becomes exponentially harder when too many changes ship togetherContinuous, small-batch delivery improves traceability and confidenceLead time can drop significantly with continuous validation (25 → 4 days)Psychological safety and trust are critical for high-performing teamsStrong infrastructure is required to support fast, safe deliveryAI increases output—but without discipline, it also increases risk Connect with Sean Graham: LinkedIn: https://www.linkedin.com/in/sean-graham-675a054Website: https://profed.laroche.edu 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."

  3. Apr 20

    "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 scaleEdge computing eliminates hardware, power, and space constraintsMoving the compute closer to the data reduces latency and processing overheadPrototyping with simple tools (like Raspberry Pi) can unlock major breakthroughsRewriting for performance (Python → C++) is often necessary at scaleRemoving infrastructure friction accelerates customer adoptionThe 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: LinkedIn: https://www.linkedin.com/in/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."

  4. May 6

    "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 limitsLong onboarding cycles often reveal hidden system fragmentationConfigurable workflows reduce dependency on per-client code changesEvent-driven, JSON-based orchestration improves flexibility and deployment safetyGradual migration strategies reduce risk in enterprise system rewritesStandardizing KPI logic is as important as standardizing AI pipelinesHuman-in-the-loop systems remain essential in dynamic real-world AI environmentsScalable platforms reduce variability instead of multiplying it Connect with Roy Resh: LinkedIn: Roy Resh: linkedin.com/in/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."

  5. May 14

    "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 practicesInfrastructure upgrades often reveal hidden dependency risksTechnical debt slows deployment speed and reduces release confidenceIncremental modernization is safer than large “big bang” migrationsAI-assisted coding still requires strong human oversight and testingEmbedding infrastructure work into product roadmaps improves long-term scalabilityDeployment confidence is a key indicator of platform health Connect with Lavanya Elangovan:LinkedIn: Lavanya Elangovan — linkedin.com/in/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."

  6. May 15

    "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 productsEnterprise trust requires going beyond minimum compliance standardsBuilding privacy into platform architecture reduces future regulatory riskAI systems increase pressure around PII handling and data minimizationTreating compliance separately from engineering creates long-term riskSimplifying platform architecture reduces regression risk and operational complexityUnified systems scale more effectively than fragmented configuration modelsPrivacy-first design can become a competitive advantage in enterprise salesStrong platform foundations reduce future engineering fire drillsAI trust depends on structure, filters, tokenization, and human oversight Connect with Matt Lievertz:LinkedIn: Matt Lievertz — linkedin.com/in/lievertzWebsite: Cloverleaf — cloverleaf.me 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."

  7. May 26

    “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 problemsManaging large fleets requires strong architecture and automationStakeholder alignment is critical during platform redesignsAI-assisted development increases the importance of planning and oversightSimplifying workflows often creates more value than adding new features Connect with David Phipps: LinkedIn: David Phipps — linkedin.com/in/dphipps 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.

  8. May 27

    “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 tasksGenAI works best as a reasoning layer on top of existing systemsHybrid AI architectures reduce cost and improve scalabilityEnterprise AI systems must ground responses in customer dataRAG pipelines require careful tuning and retrieval quality managementHallucination control is critical in business environmentsThere is a major gap between AI demos and production systemsReplacing entire platforms with GenAI often creates unnecessary complexityEngineering teams should focus on business use cases, not AI hypeSuccessful AI adoption requires experienced implementation and planning Connect with Alex Smirnoff: LinkedIn: Alex Smirnoff — linkedin.com/in/alex-smirnoff-34a13135 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.

See All (17)

Ratings & Reviews

About

Real-world engineering decisions in AI, compliance, and production systems

Information