book

Effective Machine Learning Teams

by David Tan, Ada Leung, David Colls

February 2024

Beginner to intermediate

402 pages

11h 33m

English

O'Reilly Media, Inc.

Book available

Read now

Unlock full access

Includes

Includes Quizzes

Who This Book Is ForHow This Book Is OrganizedPart I: Product and DeliveryPart II: EngineeringPart III: TeamsAdditional ThoughtsConventions Used in This BookUsing Code ExamplesO’Reilly Online LearningHow to Contact UsAcknowledgmentsFrom David TanFrom Ada LeungFrom David Colls
ML: Promises and DisappointmentsContinued Optimism in MLWhy ML Projects FailIs There a Better Way? How Systems Thinking and Lean Can HelpYou Can’t “MLOps” Your Problems AwaySee the Whole: A Systems Thinking Lens for Effective ML DeliveryThe Five Disciplines Required for Effective ML DeliveryConclusion
ML Product DiscoveryDiscovering Product OpportunitiesCanvases to Define Product OpportunitiesTechniques for Rapidly Designing, Delivering, and Testing SolutionsInception: Setting Teams Up for SuccessInception: What Is It and How Do We Do It?How to Plan and Run an InceptionUser Stories: Building Blocks of an MVPProduct DeliveryCadence of Delivery ActivitiesMeasuring Product and DeliveryConclusion
What If Our Code Worked Everywhere, Every Time?A Better Way: Check Out and GoPrinciples for Effective Dependency ManagementTools for Dependency ManagementA Crash Course on Docker and batectWhat Are Containers?Reduce the Number of Moving Parts in Docker with batectConclusion
In Context: ML Development WorkflowIdentifying What to ContainerizeHands-On Exercise: Reproducible Development Environments, Aided by ContainersSecure Dependency ManagementRemove Unnecessary DependenciesAutomate Checks for Security VulnerabilitiesConclusion
Automated Tests: The Foundation for Iterating Quickly and ReliablyStarting with Why: Benefits of Test AutomationIf Automated Testing Is So Important, Why Aren’t We Doing It?Building Blocks for a Comprehensive Test Strategy for ML SystemsThe What: Identifying Components For TestingCharacteristics of a Good Test and Pitfalls to AvoidThe How: Structure of a TestSoftware TestsUnit TestsTraining Smoke TestsAPI TestsPost-deployment TestsConclusion
Model TestsThe Necessity of Model TestsChallenges of Testing ML ModelsFitness Functions for ML ModelsModel Metrics Tests (Global and Stratified)Behavioral TestsTesting Large Language Models: Why and HowEssential Complementary Practices for Model TestsError Analysis and VisualizationLearn from Production by Closing the Data Collection LoopOpen-Closed Test DesignExploratory TestingMeans to Improve the ModelDesigning to Minimize the Cost of FailuresMonitoring in ProductionBringing It All TogetherNext Steps: Applying What You’ve LearnedMake Incremental ImprovementsDemonstrate ValueConclusion
The Benefits (and Surprising Simplicity) of Knowing Our IDEWhy Should We Care About IDEs?If IDEs Are So Important, Why Haven’t I Learned About Them Yet?The Plan: Getting Productive in Two StagesStage 1: Configuring Your IDEStage 2: The Star of the Show—Keyboard ShortcutsYou Did It!Conclusion

Technical Debt: The Sand in Our GearsGetting to a Healthy Level of Debt Through Tests, Design, and RefactoringRefactoring 101How to Refactor a Notebook (or a Problematic Codebase)The Map: Planning Your JourneyThe Journey: Hitting the RoadLooking Back at What We’ve AchievedTechnical Debt Management in the Real WorldTechnical Debt Management TechniquesA Positive Lens on Debt: Systems Health RatingsConclusion: Make Good Easy
MLOps: Strengths and Missing Puzzle PiecesMLOps 101Smells: Hints That We Missed SomethingContinuous Delivery for Machine LearningBenefits of CD4MLA Crash Course on Continuous Delivery PrinciplesBuilding Blocks of CD4ML: Creating a Production-Ready ML SystemHow CD4ML Supports ML Governance and Responsible AIConclusion
Common Challenges Faced by ML TeamsEffective Team InternalsTrust as the Foundational Building BlockCommunicationDiverse MembershipPurposeful, Shared ProgressInternal Tactics to Build Effective TeamsImproving Flow with Engineering EffectivenessFeedback LoopsCognitive LoadFlow StateConclusion
Common Challenges Faced by ML OrganizationsEffective Organizations as Teams of TeamsThe Role of Value-Driven Portfolio ManagementTeam Topologies ModelTeam Topologies for ML TeamsOrganizational Tactics to Build Effective TeamsIntentional LeadershipCreate Structures and Systems for Effective TeamsEngage Stakeholders and Coordinate Organizational ResourcesCultivate Psychological SafetyChampion Continuous ImprovementEmbrace Failure as a Learning OpportunityBuild the Culture We Wish We HadEncourage Teams to Play at WorkConclusionEpilogue: Dana’s Journey

Content preview from Effective Machine Learning Teams

Chapter 7. Supercharging Your Code Editor with Simple Techniques

There are no shortcuts in life, but there are many in coding.

Juntao Qiu, developer and author

Most ML practitioners that we know love to code. Code is our vehicle for transporting ideas in our head (“will this feature engineering technique improve the model’s performance?”) into reality. In fact, many bemoan the fact that there are too many distractions, too many meetings, and not enough time to write code. However, when we do get time to code, it’s common to find ourselves wasting valuable time on tedious tasks such as manual testing (the focus of Chapters 4 and 5), reading convoluted code (the focus of the next chapter), and unproductive coding practices (the focus of this chapter).

In this chapter, we will detail how you and your team can spend less time getting stuck or even lost in the weeds with unproductive coding practices. We’ll demonstrate how your integrated development environment (IDE) can help you to read and write code more effectively. An IDE is an application designed to aid developers, data scientists, and engineers to write, run, test, and debug code productively. It provides development tools such as a source code editor, integrated terminal, version control support, virtual environment management, and code suggestions. It can also assist you with refactoring toward a better designed and more readable codebase (see Figure 7-1).

To that end, this chapter will cover: