Event language
UI language
Data science notebooks often represent a <em><strong>"</strong></em><strong>perfect analysis”</strong><em>. </em>But the problem lies in turning them into actual working services in production environments. <br><br>In this proposed workshop session, these are lessons learned working as an ML Engineer/ Data Scientist at Air Arabia, bridging data science work that looks perfect in notebooks with how those ML systems need to be optimized to be in production.<br><br>Using a problem in Formula 1 as an example participants will see,<br><ul><li> How refactoring of a Jupyter notebook into a production-ready Python service happens using best practices,</li><li>Deploy it as a scheduled job or inference API (FastAPI vs Cron), </li><li>Observability to catch failures. (Grafana, logging)</li><li>Post-deployment maintenance</li></ul><br>Also, exploration will be done on how real-world business behavior (Changing records, data inconsistencies, data drift) can invalidate predictions even when models are technically correct, and how explainability plays a role for stakeholders.