Coffee-break with EngX Experts
summary
Casual Q&A format uses a spinning wheel to pick concrete problems: Copilot privacy and ownership — presenters cite Copilot policy removes uploaded code and argue generated snippets become the developer’s code — plus hazards of overreliance. Unit tests aim for a practical target, roughly 80% industry standard with near‑100% for core libraries. Persuasion uses ROI and risk math, citing process fixes that cut production bugs 13x fewer production bugs, and mentions integrating measurements with EPAM tooling like Prism and delivery dashboards.
AI-written summary · about
chapters (9)
- 0:00Introduction and welcome
- 1:38Introducing the experts
- 5:10AI tools like Copilot in development
- 13:43Security and performance checks in pipelines
- 21:40Unit test coverage standards
- 31:21Enforcing unit testing practices
- 38:30Stopping after-hours client work
- 44:55Engineering Excellence certification
- 53:13Summary and closing remarks
related talks
47mPanel Discussion: QE Strategic Shift: What's Changing with AI, Automation, and Speed?
24mGitHub Copilot Agents + Sonar | The Blueprint for Agentic Development
36mNuances of Influencing Developer Experience and Productivity Through Tech Products
46mPanel Discussion: The Agentic Software Factory That Enterprises Actually Need
52mInject the power of the cloud and AI into your development workflow
43mCopilot Workspace - A reimagined developer inner loop with AI assistance at every step
45mPanel Discussion: Ways to unlock engineering effectiveness
49mPanel Discussion: Mission-Critical Priorities in Quality Engineering: The Leader's Playbook